For months, years actually, backups w/ Akeeba, most recently with 5.2.5-pro, appear to work fine. Restores from them to the same sub-domain directory on the same web host server with an emptied database often failed however and I don't know why. Restores from 5.2.5-pro backups to the same sub domain directory on the same web host server with an emptied database have always failed and I don't know why.
Description of my issue: First sign of trouble is I logout from one of my J3.6.5 sites after installing Akeeba core or pro and running a Site+DB backup OK. I try to do an admin login and the admin login fails. There seems to be nothing I can do to restore the site, even via Angie Restore from the jpa backup, so I can do an admin login ever again. I've tried so many ways to work-around and restore the site and all ways fail.
WTF is going on? I'm now 99.99% sure Akeeba Backup is the problem. Here is my latest most convincing test:
I had my J3.6.5 site with only the ProjectFork4 (4.3.3) extension installed on it, but no content, up for weeks during which time I logged out and logged in again -- and I changed nothing on the site. I could always login again. Once I installed Akeeba Backup, 5.2.5-pro in this most recent case, I ran a Site+DB backup AOK. Logged out. Tried to do my usual admin login again. And the admin login failed. I could never do an admin login again no matter how I tried to restore the site to ~99% what is was when last I was admin logged in ok.
My next option, only option at this point, is to STOP USING AKEEBA BACKUP, build my J3.6.5 sites once again in very simple ways with only 1-2+ other extensions, installed one-by-one, after which I keep testing back-end logout and re-login as administrator for days or more given only the one new extension installed. In this way I see which other extensions cause this login problem and which don't.
PLEASE TELL ME YOU KNOW ABOUT THIS PROBLEM AND HAVE A FIX FOR IT.
JGW-SanFrancisco.org