@bls Looks like the key line is "no trusted certificates found." The problem is clearly on the desktop end, not the Pi end. I've removed and re-established the ssh key twice, with no improvement.
Discussion
Loading...
Post
Is the laptop going over wifi and the desktop is going over ethernet and the networks aren't bridged?
@MegaMichelle You're very close. The desktop is on ethernet, and the laptop is on wifi... but I can ssh from the desktop to the Pi using the same local IP address.
What happens if you telnet to the port that VNC is running on? Can you connect, or does the network firewall you out?
If you can connect, then VNC might have some kind of thing that's keeping you out. Allowlist or something?
If the network keeps you out: Maybe the bridge from ethernet to wifi only allows certain ports?
@MegaMichelle I haven't used telnet in 25 years. But, it didn't matter. The Pi didn't recognize it.
I did a factory reset and ended up with Trixie-based RPOS. Same thing: the laptop connects fine, and I can ssh from the desktop, but I can't VNC from the desktop. What I have learned is that the desktop doesn't trust the certificate. On the laptop, it asked me to accept the validity of the Pi's certificate, and again when I ssh'd from the desktop, but no VNC apps asked for that on the desktop.
@Steve It means it's time to check the logs on the #raspberrypi for hints for starters.
@bls Looks like the key line is "no trusted certificates found." The problem is clearly on the desktop end, not the Pi end. I've removed and re-established the ssh key twice, with no improvement.
@Steve Uh...what does an SSH key have to do with VNC? What VNC server are you running on the #raspberrypi
@Steve and what is the error?
bonfire.cafe
A space for Bonfire maintainers and contributors to communicate
Automatic federation enabled