Virtualhere Cloudhub suddenly not found anymore by client

Submitted by Jiheffe on #1

So I am running Virtualhere Cloudhub successfully on a Raspberry PI 4 for a couple of weeks and all of of a sudden, it is not found anymore by the client on my Mac. I can still ping it succesfully,  so it is on the network. I tried to ssh into it with no user and no password, but I'm getting rejected. Also power cycled the Pi and the Mac with the client.

I already had the same issue a couple of months ago and solved it by reflashing the firmware on the SD card, but would like to avoid it this time. What can I do ?

Submitted by Michael on Sat, 2026/04/25 - 08:47

#2

Put user of root and no password see if you can login via ssh. Then type ifconfig and see what ip addresses it has

Submitted by Jiheffe on Tue, 2026/04/28 - 02:47

#3

Thank you. I knew the IP address, but I could'nt ssh in to the device to see if something was wrong. ssh with root and no password worked, thnx !

As to my initial problem: for some reason I still need to investigate, the server was not found automtically anymore by the clients. But configuring it's IP address in the clients solved the problem.

Submitted by Michael on Tue, 2026/04/28 - 08:41

#4

I notice sometimes with MacOS updates it blocks apps again. Can you check MacOS Settings->Privacy And Security -> Local Network and make sure VirtualHereUniversal is listed under there.

 

Submitted by Jiheffe on Tue, 2026/04/28 - 16:31

#5

Hi Michael,

There is no VirtualHereUniverdsal entry in Privacy And Security -> Local Network.
For info, I installed VirtualHere as a service.

But, as I said, I solved the issue by specifying the USB server manually.
It was working before, but I have made changes to my network recently, and the server is now on a different subnet than the clients. I have set up mDNS repeater in OPNsense on the router to bridge mDNS between the VLANs. I don't know how the VirtualHere clients discover the servers. As it works now, it's not a firewall issue between subnets.

I use VirtualHere to access a printer and card reader that I don't use every day, so maybe a change in network architecture a couple of days ago broke the discovery.
But a recent MacOS update may also have broken something. 


When I have some time, I may move the server to the same subnet as the clients and see how it works.


JF

Submitted by Michael on Tue, 2026/04/28 - 16:50

#6

If its on a different subnet it wont auto-find because UDP broadcasts are only done on the local subnet so its actually working as expected :)

Virtualhere Server broadcasts its existence on the network using Bonjour/mDNS/avahi and the virtualhere client listens for those broadcasts. This goes over UDP 5353