Posts: 37
Threads: 6
Joined: Jun 2018
Reputation:
0
I can understand the benefit of being able to control openCPN via a browser on any device with noVNC. I currently use realVNC to control openCPN on my iPad. Sometimes control using realVNC can be somewhat clunky and wonder if noVNC has any other benefits over realVNC in that respect.
Posts: 53
Threads: 13
Joined: Nov 2017
Reputation:
0
I follow your instruction but it doesn't work for me.
When i try
sudo echo "su - pi -c '/home/pi/bin/noVNC/utils/launch.sh --vnc 127.0.0.1:5901 --listen 8080 &'" >> etc/rc.local
Give me permission denied.
I modify manually rc.local with
/home/pi/bin/noVNC/utils/launch.sh --vnc 127.0.0.1:5901 --listen 8080 &
Before exit 0
but didn't work...
Inviato dal mio ANE-LX2 utilizzando Tapatalk
Posts: 53
Threads: 13
Joined: Nov 2017
Reputation:
0
Finally i get into novnc, port is 6080 not 8080, but when i try to connect from client, in the terminal come error: code 400 client must support binary or base 64 protocol.
Someone have some solut?
Inviato dal mio ANE-LX2 utilizzando Tapatalk
Posts: 9
Threads: 3
Joined: Jun 2019
Reputation:
2
The main difference I see between our two setups is that I have the program living at '/home/pi/bin/noVNC/...' and you look to be running the the code in '/bin/noVNC/...', which would have different permissions. Could you try moving your app to '/home/pi/bin/noVNC/' to see if you get the same results? maybe symlink to /bin/ if you need to?