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
Standalone-updater runs into http/403 #1049
Comments
I got the same error when trying to update from 2.0.4 to 2.0.6. |
Also Forbidden when upgrading from 2.0.5 to 2.0.7, 2.0.5 to 2.0.8, 2.0.7 to 2.0.8, 2.0.7 to 2.0.9, 2.0.8 to 2.0.9 and 2.0.9 to 2.0.10 (Curl as well as fgets methods). |
Got the same from 1.2.12 to 2.0.7. |
@peter-mw Is there any hope of fixing this problem? |
Found this... Changed permissions in config, storage and userfiles to 777, no change, so I put it back. Laravel log doesn't report anything about this problem. Enabled debug.. does it debug only to Laravel log? |
Found this beautiful helper. It is not Standalone Updater, but works (from 2.0.7 to 2.0.9). |
Hi, any news about the issue/ more people having it? Also 403 from 2.0.10 to 2.0.12. Today's log... |
So is there any solution to this or is the CMS just broken? Such a shame. |
Please add the following line to .htaccess
See #1063 Additionally if you have command line access you can update with
|
When trying to update from 2.0.2 to the latest version (currently 2.0.5), I'm just running into a 403 from my Apache server (version 2.4.56) on Debian 11.
I do believe thats not an error of microweber, but can't find a solution to it either, so maybe theres someone here who can help me?
The Log from the Apache says
"GET /userfiles/standalone-update/3381701083453/index.php?installVersion=latest HTTP/1.1" 403 521 "https://<domain>/admin/settings?group=updates"
The folder where microweber is stored is owned by the apacheuser and the rights are set to 744 (tried to set them to 777, nothing changed).
Is there anything further I could provide to resolve this?
The text was updated successfully, but these errors were encountered: