Raspberry Pi Connect uses its own self-contained WayVNC server instance with its own configuration file (/etc/rpi-connect/wayvnc.config which is intentionally empty, see the systemd unit in /usr/lib/systemd/user/rpi-connect-wayvnc.service for full details). It only binds to a UNIX socket rather than a port so it shouldn't interfere with any other VNC servers that typically run on port 5900.The only drawback, save for my android keyboard not triggering as already reported, is that my other VNC access seems to be no longer working. I'm genuinely confused how that works, but I'm definitely no expert. I suspect a setting changed as part of the setup process, but I don't quite know how to fix it back up.
The VNC server controlled by raspi-config has its configuration stored in /etc/wayvnc/config so I'd start there and look at the output from the system WayVNC service with:
Code:
sudo journalctl --unit wayvnc.serviceStatistics: Posted by paulmu — Fri May 10, 2024 6:37 am