I'm trying to set up my Raspberry Pi 4 as a streaming server but ran into a problem after configuring a static IP using nmtui. Initially, I was able to access the Pi via SSH after some manual configurations, but I decided to switch the IP from 192.168.1.32 to 192.168.1.34 to make it static. After setting everything up and rebooting, I lost connection, and now I get a 'no route to host' error. I've attempted to connect via Ethernet, but it switched back to the old IP and still won't allow any connections. I can't access my landlord's router to check if the Pi shows up there, and I can't find where the nmtui configuration files are to edit them. I also don't have an HDMI cable to directly connect to the Pi. I'm open to any suggestions for fixing this without needing access to the router, as I really want to recover my setup after spending so long on it!
2 Answers
It sounds like a tricky situation! First, I'd recommend checking your router settings if you get access. Sometimes devices might not show up if they are on a different subnet. If you can’t do that, you could try taking out the SD card and using another machine to access it—this way, you can look for the network configuration files. They’re usually in `/etc/NetworkManager/system-connections/`. You might be able to change the settings back to DHCP to regain access. Good luck!
If you've got no access to the router, then modifying the SD card is your best bet. Once you have it mounted on another computer, look for the `/etc/dhcpcd.conf` file. You should be able to find and remove any static IP configurations you set up using nmtui. Then just put the card back in and try booting the Pi again—it should revert to dynamic IP settings! Let us know how it goes!
Related Questions
Google Nest Doorbell Not Alerting Google Hub Or Google Mini
Can't Rename Google Nest Doorbell