I have recently bought a Raspberry Pi 4B to start a series of personal projects of self hosting some applications. Since I was planning to completely use the PI with remote connections, when writing the Raspbian OS to the SD card, I made sure to enable SSH. As soon as I SSH'ed into the PI, I didand enabled the VNC service. Everything was going well: I could connect to the PI with both SSH and VNC. At this point I should mention that I am controlling the PI from a laptop, which has a dualboot of Windows 11 and Debian 12. On Windows, I use Putty (for SSH) and Tiger VNC (for VNC), whereas on the Debian system I use the terminal and again Tiger VNC.
With this setup, I had managed to put up a very simple Vaultwarden service. I then decided to make it more robust by setting up my own WireGuard VPN so that I could limit the access of my Vaultwarden service only to devices connected on my VPN. After successfully (I think) setting up my WireGuard VPN, is when I noticed that suddenly I could no longer use VNC services to connect to my Raspberry Pi. I don't know if that was a coincidence or not, but since I was messing with IP addresses and such with WG, I thought that maybe that's what had caused VNC not to work anymore. Anyway, I decided to disable WG and all the Docker processes I had running (Vaultwarden and Caddy) to see if that would make VNC work again. No luck. I could no longer use Tiger VNC to connect to my Raspberry Pi (from either the Windows or Debian systems). I have tried to make the connection with the same IP address as before, but I am always granted with a 10060 error after some time. SSH still works (from both systems) using the same IP address as before.
I have searched online for a solution, but failed to find anything that described my exact problem. What I have tried so far:
1) I made sure that the local IP address of my PI is still the same (I checked the list of connected devices on my router's configuration page);
2) I have checked that the wayvnc service is up and listening to the default 5900 port on my PI using which returned3) I have checked that the wayvnc service does exist using which returned4) I have tried another VNC viewer service on my Windows system (RealVNC Viewer) but the same time-out error occurs;
5) I have tried disabling and enabling VNC with. I have also tried rebooting the PI and my laptop;
6) I even tried starting a new wayvnc server on my Raspberry PI, but this time on a different port, but again I am not able to connect to it;
7) Finally, I tried accessing the help menu of wayvnc but I found it very limited. I also couldn't find an oficial documentation for it, so if anyone can point me to a more extensive document on its workings that would be much appreciated.
To wrap-up, I would also like to add I do not have any formal background on any of this. I am just messing around, following forums and YouTube guides, so apologies if anything I have wrote is not exactly correct, so feel free to correct me! Has anyone been through this issue before or have any ideas on what I could try next?
Many thanks.
Code:
sudo raspi-configWith this setup, I had managed to put up a very simple Vaultwarden service. I then decided to make it more robust by setting up my own WireGuard VPN so that I could limit the access of my Vaultwarden service only to devices connected on my VPN. After successfully (I think) setting up my WireGuard VPN, is when I noticed that suddenly I could no longer use VNC services to connect to my Raspberry Pi. I don't know if that was a coincidence or not, but since I was messing with IP addresses and such with WG, I thought that maybe that's what had caused VNC not to work anymore. Anyway, I decided to disable WG and all the Docker processes I had running (Vaultwarden and Caddy) to see if that would make VNC work again. No luck. I could no longer use Tiger VNC to connect to my Raspberry Pi (from either the Windows or Debian systems). I have tried to make the connection with the same IP address as before, but I am always granted with a 10060 error after some time. SSH still works (from both systems) using the same IP address as before.
I have searched online for a solution, but failed to find anything that described my exact problem. What I have tried so far:
1) I made sure that the local IP address of my PI is still the same (I checked the list of connected devices on my router's configuration page);
2) I have checked that the wayvnc service is up and listening to the default 5900 port on my PI using
Code:
sudo netstat -tulpn | grep :5900Code:
tcp6 0 0 :::5900 :::* LISTEN 3059/wayvncCode:
ps -ef | grep vncCode:
vnc 3040 1 0 10:53 ? 00:00:00 /bin/sh /usr/sbin/wayvnc-run.shvnc 3059 3040 0 10:53 ? 00:00:00 wayvnc --detached --gpu --config /etc/wayvnc/config --socket /tmp/wayvnc/wayvncctl.sockroot 3071 1 0 10:53 ? 00:00:00 python /usr/sbin/wayvnc-control.pyPIngo 3118 2801 0 10:54 pts/1 00:00:00 grep --color=auto vnc5) I have tried disabling and enabling VNC with
Code:
sudo raspi-config6) I even tried starting a new wayvnc server on my Raspberry PI, but this time on a different port, but again I am not able to connect to it;
7) Finally, I tried accessing the help menu of wayvnc but I found it very limited. I also couldn't find an oficial documentation for it, so if anyone can point me to a more extensive document on its workings that would be much appreciated.
To wrap-up, I would also like to add I do not have any formal background on any of this. I am just messing around, following forums and YouTube guides, so apologies if anything I have wrote is not exactly correct, so feel free to correct me! Has anyone been through this issue before or have any ideas on what I could try next?
Many thanks.
Statistics: Posted by camalazeon — Wed Jul 23, 2025 3:03 pm — Replies 2 — Views 63