New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade from 3.7.0 to 3.8.0 got db error, can no longer log in. #13984
Comments
If it's helpful, the console script errors on all commands right now:
|
and the error message I get when I attempt to log in is:
|
This issue has been reported by multiple other uses on the forum at https://forum.matomo.org/t/cannot-sign-in-after-update/31321/2 |
The error message I saw is the same mentioned on the forum,
|
I also got this I could continue with the update though, needed to re-login. |
Probably related to #13836 Kind a tells you, that Matomo doesn't do even basic QA of the upgrade. |
here my error: |
I found, that you need to click "Back to Matomo", and it will ask you to Upgrade DB, which adds new (missing) table |
👍 Same happened to me on 1 VPS server running Matomo, and I could not log-in from any of my devices afterwards (all PCs, mobiles where I was logged-in before auto-update).
( btw. you are using html special characters encoding in PHP log files - why? ) FIX Then, I have cleared application cache (alternatively delete your cookies on mobile for Matomo/Piwik website), restarted browser and now finally I can normally log-in back. Off-topic: Btw. my file ownership and permissions are in order, every other PHP app can read/write there just fine, except Piwik/Matomo for couple of major update releases now (3.x something). Every time I have to manually run commands in terminal to remove obsolete files - Why? Something is definitely not right there. If this was truly the case, temporary and cache files errors would be present in the first place, which aren't (they are normally created, including sub-dirs etc.). |
+1 |
i can't relogin.... i've deleted the cache and it doesn't work. |
You will probably have to create the missing database table and update database manually: See Matt's answer here: #13836 (comment) Also, do not use your bookmark, instead, try to access to your 'root' matomo folder without any URL parameters (index.php?etc...). |
Same problem about missing table here - both, on a Debian and a FreeBSD server: |
duplicates #13836 |
I saw a notice about upgrading from 3.7.0 to 3.8.0, so I followed the web UI for performing the upgrade. After initiating the upgrade, I got an error which unfortunately I did not write down or screenshot so I can't supply any error message. I retried loading the login page and was directed to a different page indicating that my database was out of date and had to be upgraded, so I clicked the button to proceed, and got a 502 error. Now when I load the login page everything appears okay, but I can't log in with my admin account anymore.
FWIW, my analytics requests from tracked pages are returning 200 responses, so hopefully it's still collecting data and the issue is only related to log-in lockout.
This is hosted on a VPS, so I'm happy to SSH in and pull any logs if folks know of a special place upgrade / migration logs get stored.
The text was updated successfully, but these errors were encountered: