I cannot access the web interface for Octoprint. My browser gives the error:
Unable to connect
Firefox can’t establish a connection to the server at 100...___:5000
The Pi has access to the Internet, and I can SSH into it fine. I followed the instruction from tedder42 here No web interface to try curl http://localhost:5000 and curl http://localhost:80 to see if the interface was running locally and got code output (not errors), which according to that post means that it was running.
What did you already try to solve it?
Attempted to reach the webpage in Firefox, Chrome, and Edge
Restarted octoprint (sudo systemctl restart octoprint)
Reflashed Octopi (new camera stack)
Reflashed with Octopi (stable)
(This was also on a different SD card)
Switched power supplies
Running the latest version of Octopi (New camera stack) on a Raspberry Pi 4B flashed with the Raspberry Pi Imager.
Connected to network with onboard WiFi.
Power supply is a Canakit 5V 3.5A unit.
Connecting from a Windows 10 machine via a Tailscale connection (I have to deal with multiple networks, this is pretty essential).
I'm trying to switch over to this setup from a Windows machine running Octoprint which has never had similar issues.
Sorry for the confusion. No, I did that in the Pi's command line to see if the HTML for the webpage existed. To get to the interface, http://(ip address):5000 in a browser.
To get the logs, I was following foosel's guide here: Where can I find OctoPrint's and OctoPi's log files?
I tried generating the systeminfo bundle with the instructions you've linked to. When I input
sudo ~/oprint/bin/octoprint systeminfo .
I get no output to the command line, and I can't find a zip in the listed directory.
However, I just realized I can zip the syslog file myself, so I've updated my original post with that.
Okay, so I tried reinstalling OctoPi again, and when that didn't change anything, I installed the desktop environment to access the webpage from the Pi directly. From the Pi, I am able to reach the web interface, though I still can't remotely.
Also, I just thought to check - from on the pi, I can reach the web interface only if I use "localhost", "127.0.0.1", or "octopi.local". If I use the wlan IP address or the Tailscale IP I can't reach the web interface even from on the Pi.
Absolutely not. Being on a different numbered port to port 80 just means that it takes longer to type the URL. If you directly exposed it to the outside world, one can scan open ports almost instantly, so then they'd know it was at 5000.
OctoPi comes with a reverse proxy called Haproxy. This means that both OctoPrint and the webcam server can be both hosted on port 80, not 5000 and 8080 separately. So you can access the webcam under /webcam/, and then also use a relative URL for that configuration - you wouldn't have to change the URL if the IP address changed for example. Additionally, I believe it does do a bit of extra compression of the requests. Nothing strictly necessary, but all QoL features.