Downloaded Octoprint dated 10/1/25. Flashed memory card [3x]. Rasp 400 boots up, indicates 192.168.1.35 I can access pi via Putty, but not with any W10 browsers [chrome, edge, firefox] and not with iPhone. octopi.local = can't connect, 192.168.1.35 = can't connect. pi has internet access. Computer has internet. Router indicates pi at 192.168.1.35 but it is not working. Any ideas?
From another computer on your network, try and "ping" the ip address 192.168.1.35, (in a terminal \ command \ powershell window) if that works try "telnetting" to the host's ip address on ports 22, 80 and 443.
Using the above will at least show that the Octopi host is alive....
Even if ssh & telnet are disabled on the pi you should still be able to ping & telnet ports 80\443 etc. from another computer on the network, even the default router may have some basic tools installed, the check on connectivity to the OctoPi host....
b-morgan, thank you for your reply. There is no haproxy folder, no haproxy file that I can locate. I can upload the netstat file. But I think the problem is the other.
okay, I'm confused. I pulled the memory card [after shutting down the pi]. When I put it in the W10 computer, the files and folders are not the same as they were on the pi. What am I not getting? How do I locate these files and transfer them over?
I am able to connect via _http_s://connect.raspberrypi.com/devices. [had to insert _ to keep it from converting the web address.] I can access the pi and perform tasks from my W10 computer. But I can not get octopi.local to connect.
The microSD card is formatted with two partitions. A small FAT32 partition and the rest of the card is a Linux partition. The root (/) of the filesystem is on the Linux partition and the /boot (or /boot/firmware) directory is on the small partition. Windows can see the FAT32 partition but it can't (without additional apps) see the Linux partition.
IMO, the easiest way to transfer files to/from the RPi is to use WinSCP. This uses the SSH credentials and can see the entire filesystem.
To post text here that you don't want the markdown to (attempt to) interpret, use the </> preformatted text icon above.
So now to the actual issue, there is no haproxy and the RPi is not listening on any HTTP ports.
I just looked in the RPi Imager (1.9.6) and neither OctoPi image is dated 2025-10-1 so I must ask, exactly where did you get the image you flashed? I suggest that you start over with the "OctoPi (stable)" image. If you have one, use a different microSD card. I also suggest that you use the username "pi" with a password of your choice.
When you first boot the RPi 400 with a fresh card, it will do some initial setup which includes a couple of reboots. Give it time to do that.
Have to agree with @b-morgan here, that definitely doesn't sound like you flashed an OctoPi image to begin with (or possibly some broken nightly?), which would explain the issues.