VNC stopped working

[Rapid1981]

Hello!
The VNC on my RPI stopped working after I installed the Allsky system.
Is it intentional or something went wrong?
I tried a few fixes, resetting VNC resolution, reinstalling packages, but no solution so far.

And another, not related question:
Is it possible to have a remote website without the local one?

Thanks!

[EricClaeys]

@Rapid1981 Allsky doesn't change networking, although if this is the first time you installed Allsky on this Pi the host name probably changed to "allsky", which may have impacted VNC.

Yes, you can install a remote Website without a local one. Look at the installation instructions for how.

[Rapid1981]

And if both websites are installed already, how can I remove the local one?

[EricClaeys]

@Rapid1981, to remove it:

# In the "Editor" page of the WebUI, select "ftp-settings.sh".
# Set the `WEB_*_DIR` variables to "".  For example, `WEB_KEOGRAMS_DIR=""`).

# Make sure you don't want any saved images.  It's in ~/allsky/html/allsky.
cd ~/allsky/html
rm -fr allsky
~/allsky/scripts/check_allsky.sh
# This will tell you if there are any problems with your settings.

FYI, in the next major release of Allsky, the local Website will be part of Allsky since it's only 2 MB (without images).  There will be a signle on/off switch in the WebUI for it.  No other settings will be needed.

[Rapid1981]

The solution to the VNC was the hdmi_force_hotplug=1, so it's not related to allsky at all.

Thank you for the removal solution of the local website.

[EricClaeys]

@Rapid1981, I think other people have had the same experience, so I'd like to understand it better. How did hdmi_force_hotplug get set to 0? Did the problem happen after the Allsky installation and reboot, or was it a while later? Any other info?

[Rapid1981]

The hdmi_force_hotplug=1 originally was commented out in the config.txt, but the VNC worked without any issue prior to the Allsky installation.
I don't know what changed during the installation, but after the reboot the VNC only gave me the "Cannot currently show the desktop" error.
I even tried xrdp, but that also gave me a "Cannot connect to display 0" error.

I removed the # in front of the hdmi_force_hotplug=1 in the config.txt, set the hdmi_group and hdmi_mode and now it's working flawlessly.

[EricClaeys]

Interesting, given that HDMI is for the display port on the Pi. All my "hdmi" entries in config.txt are commented out on my Bullseye system but UNcommented on my Buster Pi. Do you have Bullseye or Buster?

[Rapid1981]

I'm using Bullseye.