Anyone have any input?
HW is raspberry pi 4B various memory levels
SW is Pi OS 64 bit standard install and VNC server. Bookworm
So, I've confirmed it has happened on at least two separate boards.
If I change the VNC port to what i needed (in this case 37780) the board still boots fine, when you connect via VNC the screen is black, not dead, just black with an active mouse. Happened to have one of them already logged into RPI connect so I tried that. I could get to it that way, moving the mouse on the PRI connect screen was reflected on the black VNC session.
If I change the VNC port back to 5900 VNC works fine. There are no port and firewall issues as the devices are on the same lan in a build setup scenario before deployment.
Is rpi connect messing with VNC or is vnc broken when you change the port? Any ideas?
I'll try it on a 5 and update as well.
HW is raspberry pi 4B various memory levels
SW is Pi OS 64 bit standard install and VNC server. Bookworm
So, I've confirmed it has happened on at least two separate boards.
If I change the VNC port to what i needed (in this case 37780) the board still boots fine, when you connect via VNC the screen is black, not dead, just black with an active mouse. Happened to have one of them already logged into RPI connect so I tried that. I could get to it that way, moving the mouse on the PRI connect screen was reflected on the black VNC session.
If I change the VNC port back to 5900 VNC works fine. There are no port and firewall issues as the devices are on the same lan in a build setup scenario before deployment.
Is rpi connect messing with VNC or is vnc broken when you change the port? Any ideas?
I'll try it on a 5 and update as well.
Statistics: Posted by libram11 — Sat Jun 22, 2024 4:29 am