I keep getting following error. Could you help? Trying to connect via TigerVNC from Windows 10 to Amazon Linux 2. Putty connections works just fine.
2023-03-22 16:21:35 Opening connection to localhost:5901 for forwarding from [::1]:62131
2023-03-22 16:21:35 Forwarded connection refused by remote: Connect failed [Connection refused]
Thank you for your comment. We'll review and update the Knowledge Center article as needed.
I have followed all instructions in this article, but when I connect via TigerVNC I get an empty screen. Meaning, the connection is successful but nothing appears on screen.
I am running CIS Amazon Linux 2 Kernel 5.10 Benchmark v1.0.0.14 - Level 1-abcfcbaf-134e-4639-a7b4-fd285b9fcf0a (ami ID ami-0547e646fff07d3e3)
Thank you for your comment. We'll review and update the Knowledge Center article as needed.
This guide is outdated. amazon-linux-extras no longer exists in Amazon Linux 2023
Thank you for your comment. We'll review and update the Knowledge Center article as needed.
Is there an updated quide?
Thank you for your comment. We'll review and update the Knowledge Center article as needed.
Tried using the latest AMI with MATE desktop connection but the GLIBC libraries are at 2.26 which is too old not not a viable solution
Thank you for your comment. We'll review and update the Knowledge Center article as needed.
Hello, we have a AMI product providing GUI desktop that can be found at https://aws.amazon.com/marketplace/pp/prodview-qxpguux4j23ns?sr=0-10&ref_=beagle&applicationId=AWSMPContessa please don't hesitate to contact us for further assistance.
Can you provide detailed instruction on how to REMOVE installed GUI and VNC?
I followed these instructions on a fresh Linux 2 box but when I tried to enable vncserver at startup
$ sudo systemctl enable vncserver@:1
I got:
Failed to execute operation: Too many levels of symbolic links
Any help?
I encountered a blank screen after following the steps in this article. it turned out to be the ".vnc/xstartup" file in the user's home directory, which was configured to start KDE. To resolve this, I commented out the existing configuration and replaced it with the following, which worked successfully.
!/bin/sh
unset DBUS_SESSION_BUS_ADDRESS
[ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup
[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
xsetroot -solid grey
vncconfig -iconic &
x-terminal-emulator -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
x-window-manager &
mate-session &
Thank you for your comment. We'll review and update the Knowledge Center article as needed.
i also got
Failed to execute operation: Too many levels of symbolic links
when i ran
sudo systemctl enable vncserver@:1
Thank you for your comment. We'll review and update the Knowledge Center article as needed.
Step 5 under (Optional) Install a web browser (X86 only) needs to be corrected. Special characters are being escaped, rendering the file syntax invalid.
The guide is out of date. It is also not informative/educational enough. Too concise. This is a 'blind' guide. You show only steps but don't show original configuration file contents. Simply showing a bunch of steps is not informative and dangerous for system administration to blindly follow.
Step six (6) is plain wrong now and because you have shown no contents of the systemd unit file one is left wondering what this step may have been doing.
sudo sed -i 's/<USER>/'${USER}'/' /etc/systemd/system/vncserver@.service
Does nothing as there is no USER string to replace in the vncserver@.service file
# grep -i user /lib/systemd/system/vncserver@.service
# 1. Add a user mapping to /etc/tigervnc/vncserver.users.
# 2. Adjust the global or user configuration. See the
# [user@hostA ~]$ ssh -v -C -L 590N:localhost:590M hostB
After=syslog.target network.target systemd-user-sessions.service
WantedBy=multi-user.target
This step is a crucial part of the configuration but what was the intended outcome?
The service fails to start due to errors in configuration steps above:
May 13 22:13:49 ip-10-2-4-188.us-west-2.compute.internal vncsession[624125]: vncsession: vncserver exited with status=2
May 13 22:13:49 ip-10-2-4-188.us-west-2.compute.internal vncsession[624125]: pam_unix(tigervnc:session): session closed for user ec2-user
Step four (4) is also dangerous as you are clobbering (destroying) a config file's informative comments. Potentially future releases of this file could hold important configuration details which would be lost using this blind step.
$ pwd
/etc/tigervnc
$ cat vncserver-config-mandatory
## Mandatory settings for VNC servers started by the vncserver service
#
# Any settings given here will override the builtin defaults and
# settings specified in ~/.config/tigervnc/config or vnc-config-defaults.
#
# See HOWTO.md and the following manpages for more details:
# vncsession(8) Xvnc(1)
#
# Several common settings are shown below. Uncomment and modify to your
# liking.
# session=gnome
# securitytypes=vncauth,tlsvnc
# geometry=2000x1200
# localhost
# alwaysshared
Relevant content
- asked 3 years ago
- asked 2 months ago
- asked 7 months ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated a year ago