port – Derek Demuro https://www.derekdemuro.com Software Engineer Tue, 03 Jun 2025 17:03:09 +0000 en-US hourly 1 160473225 Fix VNC has been configured on this system by Cloudmin, but the VNC server on port 590… https://www.derekdemuro.com/2016/06/06/fix-vnc-has-been-configured-on-this-system-by-cloudmin-but-the-vnc-server-on-port-590/ https://www.derekdemuro.com/2016/06/06/fix-vnc-has-been-configured-on-this-system-by-cloudmin-but-the-vnc-server-on-port-590/#respond Mon, 06 Jun 2016 06:26:23 +0000 https://www.derekdemuro.com/?p=3206 This Cloudmin issue drove me nuts, but then it clicked on why it didn’t work.

If, for some reason, after you configure your network or your server magically, VNC stops working. The answer is as simple as your host’s file.

root@mvd01:~# cat /etc/hosts
127.0.0.1       localhost
127.0.1.1       mvd01.takelan.com       mvd01
# The following lines are desirable for IPv6 capable hosts
::1     localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
 
# If we consider 127.0.1.1       mvd01.takelan.com       mvd01 as localhost MAKE SURE your HOSTNAME is THERE!
root@mvd01:~# cat /etc/hostname
mvd01.takelan.com

Your hostname MUST be declared in the Hosts file (as 127.0.0.x)…

After you’ve fixed that, try it again, and should be working just fine.

]]>
https://www.derekdemuro.com/2016/06/06/fix-vnc-has-been-configured-on-this-system-by-cloudmin-but-the-vnc-server-on-port-590/feed/ 0 3206