I’ve seen plenty of people run into this and similar issue, but I haven’t been able to find a solution.
The login screen is presented, I enter the correct admin username and password, and then try to login. Several calls are made, and then “Login success” is displayed in the browser console.
One second or so later, the message “Error occurred while retrieving records” is displayed on the login screen, and there’s the dreaded
10:58:02.152
XHRGET
https://suitecrm.local/api/index.php?action=Login&module=Users
[HTTP/2 404 Not Found 316ms
How can it first validate my login successfully, and then all of a sudden return a 404 …
Yes on all accounts This was a working 8.3.x installation before, so all of that is verified.
The URL looks strange because of the “suitecrm.local” hostname, but that’s actually OK. The weird thing is that everything loads up and looks fine, until suddenly the API call returns a 404.
Well that’s certainly odd But I do see the /#/Login URL before I click the button. And there are calls to /api/graphql that succeed. So it’s only the last URL that you list that differ.
I’m pointing DocumentRoot (Apache) to the /public SuiteCRM folder. The relevant block has AllowOverride all. The .htaccess file in /public/legacy has /legacy/ as its RewriteBase.
What I don’t get is why it says the login was successful and then it just kicks back with an error (but perhaps that’s due to the failed api call).
If I enter invalid credentials on purpose, it does tell me that they are indeed invalid.
The php_errors.log does show content, but only PHP deprecation notices. No errors.
The Apache error log file shows nothing of interest.
The directory that holds PHP session files is quickly filled with “junk” (session files) even after I clear it and re-start PHP-FPM.
I tried this with PHP FPM 8.1 and 7.4, same result.
And I don’t understand why my fresh install works (also 8.4.0) but this one doesn’t. It’s almost as if there’s something “odd” in the database lingering that triggers bad code.