Vitreous Humour

Members
  • Posts

    5
  • Joined

Everything posted by Vitreous Humour

  1. I'm having a minor issue. The syncthing container is working normally, but oddly won't autostart with the other docker containers. It will manually start fine, but just won't autostart. More an annoyance issue than anything else, but anyone else having it? Or know how to fix it? I looked in both the server logs, as well as the syncthing container logs, and don't see any record of failed attempts to start the container.
  2. Hmm. So it sounds like it should be working, any other ideas why I still don't get a password prompt when accessing the webGUI for DirSyncPro? Thanks so much for the help!
  3. Literally the exact instructions in your post. 1. Opened the terminal by clicking console under DirSyncPro on the docker tab 2. Enter root by typing "su $USER" in the opened terminal 3. Executed password creation by typing "vncpasswd" 4. Put in 8 character password, twice 5. Edited the DirSyncPro settings to add a blank variable with "TURBOVNC_PARAMS" as the key. 6. Pressed apply to restart the container. The only additional step is I had to create a .vnc folder in the DirSyncPro appdata folder, so that I wouldn't get a " password file couldn't be created" error after inputing the passwords after the vncpasswd command. I'm assuming I'm running DirSyncPro as root when typing "su $USER", is there another way I should be running DirSyncPro as root? I'm on the latest version of your DirSyncPro docker, since I just installed it.
  4. Apologies, but I just installed DirSyncPro and when I tried to set the noVNC password using the process described in the Recommended Post at the beginning of this topic I get a "Cannot write password file /dirsyncpro/.vnc/passwd" error and a password never appears to get set. Anyone have an idea as to why this is occuring, and how to allow that file to be created? Edit: I figured out that you need to actually manually create a .vnc folder in the dirsyncpro folder in appdata for the file to be properly written, but for some reason there is still not a required password to use the WebGUI. I made sure I had the TURBOVNC_PARAMS variable created and restarted the docker but nothing is showing up.