-
-
Notifications
You must be signed in to change notification settings - Fork 116
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
Autoupdater breaks install #358
Comments
Thanks for the log, but we need different logs.
This is because we want to know WHY libs.min.js does not exist. |
😂 Could have thought about it. I attached the apache error_log.txt. Unfortunately, there is no PHP error log. Looks like a permission problem? |
I see:
So that means the extraction worked. But then:
Are you using SELinux? If so, you should check the configuration. |
This is a shared hoster using Plesk. I really don't know what is running in the background there. I can redo the test and check permissions on files and folders if this helps. |
Hello, Same problem with different configuration. No error in php and apache log. |
If @Bagu has this problem on windows then it is probably not related to SELinux. Is there anything we can do for you here? Do you want to have a look at my shared hoster to see what's going on? |
Hello, I have a lead. Looking closer, I have this message that appears in the console of firefox: And when i try a direct access : |
Did you disable auto updater feature? I wanted to give the updater another try. I am currently on 2.16.1. The about page tells me that there is a 2.16.2 with a link to releases. But there is no button for auto update anymore. Is there anything, we can help you with? |
Nothing new with this version. It seem that there is a mime type problem ? |
Any news on the auto-updater? |
Somehow i can't reproduce this issue. Did you find out? |
Nop. I'm under php 8.1.12 + fcgid + apache 2.4.54. Mozilla console show that app.min.css and libs.min.js can load and type is shown as html instead of css and js type. |
Open the Firefox developer tools. |
It show an error 400.
|
I think i found the problem. But i also need to check the umask() and after that it might work. |
Good evening, but the one concerning is still there. |
Could be, i'm still investigating |
I try v2.27.3 and still having the problem. I try remove every .htaccess modification of my vhost, but i don"t have any success. |
Hi. Any news on this one? Is there anything we can help with? I could do some testing, if you needed that. |
I've done a test : if i don't use HTTPS, it work. |
Hmmm, i'm shooting in the dark. But maybe an issue in the HTTP/2 protocol handling? |
I did some tests by disabling mod_httpd2. Unfortunately, the result is the same. Several files are not sent by Apache when using https. |
I find the problem in my configuration :
If i remove these lines, snappy work in http and https. |
Correct! The folders If not there is probably a (selinux?) permissions conflict. |
So fixing rights to these folders will help for now? |
Yes it should |
yes, that fixed it. Thank you. |
I tried to auto update to current version 2.32.0 and it is the same problem again. Folder permissions were 0700 again. After setting them to 0755 manually, it worked again. |
Correct! |
I can confirm that it worked this time. Thanks!!! |
your welcome |
Describe the bug
In snappy v2.15.0, I tried to use the new shiny auto-updater. It told me that there is a new version. When I clicked "update", the page reloaded after about a second and showed me that there was still an update to v2.15.1. I waited a minute and tried to reload the page where I ended up stuck with this message:
An error occurred.
Please refresh the page and try again. Failed loading /snappy/snappymail/v/2.15.1/static/js/min/libs.min.js
After that, I deleted v2.15.1 folder and changed the version in index.php to
define('APP_VERSION', '2.15.0');
That made the software work againand I could reproduce the behaviour again.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Updated to v2.15.1
log
log-2022-04-30.txt
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: