![]() ![]() No network issues for a continuous period of 70 days. UPDATE: I have connected four rpi4s to a hub, and the hub uplink port with a wired connection to a Linksys Velop satellite node. I know that does not help right now if you can’t VNC or SSH into your system. This seems to help, but it occasionally goes down. I also run a cron job and script to check if the WiFi is down and reconnect. So.my suggestion is to connect your rpi to your router by cable, or to run 1-2 backup rpi (could use zero’s for this) on a cheap Ethernet hub so you can reboot if one goes down. ![]() (I am running a Velops mesh system with reserved WiFi IP addresses for each pi). Connecting via RealVNC cloud does not necessarily mean that the traffic is routed via the internet - If the machines are on the same network it should automatically figure this out and route the data locally. I suspect it is due to instability in the WiFi daemon in Raspbian Buster, as the hardwired connection never drops. I have been troubleshooting this for a couple of months, and don’t yet have a definitive answer. I know the rpi4 itself is still running as I can ssh to it via a wired connection (all the rpi4s are on both WiFi and a separate hardwired Ethernet subnet via an independent router). I know RealVNC is up, because I can reach the other 3. RealVNC seems to go down somewhat randomly on the four rpis, but much less frequently on the one running the python routine. I have a 3 x rpi4 cluster and a single rpi4 running a python routine to monitor a wine cabinet. I have the same problem, and I don’t think it is the RealVNC servers, but rather the WiFi connection dropping and not restarting. At this point I think I might just be screwed, so if anyone could explain in the comments why VNC likes to commit death when I need it not to (maybe I need to have my pi automatically reboot daily?) that would still help. Other internet-connected features on the pi were still working, although the only one I have access to has crashed due to (I assume) unfinished code changes.ĭoes anyone have any ideas why this happened, or how to remotely troubleshoot this with no portforwarding or SSH? I cannot try rebooting or doing anything that uses keyboard+mouse because I am 100 miles away and cannot return.Ĭlarification: The remote place IS my home and the only key-holders closer to my home than me are computer illiterate. A couple of attempts later, the connection failed with a message: "VNC Server is not currently listening for Cloud connections." The client (running on windows) suddenly froze, like it often does, so I disconnected and tried to re-connect, only to find it refused. After that, we need to check If we have disabled cloud connections in VNC Server’s Options dialog, under the Connections heading. I'm currently 100 miles away from said Raspberry Pi, and it's suddenly stopped listening for cloud connections through no intervention of my own. The remote computer is not connected to the Internet 2. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |