Mainsail to Moonraker Connection
I have a Mainsail to Moonraker connection issue while trying to install the firmware on my new V-minion. Following the RatOS configuration documentation, I was successful in installing RatOS v2.0.0 onto my pi3B+ and ran the RatOS configurator. I successfully started step 2 of the configurator which flashes the control board. My printer uses the SKR 2 (429) board. So I selected that option for the configurator to create the binary file to flash the control board. After installing the microSD card into the controlboard I powered everything up and logged into ratos.local which brought up Mainsail. Everything seems to be working per the instructions at this point until I try to update RatOS using Update Manager in Mainsail. I click on the update button and it starts the update process and then Mainsail tries to connect to Moonraker whereby I get a connection failed error "Cannot connect to Moonraker (ratos.local)". The trouble shooting section of the RatOS documentation said to fix this problem by adding your IP range in CIDR notation to the [authorization] section in "~/klipper_config/moonraker.conf" on the pi as follows:
ssh ratos.local
nano ~/klipper_config/moonraker.conf
sudo systemctl restart moonraker
Problem is that after I SSH into the pi, there is no klipper_config directory and no moonraker.conf file to edit. I did, however, find a moonraker.conf file under the Machine tab Config Files section on Mainsail. Commented out the authorization section as directed by the instructions as an alternate solution, saved it but it didn't solve the problem. The guide also said the issue might be fixed by logging into Mainsail using the IP address instead of the ratos.local address. Didn't work.
Can anyone tell me how to fix this? Thankyou for your help.
9 Replies
I think you are getting errors because you are not following the ratos documentation https://os.ratrig.com/docs/installation
start there and if you run into an issue, don't try and follow another guide. come back here and post the issue you ran into
exotic-emerald•2y ago
Thanks for replying. That's the documentation I did follow - to the letter as far as I can tell.
ok, so what step are you on that you are getting the error?
exotic-emerald•2y ago
I'm in Mainsail and using the Update Manager to update RatOS before updating the other components. Its during the update process when Mainsail apparently tries to connect to Moonraker that the connection error occurs.
@miklschmidt any idea if they still need to update moonraker.conf?
I did, however, find a moonraker.conf file under the Machine tab Config Files section on Mainsail. Commented out the authorization section as directed by the instructions as an alternate solution, saved it but it didn't solve the problemYou wouldn't be able to do this if you were getting:
Cannot connect to Moonraker (ratos.local).. So i'm confused.
This is normal
Moonraker is restarted in case of changes to the configuration.
It should come right back when you click "try again"
"it's a feature, not a bug" :D.. You should also be presented with "Update succesful" afterwards.
Ie, there's no problem here, proceed as normal 🙂
there's nothing to update in RatOS v2.exotic-emerald•2y ago
If there is nothing to update, why does The update manager show that there is? I'm confused too.
I'm curious. Did the RatOS documentation get updated for the release of v2? I ask because the installation section clearly instructs to update RatOS to the latest before updating the other components once you first get into Mainsail.
Was talking specifically about moonraker.conf in ~/printer_data/config which isn't a managed file.
Yes it did. And yes you're supposed to update.
I click on the update button and it starts the update process and then Mainsail tries to connect to Moonraker whereby I get a connection failed error "Cannot connect to Moonraker (ratos.local)".This is completley normal, you just click the "try again" button and it should come right back. That happens because moonraker need to be restarted during the updates. I don't think you ever experienced an actual error, you should just proceed with the installation 🙂
exotic-emerald•2y ago
Ok, I'll try again and let you know what happens. Thanks for the help.