Server is offline


#1

What is the problem?
I installed 2018-04-11_2018-03-13-octopi-stretch-lite-0.15.0.zip

It worked for first 24h of print job, and it worked great, then suddenly, I got

Server is offline. The server appears to be offline, at least I'm not getting any response from it.

When I reload the page, I can see the basic home screen, can't see the webcam and can't login...

UPDATE: I think this is linked using the pi from another subnet- 192.168.1.x [wired] to 192.168.2.x [wireless- subnet that Pi is connected to]

I can SSH, load first page, but can't login, or see webcam.

What did you already try to solve it?

I've tried rebooting the Pi, accessing using different web browsers, updating the distro, etc. The process appears under be running top, but does not respond to web queries.

How can I know what's wrong?

Where can I view logs?

Additional information about your setup (OctoPrint version, OctoPi version, printer, firmware, octoprint.log, serial.log or output on terminal tab, ...)


#2

(as linked on top of the post dialog ;))


#3

Thanks for the link!

Here is what the log shows when I connect from .1.x.. Note on the web client side, I get the "Server is offline".

2018-04-19 10:45:02,834 - octoprint.server.util.sockjs - INFO - Client connection closed: ::ffff:192.168.1.70
2018-04-19 10:45:02,849 - octoprint.server.util.sockjs - WARNING - Could not send message to client ::ffff:192.168.1.70: object of type 'NoneType' has no len()
2018-04-19 10:45:02,856 - octoprint.server.util.sockjs - INFO - Client connection closed: ::ffff:192.168.1.70
2018-04-19 10:45:02,871 - octoprint.server.util.sockjs - INFO - New connection from client: ::ffff:192.168.1.70
2018-04-19 10:45:02,981 - octoprint.server.util.sockjs - INFO - New connection from client: ::ffff:192.168.1.70
2018-04-19 10:45:03,083 - octoprint.server.util.sockjs - INFO - New connection from client: ::ffff:192.168.1.70
2018-04-19 10:45:03,243 - tornado.access - WARNING - 400 GET /sockjs/180/glnal2zq/websocket (127.0.0.1) 2.54ms
2018-04-19 10:45:08,827 - octoprint.server.util.sockjs - INFO - Client connection closed: ::ffff:192.168.1.70
2018-04-19 10:45:08,834 - octoprint.server.util.sockjs - INFO - Client connection closed: ::ffff:192.168.1.70
2018-04-19 10:45:08,868 - octoprint.server.util.sockjs - INFO - New connection from client: ::ffff:192.168.1.70

Here is what happens when I connect from .2.X; please note I was able to get to connect printer dialogue (printer was not connected).

2018-04-19 10:46:00,352 - octoprint.server.util.sockjs - INFO - New connection from client: ::ffff:192.168.2.70
2018-04-19 10:46:00,508 - octoprint.server.util.sockjs - INFO - Client connection closed: ::ffff:192.168.2.70
2018-04-19 10:46:05,827 - octoprint.server.util.sockjs - INFO - Client connection closed: ::ffff:192.168.1.70
2018-04-19 10:46:05,836 - octoprint.server.util.sockjs - INFO - Client connection closed: ::ffff:192.168.1.70
2018-04-19 10:46:05,855 - octoprint.server.util.sockjs - INFO - Client connection closed: ::ffff:192.168.2.70
2018-04-19 10:47:04,307 - octoprint.util.comm - INFO - Changing monitoring state from "Offline" to "Detecting serial port"
2018-04-19 10:47:04,410 - octoprint.util.comm - INFO - Changing monitoring state from "Detecting serial port" to "Error: Failed to autodetect serial port, please set it manually."

Any idea why octoprint only works from within it's domain?


#4

Please always provide the full log. Also check the JS error console, that might give you more hints.

This certainly looks like something in the web socket connection is going nuts when coming from your .1.x subnet:

2018-04-19 10:45:03,243 - tornado.access - WARNING - 400 GET /sockjs/180/glnal2zq/websocket (127.0.0.1) 2.54ms

In general OctoPrint shouldn't care about sub nets, but if there's something in between causing connections like the socket connection to fail, you'll get errors. Could also be increased delays that cause issues here. It's tricky to debug from afar.