guysoft
commented
2 years ago I have no Raspberry Pi Zero 2 to test this :-/
The only thing I can say is that if I look at https://data.octoprint.org/ I see that about 2500+ people managed to run OctoPi on a Raspberry Pi Zero 2 W. But it might be a different rev than the one you have. So I would look if this also happens on stock RaspberryPi image, because it might be the hardware.
Hello!
I have a Raspberry Pi Zero 2 W on which I have recently installed Octopi. It is attached to the back of an Prusa I3 MK3 board via the method described here.
My Wifi is correctly set up and working.
When the Raspberry boots, it connectes via Wifi and pulls an IP address via DHCP, which I can see in the router. However, Octopi will at this point not yet respond. This means no ping responses and no web interface either. It will stay in this state for hours unless I intervene.
The only way to get it to respond is to continuously ping it for 20-40 seconds. Eventually pings start coming back. At this point the web interface also works. Octopi will continue to respond normally until it is completely rebooted (not just Octoprint being restarted)
This is a weird bug that I cannot explain. The Pi is connected (or it couldn't pull DHCP) but refusing incoming connections. An iptables issue? Why would it start responding after ping bombardements? And since pings are also affected, this must be a system-wide issue, not one limited to Octoprint itself.
Any ideas? Thanks!
What were you doing?
What did you expect to happen?
Pi responds
What happened instead?
No response
Did the same happen when running OctoPrint in safe mode?
Octoprint itself is not responsible, it's a system-wide networking issue. Therefore I haven't tested safe mode.
Version of OctoPi
OctoPrint 1.7.3 Python 3.7.3 OctoPi 0.18.0
Printer model & used firmware incl. version
Prusa i3 Mk3
I have read the FAQ.