Cannot connect anymore to Moonraker server through another pc
Hi there. I cannot connect anymore to the Moonraker server nor SSH with WinSCP on another PC. However on the PC running Klipper everything works. I checked the Moonraker status and everything seems to be running fine. I also have a warning message on Mainsail saying that the path of the moonraker.conf file is not good. I tried to changed it however when i change it, i got multiple warning messages. Thanks in advance 😉
17 Replies
are you using IP address when trying to SSH?
reguarding the moonraker - did you update from ratos-1.x to ratos-2.x?
Yes I used my login and the IP address from the server.
I started with ratios-2.x
are the IP of the destination and the source in the same subnet?
It was a new installation
Yes because yesterday it worked, I tried to resolve the moonraker warning message by moving the moonraker.conf file from the Ratos folder to the config parent folder. And since I cannot ssh or connect to the IP address
yeah, you shouldn't have done that
If it was a fresh install of ratos-2.x then you just needed to update things and it would been ok
Then should I reinstall moonraker?
reflash ratos and follow the instructions: https://os.ratrig.com/docs/installation#updating
I'll try that
after you update, you can ignore those moonraker warnings
I updated the System and Klipper in the update manager section, now everything is up to date. However it still doesn't work, I cannot ssh nor connect to the IP address.
I'm not using a pi as server but a pc, so i do
[email protected]
imprimante is the name of my pc on the router.that's not how it works. ssh takes the <username>@<ip address>
so what is the username on that system?
it the same
imprimante, before to ssh I only did imprimante@imprimante
and my passwordNot sure then, the recommended setup is a physical PI (or other single board computer). Not knowing how you setup the network when you created the machine on your router, I can't really troubleshoot further
Ok thanks, i think i'll reinstall everthing from scratch. Thanks for your help 😉
I found the problem it was coming from my router (the security protocle WPA).