Hi, my English is very poor but anyway using your great tutorial now I'm able to graphically use arch-linux on my little Odroid HC1 (arm). Thanks a lot.
Thank you so much. I was following the Arch Wiki and the commenting out the localhost section in the config file did it for me. Also, you can start it as a service on boot with systemd sudo systemctl enable vncserver@:1 sudo systemctl start vncserver@:1
You should know what you are doing. If you comment out the localhost option, then you will make sure that tigervnc is using encryption by itself. If you don't do that, the connection will be in plain text and this is insecure. The localhost option is there to limit the connection to localhost. Thus it's not possible to connect from a remote machine to the vnc server the normal way. To connect anyway, you need to use ssh to tunnel into the remote machine and then you can use the vnc server with the localhost option applied. Using a ssh tunnel is much safer then connecting directly to the vnc server. Also keep in mind, the vnc server is a complex software and usually not the one, that gets good support when we're talking about security fixes. ssh is much better in that. That's why using a ssh tunnel and limiting vnc to localhost is the way to go. All other configurations are not good solution.
How do I access it from my windows machine? I appeciate the video, but it's not clear how you use it once it's on. Tigervnc seems to shut itself down when I need to remote from a place that takes me a trip to get there. Please offer more details.
All this VNC and Remote Desktop is already built into X11. All you need to do is enable X11Forwarding on SSHD Config and then ssh into the remote server and run any GUI application. The app will show up on your local PC but the app process will run on remote server.
The localhost option limits the vnc session to localhost. That's why you can't connect to it. It's security feature. Especially if your vnc is setup in a way, that no encryption is used. To connect to a vnc server with the localhost option enabled you can use a ssh tunnel. With that, you also get encryption from ssh. This is the most safest setup. So enabling the localhost option is a good thing. Otherwise you must figure out, how an encrypted connection does work, if you don't do that, the conncetion is transfered in plain text over the network. This is a big security nightmare, if you can't trust the network.
Interesting. Is it much of security issue though when it's only for use on the local network? In other words, you're not transmitting the connection externally and not opening ports externally into your network, so it's only for use on LAN. If you then wanted external access, a VPN would be appropriate. Sure other LAN users could compromise the connection so for something like a school, big office or hotel etc. Where there is a lot of public LAN use, that could be of concern. This is just for home LAN usage though.
@@KyleGP Can you update the firmware of your network printer, Smart TV or your old smart phone attached to the LAN? No. This means you can't trust these old devices and thus you can't trust your home LAN. Except if you put them into a separate vlan. And because of that today with modern security thinking it's common to not trust the internal LAN. Trusting the home LAN is outdated security thinking. If you really need such a private trusted LAN, you need to setup a new vLAN for only administration tasks.
@@KyleGP Yes it is. VNC is completely unencrypted, everybody connected to you lan can see any password you enter in vnc easily. And WPA2 is no more safe, so unless you have WPA3 only and change the wifi password frequently, you should consider your wifi hacked.
Thanks , it helped me a lot But I faced a different problem , actually the vnc viewer application resolution is fixed , is it possible to adjust the vnc server screen according to the vnc viewer window size ? I mean if the geometry is set to 1920×1080 in VNC server when we try to resize it doesn't fit to the viewer window, a scroll bar come . Can it be solved ?
Idk, I just can't get it to work. I followed your guide step by step but the server never starts up. systemctl status vncserver@:1.service tells me the server is inactive and my console get's stuck at "qt5-translations". Edit: Forget the comment. Somehow it worked after a few restarts. Idk why but restarting multiple times did the trick. It's working now. Btw, it was a good video. Keep 'em coming.
i installed manjoro on my android phone, setting "-localhost no" didn't working for me, then i just remove -localhost.. then it works like a charm 😊 edit: i remote my phone with my PC with IP and Port: 5901 (default)
Oh dear, it’s 2021… and still not a simple and easy way to remote into a Linux desktop!! RDP in Windows is just a single click + autoscaling feature, audio redirection, etc. Frustrating as Linux has so much potential but clearly not ready for a proper desktop use case
Skipping the service setup is kind of a big omission. Especially given how easy it is. At a command prompt: sudo systemctl enable vncserver@:1 sudo reboot now (replace ":1" if you used a different port when configuring the vnc user). And make sure you have automatically login disabled! Having two active logins for the same user causes nothing but endless misery and inconsistent behavior. Also worth knowing: most server configuration changes (network changes particularly) need to be done on a non-VNC connection. Just remember to disconnect your VNC session before you login in locally!
Thanks for the comment. The systemctl command was added after I uploaded as I mentioned I would in the video. The primary reason for this video is to solve common issues, not enable it in systemctl. Plenty of information on enabling services out there.
![⭐ฮิตในTikTok!! ( มะมะมะหมูเด้ง MooDeng ) Ver. แดนซ์ ReMix BY [ ดีเจกิต รีมิกซ์ ]](http://i.ytimg.com/vi/4noyAoMa7bQ/mqdefault.jpg)
Hi, my English is very poor but anyway using your great tutorial now I'm able to graphically use arch-linux on my little Odroid HC1 (arm). Thanks a lot.
Thank you so much. I was following the Arch Wiki and the commenting out the localhost section in the config file did it for me.
Also, you can start it as a service on boot with systemd
sudo systemctl enable vncserver@:1
sudo systemctl start vncserver@:1
Cheers! If you check the description I think I had added that there right after making the video haha. Glad it worked for you!
Same here. Tried many things in Arch and could never get VNC to work. Thanks Kyle very much for the localhost tip.
You should know what you are doing.
If you comment out the localhost option, then you will make sure that tigervnc is using encryption by itself. If you don't do that, the connection will be in plain text and this is insecure.
The localhost option is there to limit the connection to localhost. Thus it's not possible to connect from a remote machine to the vnc server the normal way.
To connect anyway, you need to use ssh to tunnel into the remote machine and then you can use the vnc server with the localhost option applied.
Using a ssh tunnel is much safer then connecting directly to the vnc server.
Also keep in mind, the vnc server is a complex software and usually not the one, that gets good support when we're talking about security fixes. ssh is much better in that.
That's why using a ssh tunnel and limiting vnc to localhost is the way to go.
All other configurations are not good solution.
cant understand why is this so difficult. I've tried installing and configuring VNC server on Ubuntu and Manjaro... and still nothing.
It would be really helpful if you can tell we where to get those CPU widgets that you are using🥺.
does the linux version of tigerVNC has a GUI, so I can configure the server graphically? Or is the use of konsole obligatory?
How do I access it from my windows machine? I appeciate the video, but it's not clear how you use it once it's on. Tigervnc seems to shut itself down when I need to remote from a place that takes me a trip to get there. Please offer more details.
All this VNC and Remote Desktop is already built into X11. All you need to do is enable X11Forwarding on SSHD Config and then ssh into the remote server and run any GUI application. The app will show up on your local PC but the app process will run on remote server.
the only vid that acctually helped
respect !!
The localhost option limits the vnc session to localhost. That's why you can't connect to it. It's security feature. Especially if your vnc is setup in a way, that no encryption is used.
To connect to a vnc server with the localhost option enabled you can use a ssh tunnel. With that, you also get encryption from ssh. This is the most safest setup.
So enabling the localhost option is a good thing.
Otherwise you must figure out, how an encrypted connection does work, if you don't do that, the conncetion is transfered in plain text over the network. This is a big security nightmare, if you can't trust the network.
Interesting. Is it much of security issue though when it's only for use on the local network? In other words, you're not transmitting the connection externally and not opening ports externally into your network, so it's only for use on LAN. If you then wanted external access, a VPN would be appropriate. Sure other LAN users could compromise the connection so for something like a school, big office or hotel etc. Where there is a lot of public LAN use, that could be of concern. This is just for home LAN usage though.
@@KyleGP Can you update the firmware of your network printer, Smart TV or your old smart phone attached to the LAN?
No. This means you can't trust these old devices and thus you can't trust your home LAN. Except if you put them into a separate vlan.
And because of that today with modern security thinking it's common to not trust the internal LAN. Trusting the home LAN is outdated security thinking.
If you really need such a private trusted LAN, you need to setup a new vLAN for only administration tasks.
@@KyleGP Yes it is. VNC is completely unencrypted, everybody connected to you lan can see any password you enter in vnc easily. And WPA2 is no more safe, so unless you have WPA3 only and change the wifi password frequently, you should consider your wifi hacked.
Thanks , it helped me a lot
But I faced a different problem , actually the vnc viewer application resolution is fixed , is it possible to adjust the vnc server screen according to the vnc viewer window size ?
I mean if the geometry is set to 1920×1080 in VNC server when we try to resize it doesn't fit to the viewer window, a scroll bar come .
Can it be solved ?
I always get the message invalid geometry
And then the numbers I put there in the config
Tried many different
But they don't work
Woo thx alot! finally vnc works =)
Le di like solo x como se tradujo el titulo, sos un genio xD
you should make your fonts a little bigger
Idk, I just can't get it to work. I followed your guide step by step but the server never starts up. systemctl status vncserver@:1.service tells me the server is inactive and my console get's stuck at "qt5-translations".
Edit: Forget the comment. Somehow it worked after a few restarts. Idk why but restarting multiple times did the trick. It's working now.
Btw, it was a good video. Keep 'em coming.
Cheers, glad it worked in the end :)
i installed manjoro on my android phone, setting "-localhost no" didn't working for me, then i just remove -localhost.. then it works like a charm 😊
edit: i remote my phone with my PC with IP and Port: 5901 (default)
I am also trying to connect to my phone. However, it is not working for me. I have localhost commented out and use IP:5901
Oh dear, it’s 2021… and still not a simple and easy way to remote into a Linux desktop!! RDP in Windows is just a single click + autoscaling feature, audio redirection, etc. Frustrating as Linux has so much potential but clearly not ready for a proper desktop use case
Yes unfortunately I use windows as my main system and Linux is secondary for reasons such as these.
Skipping the service setup is kind of a big omission. Especially given how easy it is. At a command prompt:
sudo systemctl enable vncserver@:1
sudo reboot now
(replace ":1" if you used a different port when configuring the vnc user). And make sure you have automatically login disabled! Having two active logins for the same user causes nothing but endless misery and inconsistent behavior. Also worth knowing: most server configuration changes (network changes particularly) need to be done on a non-VNC connection. Just remember to disconnect your VNC session before you login in locally!
Thanks for the comment. The systemctl command was added after I uploaded as I mentioned I would in the video. The primary reason for this video is to solve common issues, not enable it in systemctl. Plenty of information on enabling services out there.