To get X11 forwarding working over ssh, you'll need 3 things in place.
Your client must be set up to forward X11.
Your server must be set up to allow X11 forwarding.
Your server must be able to set up X11 authentication.
If you have both #1 and #2 in place but are missing #3, then you'll end up with an empty DISPLAY environment variable.
Make sure that:
You've xauth installed on the server (see: xauth info/xauth list).
On the server your /etc/ssh/sshd_config file have these lines:
On the client side your ~/.ssh/config file have these lines:
On the client side, you've X server installed (e....
If you look at the Wikipedia page on the subject there are several apps mentioned.
xmove is a computer program that allows the movement of X Window
System applications between different displays and the persistence of
X applications across X server restarts. It solves a problem in the
design of X, where an X client (an X ...
It’s part of the X11 protocol (search for "6000") and is documented e.g. in Xorg(1):
Xorg listens on port 6000+n, where n is the display number. This connection type can be disabled with the -nolisten option (see the Xserver(1) man page for details).
Per #4, are you editing the right file? The ~/.ssh/config file to change is the one on the client (where the keyboard is, usually).
As for #2 (and 3), remember that ForwardX11Trusted doesn't imply ForwardX11. ForwardX11Trusted just means that if you turn on forwarding (whether via config file or command line) then the forwarded connection will be trusted.
Yes, this is possible in a few different ways but you will need an X window server for Windows. Some options of a X windows server are XManager, XMing and MobaXterm. Once you have an X server running on Windows you can use PuTTY to connect to your host after you have set the configuration parameters:
Enable X11 forwarding
X display ...
You are mixing up terms. The first thing is X11 forwarding and it is inefficient by definition and you can't do almost anything about that (it is not made for high-latency connections and decades ago]. In comparison to the other method, it is inefficient, because it is transferring whole gui (of broswer?) over the newtwork.
The other is SOCKS proxy (...
I have drawn some sketches
The machine, where the ssh tunnel command is typed is called »your host«.
local: -L Specifies that the given port on the local (client) host is to be forwarded to the given host and port on the remote side.
ssh -L sourcePort:forwardToHost:onPort connectToHost means: connect with ssh to connectToHost, and forward all ...
SSH blocks new X11 connections after 20 minutes in its default setup. To avoid this, run ssh -Y instead of ssh -X, or set the option ForwardX11Trusted yes in ~/.ssh/config.
If you run ssh -v, you'll see the message “Rejected X11 connection after ForwardX11Timeout expired” when a new application tries to connect to the display after the timeout. Without -v (...
I found this page useful:
It basically answers your question #2:
If ForwardX11Trusted is set to “yes”, then the commands ssh -X and ssh -Y are functionally equivalent. If ForwardX11 and ForwardX11Trusted are both set to “yes”, then the command flags are not only ...
For the sake of this conversation lets say there are 2 machines named lappy and remotey. The lappy system is where you'd be running your ssh commands from. The system you're connecting to is remotey.
1. Display GUIs from remotey on lappy
lappy .-,( ),-.
__ _ .-( )-. remotey
This error occurs when the remote machine doesn't know it's own hostname, or has an incorrect hostname associated with 127.0.1.1 (NOTE: Not 127.0.0.1 which should always resolve to localhost).
To correct it, ensure that the entry in /etc/hosts for 127.0.1.1 matches the machine's FQDN and short hostname.
Another solution is to merge the .Xauthority file of the current user with that of the root user.
change the .Xauthority file permissions so that root also has access to it.
sudo su - root
xauth merge /home/users/user/.Xauthority
It should open a gedit window.
It's possible, but probably not desirable. The VLC client (window) will be shown on whatever display you want, but it will be playing uncompressed video, which will have to be sent as networked X requests. Even without any overheads, sending 720×540 at 24 bpp and 30 fps will need around 279 Mbps (720px × 540px × 3 bytes/pixel × 30 fps × 8 bits per byte).
Letting Ubuntu bash on Windows 10 run ssh -X to get a GUI environment on a remote server
Install all the following. On Window, install Xming. On Ubuntu in the terminal, use sudo apt install to install ssh xauth xorg.
sudo apt install ssh xauth xorg
Go to the folder contains ssh_config file, mine is /etc/ssh.
Edit ssh_config as ...
Any time I run into an SSH issue I almost immediately re-run the command with more verbose messaging enabled. I like to use this technique to collect the log file on the server I'm running ssh from. If you need to get more details simply add more -v switches (the maximum is 3).
$ ssh -v user@remoteserver |& tee /path/to/sshv1.log
$ ssh -vv user@...
I need X installed on the host too, right?
You need an X server installed on the host only, and it will need to be running. You will need some X client libraries in the container (installing xbmc will presumably pull these in as dependencies), but not an X server.
What exactly are "displays" (like :0 and :1) and do I need to set them?
Try Xpra. It is the best X11 forwarding app, and more secure. It supports many codecs and compression formats, even x264. I used it to run skype on remote side, when I forced to do this by business, and wanted to keep my machine with open source code only.
App is running persistent, so you can reconnect to it if you loose connection, just like GNU screen ...
The problem is most likely the X protocol itself. It is very chatty and while the raw amaount of data is rather small, it causes many round trips which become a problem over WAN connections.
Your construct starts a remote xserver which the application you want to use is connecting to. So from the point of view of the application the xserver is local and ...
Add X11UseLocalhost no to /etc/ssh/sshd_config and restart the SSH server.
If you get no DISPLAY, check if xauth is installed correctly and then try it again.
RHE/CEntos doesn't have this issue, this is a Ubuntu thing!
You can use X forwarding on Windows as well; all you need is an X server (such as Xming) and an SSH client (such as PuTTY). Xming includes documentation explaining how to go about things; basically, you enable X forwarding in PuTTY, start the X server on your Windows machine, SSH to the Linux machine and run your Java application. You might find that rather ...
So far I've found xdotool tool which can fake input from the mouse and keyboard quite easily.
Some examples with simple keyboard interaction:
xdotool key a
xdotool key Down
xdotool key Tab
xdotool key "Return"
xdotool key "Control_L+t"
xdotool key Alt+1
xdotool key ctrl+v
xdotool key Super
xdotool key KP_Enter
xdotool key ctrl+Page_Up
xdotool key ctrl+...
An alternative method copied from this blog
Using this script
su - $userfirst -c 'xauth list' |\
grep `echo $DISPLAY |\
cut -d ':' -f 2 |\
cut -d '.' -f 1 |\
sed -e s/^/:/` |\
xargs -n 3 xauth add
Hi if you want to use the putty like use Openssh with -x you have to install XMING on your windows machine . it became like some sort of server then you have to config you putty to forward X11 of you ssh connection over this server
You can use this tutorials
X forwarding is often slow, even on a relatively fast network. It suffers from both bandwidth and latency: many applications often wait for an answer from the server, and that can translate into noticeable delays.
You can improve the bandwidth by compressing. SSH can do compression with the -C option. You can also use dxpc, which is a special-purpose ...
There are a couple of options here
Disable ForwardX11 on the server
The man page for sshd_config shows that you can set X11Forwarding no in the /etc/ssh/sshd_config file. If you do this, don't forget to restart the ssh daemon (service ssh restart works for me).
Create the file /home/fooftp/.Xauthority
If you create the file /home/fooftp/.Xauthority and ...
You only need to run the X server on your client PC where you want see the GUI/Desktop. Typically this would be on your Windows PC in most environments ofcourse you could run it on a Linux/Mac workstation to. Point is the X Server itself must run on the client pc. The Linux server needs SSH along with the X Window System installed from packages, usually it ...