Closed PatMis16 closed 2 years ago
I don't think this is really an OctoPi issue, but more one with the Raspberry Pi OS image that it is built on. You should test if you have the same issue with Raspberry Pi OS, instead of OctoPi. It is a newer image, so if you want to test like-for-like test a nightly build of OctoPi as well.
A quick check of Google actually showed that a 169.x address would be assigned when the computer cannot connect to the network. So you should check that that's configured correctly as well. If you need help with that, reach out on the OctoPrint community forums or discord server.
Can this be closed? was it solved?
Hi Guy
Yes, this can be closed.
Regards, Patrick
Von meinem iPhone gesendet
Am 10.11.2021 um 21:17 schrieb Guy Sheffer @.***>:
Can this be closed? was it solved?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.
What were you doing?
I could not successfuly connect to the RPI either through ssh nor http.
What did you expect to happen?
The interface eth0 gets an IP assigned by DHCP in the given range.
What happened instead?
DHCP did not work properly, when assigning a fixed IP the octoPi was not accessible either.
Did the same happen when running OctoPrint in safe mode?
Did not run OctoPrint in safe mode, since it is not accessible in the first place.
Version of OctoPi
0.18.0
Printer model & used firmware incl. version
I intend to use it with a Creality Ender 3 V2.
Screenshot(s)/video(s) showing the problem:
None
I have read the FAQ.