sorry my fault, misunderstood your comment.
If I remember correctly, by default RealVNC is accepting connecting from own apps only. probably there will be an enhancement on next release.
All fine as Tiger is working again!! Thx for your help.
Good point with the changed TigerVNC config file. This is something we should add to our upgrade blog at least, i.e. if the “localhost no” line in /etc/vnc.conf exists, add it as well to the new default config. And a live patch can fix it in dietpi-software for v7.5, with v7.6 the regular fix is implemented already.
And it is correct, that by default RealVNC can only be connected via RealVNC clients/viewers. I just recently recognised that this is only because of a non-standard default authentication method, which can be changed. DietPi v7.6 will by default use the standard VncAuth authentication method with RealVNC, so from then on (new installs/reinstalls) it can be connected to with any VNC client. Sadly the encrypted TLSVnc authentication method is only supported with a paid subscription, else that would be a better default (with unencrypted VncAuth as fallback), like it is on TigerVNC.
Thx for the info!
I have problem either. After upgrade to Bullseye RealVNC does work but few days later it got some update and now I cant get it to work properly. I tried to reinstall RealVNC, LXDE, X11 and nothing.
Version of RealVNC
dietpi@DietPi:~$ dpkg -l | grep vnc
ii realvnc-vnc-server 6.7.4.43891 armhf VNC® Server
dietpi@DietPi:~$ sudo journalctl -u vncserver.service
Journal file /var/log/journal/cab0abe65ac44cfebf019c60286c4fd1/user-1000.journal is truncated, ignoring file.
-- Journal begins at Mon 2021-09-13 11:44:06 CEST, ends at Mon 2021-09-13 12:13: 55 CEST. --
Sep 13 11:44:29 DietPi systemd[1]: Started Manage VNC Server (DietPi).
Sep 13 11:44:29 DietPi systemd[652]: pam_unix(login:session): session opened for user root(uid=0) by (uid=0)
dietpi@DietPi:~$ sudo ss -tulpn | grep LISTEN
tcp LISTEN 0 50 0.0.0.0:139 0.0.0.0:* users:(("smbd",pid=721,fd=45))
tcp LISTEN 0 1024 192.168.192.2%eth0:61323 0.0.0.0:* users:(("zerotier-one",pid=589,fd=18))
tcp LISTEN 0 1024 0.0.0.0:80 0.0.0.0:* users:(("lighttpd",pid=930,fd=4))
tcp LISTEN 0 4096 192.168.192.2:8080 0.0.0.0:* users:(("php",pid=585,fd=4))
tcp LISTEN 0 1000 0.0.0.0:22 0.0.0.0:* users:(("dropbear",pid=655,fd=4))
tcp LISTEN 0 50 0.0.0.0:445 0.0.0.0:* users:(("smbd",pid=721,fd=44))
tcp LISTEN 0 1024 192.168.192.2%eth0:9993 0.0.0.0:* users:(("zerotier-one",pid=589,fd=14))
tcp LISTEN 0 1024 127.0.0.1:9993 0.0.0.0:* users:(("zerotier-one",pid=589,fd=6))
tcp LISTEN 0 1024 192.168.192.2%eth0:61322 0.0.0.0:* users:(("zerotier-one",pid=589,fd=16))
tcp LISTEN 0 50 [::]:139 [::]:* users:(("smbd",pid=721,fd=43))
tcp LISTEN 0 1024 [::]:80 [::]:* users:(("lighttpd",pid=930,fd=5))
tcp LISTEN 0 4096 *:53 *:* users:(("AdGuardHome",pid=584,fd=43))
tcp LISTEN 0 1000 [::]:22 [::]:* users:(("dropbear",pid=655,fd=5))
tcp LISTEN 0 4096 *:3000 *:* users:(("AdGuardHome",pid=584,fd=14))
tcp LISTEN 0 50 [::]:445 [::]:* users:(("smbd",pid=721,fd=42))
tcp LISTEN 0 1024 [::1]:9993 [::]:* users:(("zerotier-one",pid=589,fd=7))
vncserver.service status:
dietpi@DietPi:~$ sudo systemctl status vncserver.service -l
● vncserver.service - Manage VNC Server (DietPi)
Loaded: loaded (/etc/systemd/system/vncserver.service; enabled; vendor preset: enabled)
Active: active (exited) since Mon 2021-09-13 11:44:29 CEST; 32min ago
Process: 652 ExecStart=/usr/local/bin/vncserver start (code=exited, status=0/SUCCESS)
Main PID: 652 (code=exited, status=0/SUCCESS)
CPU: 26ms
Sep 13 11:44:29 DietPi systemd[1]: Started Manage VNC Server (DietPi).
Sep 13 11:44:29 DietPi systemd[652]: pam_unix(login:session): session opened for user root(uid=0) by (uid=0)
Thank you for help in advance
EDIT:
More logs:
dietpi@DietPi:~$ sudo journalctl -u vncserver-x11-serviced
Journal file /var/log/journal/cab0abe65ac44cfebf019c60286c4fd1/user-1000.journal is truncated, ignoring file.
-- Journal begins at Mon 2021-09-13 11:44:06 CEST, ends at Mon 2021-09-13 12:28:24 CEST. --
Sep 13 11:44:30 DietPi systemd[1]: Started VNC Server in Service Mode daemon.
Sep 13 11:44:30 DietPi vncserver-x11-serviced[719]: /usr/bin/vncserver-x11-core: error while loading shared libraries: libbcm_host.so: cannot open shared object file: No such file or directory
Sep 13 11:44:30 DietPi vncserver-x11-serviced[716]: vncserver-x11-serviced: Server exited with status 127, restarting in 5s
Sep 13 11:44:35 DietPi vncserver-x11-serviced[957]: /usr/bin/vncserver-x11-core: error while loading shared libraries: libbcm_host.so: cannot open shared object file: No such file or directory
Sep 13 11:44:35 DietPi vncserver-x11-serviced[716]: vncserver-x11-serviced: Server exited with status 127, restarting in 5s
Sep 13 11:44:40 DietPi vncserver-x11-serviced[958]: /usr/bin/vncserver-x11-core: error while loading shared libraries: libbcm_host.so: cannot open shared object file: No such file or directory
Sep 13 11:44:40 DietPi vncserver-x11-serviced[716]: vncserver-x11-serviced: Server exited with status 127, restarting in 5s
Sep 13 11:44:45 DietPi vncserver-x11-serviced[959]: /usr/bin/vncserver-x11-core: error while loading shared libraries: libbcm_host.so: cannot open shared object file: No such file or directory
Sep 13 11:44:45 DietPi vncserver-x11-serviced[716]: vncserver-x11-serviced: Server exited with status 127, restarting in 5s
Sep 13 11:44:50 DietPi vncserver-x11-serviced[984]: /usr/bin/vncserver-x11-core: error while loading shared libraries: libbcm_host.so: cannot open shared object file: No such file or directory
Sep 13 11:44:50 DietPi vncserver-x11-serviced[716]: vncserver-x11-serviced: Server exited with status 127, restarting in 5s
Sep 13 11:44:55 DietPi vncserver-x11-serviced[985]: /usr/bin/vncserver-x11-core: error while loading shared libraries: libbcm_host.so: cannot open shared object file: No such file or directory
Sep 13 11:44:55 DietPi vncserver-x11-serviced[716]: vncserver-x11-serviced: Server exited with status 127, restarting in 5s
Sep 13 11:45:00 DietPi vncserver-x11-serviced[988]: /usr/bin/vncserver-x11-core: error while loading shared libraries: libbcm_host.so: cannot open shared object file: No such file or directory
Sep 13 11:45:00 DietPi vncserver-x11-serviced[716]: vncserver-x11-serviced: Server exited with status 127, restarting in 5s
Sep 13 11:45:05 DietPi vncserver-x11-serviced[989]: /usr/bin/vncserver-x11-core: error while loading shared libraries: libbcm_host.so: cannot open shared object file: No such file or directory
Sep 13 11:45:05 DietPi vncserver-x11-serviced[716]: vncserver-x11-serviced: Server exited with status 127, restarting in 5s
Sep 13 11:45:10 DietPi vncserver-x11-serviced[990]: /usr/bin/vncserver-x11-core: error while loading shared libraries: libbcm_host.so: cannot open shared object file: No such file or directory
Sep 13 11:45:10 DietPi vncserver-x11-serviced[716]: vncserver-x11-serviced: Server exited with status 127, restarting in 5s
Sep 13 11:45:15 DietPi vncserver-x11-serviced[991]: /usr/bin/vncserver-x11-core: error while loading shared libraries: libbcm_host.so: cannot open shared object file: No such file or directory
Sep 13 11:45:15 DietPi vncserver-x11-serviced[716]: vncserver-x11-serviced: Server exited with status 127, restarting in 5s
Sep 13 11:45:20 DietPi vncserver-x11-serviced[992]: /usr/bin/vncserver-x11-core: error while loading shared libraries: libbcm_host.so: cannot open shared object file: No such file or directory
Sep 13 11:45:20 DietPi vncserver-x11-serviced[716]: vncserver-x11-serviced: Server exited with status 127, restarting in 5s
Sep 13 11:45:25 DietPi vncserver-x11-serviced[993]: /usr/bin/vncserver-x11-core: error while loading shared libraries: libbcm_host.so: cannot open shared object file: No such file or directory
Sep 13 11:45:25 DietPi vncserver-x11-serviced[716]: vncserver-x11-serviced: Server exited with status 127, restarting in 5s
Sep 13 11:45:30 DietPi vncserver-x11-serviced[994]: /usr/bin/vncserver-x11-core: error while loading shared libraries: libbcm_host.so: cannot open shared object file: No such file or directory
Sep 13 11:45:30 DietPi vncserver-x11-serviced[716]: vncserver-x11-serviced: Server exited with status 127, restarting in 5s
Sep 13 11:45:35 DietPi vncserver-x11-serviced[995]: /usr/bin/vncserver-x11-core: error while loading shared libraries: libbcm_host.so: cannot open shared object file: No such file or directory
Sep 13 11:45:35 DietPi vncserver-x11-serviced[716]: vncserver-x11-serviced: Server exited with status 127, restarting in 5s
Sep 13 11:45:40 DietPi vncserver-x11-serviced[996]: /usr/bin/vncserver-x11-core: error while loading shared libraries: libbcm_host.so: cannot open shared object file: No such file or directory
Sep 13 11:45:40 DietPi vncserver-x11-serviced[716]: vncserver-x11-serviced: Server exited with status 127, restarting in 5s
Sep 13 11:45:45 DietPi vncserver-x11-serviced[997]: /usr/bin/vncserver-x11-core: error while loading shared libraries: libbcm_host.so: cannot open shared object file: No such file or directory
Sep 13 11:45:45 DietPi vncserver-x11-serviced[716]: vncserver-x11-serviced: Server exited with status 127, restarting in 5s
Sep 13 11:45:50 DietPi vncserver-x11-serviced[998]: /usr/bin/vncserver-x11-core: error while loading shared libraries: libbcm_host.so: cannot open shared object file: No such file or directory
Sep 13 11:45:50 DietPi vncserver-x11-serviced[716]: vncserver-x11-serviced: Server exited with status 127, restarting in 5s
Sep 13 11:45:55 DietPi vncserver-x11-serviced[999]: /usr/bin/vncserver-x11-core: error while loading shared libraries: libbcm_host.so: cannot open shared object file: No such file or directory
Sep 13 11:45:55 DietPi vncserver-x11-serviced[716]: vncserver-x11-serviced: Server exited with status 127, restarting in 5s
Sep 13 11:46:00 DietPi vncserver-x11-serviced[1000]: /usr/bin/vncserver-x11-core: error while loading shared libraries: libbcm_host.so: cannot open shared object file: No such file or directory
Sep 13 11:46:00 DietPi vncserver-x11-serviced[716]: vncserver-x11-serviced: Server exited with status 127, restarting in 5s
Sep 13 11:46:05 DietPi vncserver-x11-serviced[1001]: /usr/bin/vncserver-x11-core: error while loading shared libraries: libbcm_host.so: cannot open shared object file: No such file or directory
Sep 13 11:46:05 DietPi vncserver-x11-serviced[716]: vncserver-x11-serviced: Server exited with status 127, restarting in 5s
Sep 13 11:46:10 DietPi vncserver-x11-serviced[1002]: /usr/bin/vncserver-x11-core: error while loading shared libraries: libbcm_host.so: cannot open shared object file: No such file or directory
Sep 13 11:46:10 DietPi vncserver-x11-serviced[716]: vncserver-x11-serviced: Server exited with status 127, restarting in 3600s
Hi,
this is a side effect of RPi devs changed name/location of some important files. It’s caused by update of apt package libraspberrypi0. Unfortunetaly something out of our control. But we might have a workaround until RPi devs fixed their packages.
cd /usr/lib/arm-linux-gnueabihf
ln -s libmmal_core.so.0 libmmal_core.so
ln -s libmmal_util.so.0 libmmal_util.so
ln -s libmmal_vc_client.so.0 libmmal_vc_client.so
ln -s libbcm_host.so.0 libbcm_host.so
ln -s libvcsm.so.0 libvcsm.so
ln -s libvchiq_arm.so.0 libvchiq_arm.so
ln -s libvcos.so.0 libvcos.so
systemctl restart vncserver-x11-serviced
Now it’s something like that:
Journal file /var/log/journal/cab0abe65ac44cfebf019c60286c4fd1/user-1000.journal is truncated, ignoring file.
-- Journal begins at Mon 2021-09-13 13:16:24 CEST, ends at Mon 2021-09-13 13:17:22 CEST. --
Sep 13 13:16:52 DietPi systemd[1]: Started VNC Server in Service Mode daemon.
Sep 13 13:16:53 DietPi vncserver-x11[738]: ServerManager: Server started
Sep 13 13:16:53 DietPi vncserver-x11[738]: ConsoleDisplay: Cannot find a running X server on vt1
Still cant connect
dietpi@DietPi:~$ sudo ss -tulpn | grep LISTEN
tcp LISTEN 0 50 0.0.0.0:139 0.0.0.0:* users:(("smbd",pid=721,fd=45))
tcp LISTEN 0 1024 192.168.192.2%eth0:61323 0.0.0.0:* users:(("zerotier-one",pid=591,fd=18))
tcp LISTEN 0 5 0.0.0.0:5900 0.0.0.0:* users:(("vncserver-x11-c",pid=738,fd=11))
tcp LISTEN 0 1024 0.0.0.0:80 0.0.0.0:* users:(("lighttpd",pid=965,fd=4))
tcp LISTEN 0 4096 192.168.192.2:8080 0.0.0.0:* users:(("php",pid=587,fd=4))
tcp LISTEN 0 1000 0.0.0.0:22 0.0.0.0:* users:(("dropbear",pid=658,fd=4))
tcp LISTEN 0 50 0.0.0.0:445 0.0.0.0:* users:(("smbd",pid=721,fd=44))
tcp LISTEN 0 1024 192.168.192.2%eth0:9993 0.0.0.0:* users:(("zerotier-one",pid=591,fd=14))
tcp LISTEN 0 1024 127.0.0.1:9993 0.0.0.0:* users:(("zerotier-one",pid=591,fd=6))
tcp LISTEN 0 1024 192.168.192.2%eth0:61322 0.0.0.0:* users:(("zerotier-one",pid=591,fd=16))
tcp LISTEN 0 50 [::]:139 [::]:* users:(("smbd",pid=721,fd=43))
tcp LISTEN 0 5 [::]:5900 [::]:* users:(("vncserver-x11-c",pid=738,fd=10))
tcp LISTEN 0 1024 [::]:80 [::]:* users:(("lighttpd",pid=965,fd=5))
tcp LISTEN 0 4096 *:53 *:* users:(("AdGuardHome",pid=586,fd=43))
tcp LISTEN 0 1000 [::]:22 [::]:* users:(("dropbear",pid=658,fd=5))
tcp LISTEN 0 4096 *:3000 *:* users:(("AdGuardHome",pid=586,fd=41))
tcp LISTEN 0 50 [::]:445 [::]:* users:(("smbd",pid=721,fd=42))
tcp LISTEN 0 1024 [::1]:9993 [::]:* users:(("zerotier-one",pid=591,fd=7))
EDIT:
I’m idiot. its running now. Only on port 5900, not 5901.
EDIT2:
To make it work I had to change in addition:
ln -s libmmal.so.0 libmmal.so
ln -s libcontainers.so.0 libcontainers.so
ln -s libmmal_components.so.0 libmmal_components.so
Unfortunately it cant display the desktop. As the graphic environment doesnt work.
After connect I have black screen with text:
“Cannot currently show the desktop”
usually Port 5900 is used while having set desktop as autostart
And it might be a problem?
EDIT:
Ok. I disabled autostart and it works again on port 5901 and everything is ok. I can connect with no problem to LXDE. Thank you for help
if not needed, better not to start into a desktop as it will save system resources 