You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When updating from 2.29.1 to 2.29.4, I keep getting an error which breaks the web app. Any attempt to access the application returns this user-facing error:
An error occurred.
Please refresh the page and try again.
Failed loading /snappymail/v/2.29.4/static/js/min/libs.min.js
I tried using the built-in web updater. That caused this initially. I reverted to 2.29.1, and got it working again. Then I tried replacing the server files manually. The same error resulted.
I would have assumed that after the update, I would be able to load the web app normally, as the documentation indicates that a simple file replacement should be sufficient.
Browser: any
PHP version: 7.4
SnappyMail Version: 2.29.4
Mode: standalone
Logging was already enabled:
But there is no "logs" folder, where specified in the documentation: …/data/_data_/_default_/logs
Am I messing something up? Thank you!
The text was updated successfully, but these errors were encountered:
What if you delete snappymail/snappymail/v/2.29.4/static/.htaccess?
There was no htaccess file under that directory, but I tried deleting the ones in the root directory, and the data directory. No change.
Would be nice to have the exact HTTP error code and such
I'm getting HTTP/200. No error code there, just the web app displaying this error message on top of its standard theming. The CSV is still being utilized.
When updating from 2.29.1 to 2.29.4, I keep getting an error which breaks the web app. Any attempt to access the application returns this user-facing error:
I tried using the built-in web updater. That caused this initially. I reverted to 2.29.1, and got it working again. Then I tried replacing the server files manually. The same error resulted.
I would have assumed that after the update, I would be able to load the web app normally, as the documentation indicates that a simple file replacement should be sufficient.
Logging was already enabled:
But there is no "logs" folder, where specified in the documentation:
…/data/_data_/_default_/logs
Am I messing something up? Thank you!
The text was updated successfully, but these errors were encountered: