After switching from Wayland to RealVNC in the advanced menu, the log shows it tried and failed to connect. Not sure why it didn't work.
I'm using TightVNC as the client.
Code:
● vncserver-x11-serviced.service - VNC Server in Service Mode daemon Loaded: loaded (/lib/systemd/system/vncserver-x11-serviced.service; enabled; preset: enabled) Active: active (running) since Fri 2024-05-10 20:13:15 PDT; 12min ago Main PID: 725 (vncserver-x11-s) Tasks: 5 (limit: 1576) CPU: 572ms CGroup: /system.slice/vncserver-x11-serviced.service ├─ 725 /usr/bin/vncserver-x11-serviced -fg ├─ 752 /usr/bin/vncserver-x11-core -service ├─ 810 /usr/bin/vncagent service 0 ├─1191 /usr/bin/vncserverui service 0 └─1234 /usr/bin/vncserverui -statusicon 0May 10 20:13:15 RPi4-CNC systemd[1]: Started vncserver-x11-serviced.service - VNC Server in Service Mode daemon.May 10 20:13:16 RPi4-CNC vncserver-x11[752]: ServerManager: Server startedMay 10 20:13:16 RPi4-CNC vncserver-x11[752]: ConsoleDisplay: Cannot find a running X server on vt1May 10 20:13:16 RPi4-CNC vncserver-x11[752]: ConsoleDisplay: Found running X server (pid=785, binary=/usr/lib/xorg/Xorg)May 10 20:14:21 RPi4-CNC vncserver-x11[752]: Connections: connected: 192.168.0.182::57379 (TCP)May 10 20:14:22 RPi4-CNC vncserver-x11[752]: Connections: disconnected: 192.168.0.182::57379 (TCP) ([EndOfStream] Disconnection by client)Statistics: Posted by bkenobi — Sat May 11, 2024 3:27 am