After running plugin updates (I don't recall which, I just saw the popup and figured why not) and restarting the Raspberry Pi (3B), OctoPrint won't show the web interface. The port responds and I see the "OctoPrint is still starting up, please wait..." screen, but it stays this way for hours. I've rebooted the pi, restarted the service, and attempted safe mode with no such luck.
I'm running the pi over Ethernet so there shouldn't be any problems with latency or interference with wifi and the power supply is capable of providing 2.4A.
What did you already try to solve it?
Rebooted the Raspberry Pi
Restarted the OctoPrint service
Reviewed the octoprint.log file for errors
Started OctoPrint in safe mode
Have you tried running in safe mode?
Yes
Did running in safe mode solve the problem?
No
Systeminfo Bundle
You can download this in OctoPrint's System Information dialog ... no bundle, no support!)
I don't have access to the web interface so I can't get the 'official' bundle but I've glued together the logs as requested in the systeminfo bundle page.
I also tried the command posted on Unable to connect to OctoPrint web interface - #2 by PrintedWeezl , both with and without the ., but it just sat for 10+ minutes without outputting anything useful (other than the grep copyright information) or returning to the system prompt. I also don't see anything using high cpu or writing anything to the current directory so I'm not sure what it should be doing.
Additional information about your setup
OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible
Unfortunately that did not work for me, below is the output of the command. I had left it running since I posted this yesterday and just now stopped it manually.
pi@octopi:~ $ date
Sun 3 Aug 14:40:14 EDT 2025
pi@octopi:~ $ ~/oprint/bin/octoprint systeminfo
grep (GNU grep) 3.6
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Written by Mike Haertel and others; see
<https://git.sv.gnu.org/cgit/grep.git/tree/AUTHORS>.
^C^C
Aborted!
pi@octopi:~ $ date
Mon 4 Aug 12:31:59 EDT 2025
pi@octopi:~ $
Yes I've tried clearing the cache with ctrl+shift+r, ctrl+F5, incognito/private browsing, and using different browsers.
This morning the octoprint webpage simply showed " Looks like something went wrong during startup, the server is gone again. You should check octoprint.log." but the logs are still showing the heartbeat.
[...]
2025-08-03 23:59:36,816 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2025-08-04 00:14:36,817 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2025-08-04 00:29:36,818 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2025-08-04 00:44:36,818 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2025-08-04 00:59:36,819 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2025-08-04 01:14:36,820 - octoprint.server.heartbeat - INFO - Server heartbeat <3
I'm not opposed to a reinstall, but if this is fixable, that is my preferred solution.
If the storage was full the log would stop writing. But the heartbeat is going and nothing in the log indicates any kind of error.
Does the recovery page work? You should be able to reach it by attaching /recovery/ to the end of your regular address. Does the reverse proxy test at /proxy-test/ work and report all green?
Does sudo netstat -tulpen even still show the server as running? Does ps -ef | grep -i octoprint?
Tbh, this is an error case I've never seen before, and it sounds broken AF. You could try if ~/oprint/bin/pip --force-reinstall OctoPrint followed by a restart helps, but that's just a shout in the dark. Won't touch your data btw, just reinstall OctoPrint instead and hopefully clear up any possible corruption.
Other than that I'm out of ideas, the error behaviour doesn't make much sense tbh.
The e is a new switch for me but I see several ports listening and a curl at localhost:5000 shows the startup page that I get in the browser when I hit port 443.
Sadly the reinstall didn't bring anything back to life, maybe my SD card just silently died. I don't think I modified the haproxy config (at least not intentionally), but I'm not afraid to blow everything away, I just figured I'd ask since there were no errors and that seemed very bizarre.
Thank you for your help, I've been backing OctoPrint on patreon for a little while but signed up with the wrong email here (oops). I appreciate the support this community provides.
and then try connecting to your server at port 5000 from a browser. If that still fails, see if the browser's error console contains anything meaningful (F12).
But yeah, given that there are no errors getting logged, the server is running but apparently just not serving any requests anymore, and even a reinstall doesn't work, I'm a bit at a loss. It sounds like it might be stuck in serving the intermediary server from startup, but that should get stopped and the full server be fired up during start. You should be able to observe that through the log too.
Unfortunately my day job is in IT and I don't have the energy to troubleshoot this in too much depth after troubleshooting stuff all day at work. I ended up just nuking the install yesterday and starting fresh.
Thank you again. I'm not sure if I should mark this reply, noting a fresh install, as the solution or leave this unresolved since I didn't end up "fixing" the installation.
Totally understandable, I'm not much into debugging during my free time either thanks to having to do it enough during my full time work on OctoPrint
I took the liberty to mark your post as the solution as it is how you solved it, even though we didn't figure out the reason. I just hope things will work as they should from more on!
