-
Notifications
You must be signed in to change notification settings - Fork 550
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 error after updating #1351
Comments
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue still happens after pulling the latest docker image as of today 8/2/2024 |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
I'm also getting this, but it doesn't seem to matter if it's a new directory or the existing directory. Possibly because I'm using mysql. |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
I just tried to update to 2.6.2 using the above commands and I'm still getting a 500 error. Error from apache2 error log
|
Have you tried creating it from scratch and copying the database over? My guess is there is some conflicting files from the old install. 2.6.0 updated the underlying Laravel version from 8 to 10 |
That seems to have done the trick. Settings are reporting v2.6.3. I only copied over the database dir and .env file. If there's anything else I should bring over let me know |
HI all.
After updating from v2.5.6 to v2.6.1 I'm getting an http 500 error with the following in the apache error log.
I'm updating as follows...
If I clone to a new dir then there's no issue so it's something to do with the update.
Any ideas on what the issue is?
Cheers,
Shannon
The text was updated successfully, but these errors were encountered: