I had this problem some time back. Forgot exactly how I fixed it
but I think there's a configuration menu for VNC and you have to
tell it to "accept all connections". I found that the config file
doesn't always save and if you ever reboot, you have to set it up
again. Some place there's a command to save config file.
Rick
On 4/1/2020 1:00 PM, Jesse Jones wrote:
This is a brand new Paravel Appliance being set up on minimal CentOS 7. I have installed as root the x11vnc-auto per the instructions Nov 2018 RDD, including systemctl start x11vnc-auto.socket and systemctl enable x11vnc-auto.socket. As user rd used vnc password and following the prompts I set a password but did not use a view only password. Up until this point everything has gone as expected except when I use a TightVNC from Windows 10 Pro across the LAN the Appliance connects and asks for the password. When I put in the correct password, the Appliance responds with "The connection has been gracefully closed". /home/rd/vnc.log is empty. Tail of dmesg has nothing I recognize as vnc related. This same Windows 10 computer Tight VNC works on 11 other (older) Appliances. This is my first RD3 and my first in CentOS 7 - everything else was in CentOS 6 and I have to use notes just to get around.
Do you think I need to add the password to root to get the VNC to open? What else should I do to get this working?
_______________________________________________ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
_______________________________________________ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
