-
-
Notifications
You must be signed in to change notification settings - Fork 107
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
500 server error when trying to access notification menu (v0.21.0) #1652
Comments
Seem to be related to the database migrations. |
@svenvg93 That command emptied my database |
Yes same, I will roll back to a backup from earlier today. |
Yeah don't run that command in production, it's a part of testing and the initial install process. |
I'll circle back to this tonight, I suggest staying on |
It is save to just use the old tag after upgrade to latest or will this broke something in the DB? |
Yes you can roll back |
@eeeeb or someone else experiencing the issue, if you're familiar with navigating your database can you verify the following records in the |
If you have some steps to get there I can pull that info. I didn't rollback my image. |
@alexjustesen recent migrations has 2 batch |
For those having the issue and the |
Restarted twice and didn't help. Sorry I didn't get a chance to look and see if my tables look the same though. |
Can you add/set the environment variable |
It works! |
That worked |
🤘 fix incoming, thanks all! |
I had this same issue though I'm on version |
Describe the bug
I just updated my docker image from 0.20.9 to 0.21.0 and when I try to open the notifications menu, I get an 500 server error message.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The notification settings are being displayed
Environment (please complete the following information):
Screenshots
Logs
From the laravel.log
The text was updated successfully, but these errors were encountered: