search

Arksine / moonraker

Web API Server for Klipper
https://moonraker.readthedocs.io
GNU General Public License v3.0
1.09k stars 417 forks source link

Failed to Connect to spoolman: [Errno 113] No route to host #897

Closed JekleFPV closed 3 months ago

JekleFPV commented 3 months ago

What happened

Spoolman worked just fine on the latest software about two weeks ago.

I ran the latest updates available for klipper/moonraker/mainsail/fluidd/spoolman today. Ever since updating, both Mainsail and Fluidd report "Spoolman server not available". The Spoolman webUI is working though, on the same address as it was before.

Screenshot 2024-08-11 at 17 00 47

Not sure where the problem lies, but Moonraker.log reports the following: Failed to Connect to spoolman: [Errno 113] No route to host

Client

Mainsail, Fluidd, MobileRaker

Browser

Safari

How to reproduce

It was working properly about two weeks ago, I only updated everything to the latest version just today, error has popped up ever since

Additional information

moonraker-3.log

Arksine commented 3 months ago

The error suggests that the Spoolman server is not available at the configured address/port. I'd suggest checking the Spoolman service to make sure its running. I'd also check the IP address and port, if DHCP assigned the host a different IP you would get this error.

JekleFPV commented 3 months ago

The error suggests that the Spoolman server is not available at the configured address/port. I'd suggest checking the Spoolman service to make sure its running. I'd also check the IP address and port, if DHCP assigned the host a different IP you would get this error.

Spoolman is running, I can get into its own webUI and interact with it, on the same address and port as before, so none of that should be the issue.

Arksine commented 3 months ago

For some reason it isn't reachable from Moonraker. You are experiencing a network error. Unfortunately I don't have any guidance as to what the best way is to solve it other than my previous suggestions.

JekleFPV commented 3 months ago

EDIT: never mind, turns out moonraker.conf had a static IP set, instead of localhost.... Smooth sailing again!

Everything is running on the same RPi, so wouldn't really be a network issue, but is there any file I could check for the localhost address perhaps?

Arksine commented 3 months ago

EDIT: never mind, turns out moonraker.conf had a static IP set, instead of localhost.... Smooth sailing again!

Glad you were able to resolve it, I thought it might be a DHCP issue. I'll close this as complete.