-
-
Notifications
You must be signed in to change notification settings - Fork 121
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
502 Bad getway after updating RatOS core packages (v2.1.0-RC2) #178
Comments
Same problem for me. I could install if I skipped the part with updating before continuing, but efter printer vas setup and working I updated and the system collapsed with plenty of errors. |
Same here. I updated RatOS core packages and now I am unable to access configurator and I also get a bunch of moonraker warnings. I tried to manually install RatOS configurator using the command git clone [email protected]:Rat-OS/RatOS-configurator.git, thinking perhaps if I reinstalled the package and ran the install script, it may fix the issue, but I get access denied errors. |
I no longer have this issue. I reflashed RatOS 2.1 on my SD Card and did all the setup before updating the packages and the printer is now fine. Still an issue if you follow the documentation steps, but workaround exists. |
Same problem here. Updated to latest packages, and klipper throws error connecting to mcu, lots of moonraker warnings and bad gateway on configurator. |
What happened
Error 502 Bad Getway when access http://ratos.local/configure after updating ratos core packages
What did you expect to happen
I want to try new ratos version, so I downloaded https://github.com/Rat-OS/RatOS/releases/tag/v2.1.0-RC2 then flash to my SD card, BelenaEtcher not working so I use rufus and it worked.
After config wifi, I follow the config steps here https://os.ratrig.com/docs/installation/#updating-ratos by updating ratos core packages, then when I continue to the confiurator, the page shows 502 Bad Getway error
How to reproduce
RatOS
ratos-configurator
Additional information
No response
The text was updated successfully, but these errors were encountered: