My droplet always needs to be power cycled after starting vncserver
I followed this tutorial if that helps :/
I am using the 512MB package because I'm new to DO and I'm not ready to move from Azure just yet :)
I followed this tutorial if that helps :/
I am using the 512MB package because I'm new to DO and I'm not ready to move from Azure just yet :)
Glad to hear that you've gotten this resolved. For future reference we also provide a user-data script which you can paste directly into the create page and auto-configure an XFCE desktop with x2go (an alternative to VNC that often has better performance). This script is targeted at Ubuntu 14.04 but I have also personally tested it on 16.04. You can find the x2go client for Windows, Mac or Linux here.
To use this script, on the create page check the "user-data" checkbox and a text area will appear. Paste the script there.
Once your droplet is created the installation of the desktop will start automatically and may take up to 5-10 minutes. When it's done you'll be able to log in as the root user with either your password or an ssh-key if you configured one. Make sure you set the session type to XFCE in the x2go client.
A user data script can be either a special YAML format ( Like this one for docker ) or any script that can be executed. In this case it is a bash script and you can run it either from the CLI or by pasting it into the user-data field on the droplet creation page.
Size of droplet should not be a problem. 512 MB droplet is be able to launch tightvnc server and xfce.
I would check log files at
$HOME/.vncdirectory. Log files have.logextension. You can share in comment or GitHub gist.Warning: Be sure to hide all sensitive informations if there is any !
I just deleted the
.vncfolder and reinstall vnc, I'm pretty sure your solution would have worked if I tried it, so I'll "love" it :)