A note on X11-Forwarding in SSh.

SSH-X11-Forwarding.md

I used to think that

ssh -X me@some.box

"just bloody worked". However this might not work - ssh must play ball on both sides of the link. On the remote (ssh server, X client) sshd must sit behind some port, tell Xlib to send X11 requests to it and then forward them back to you the X server (where the ssh client is). If the remote box is locked down to prevent this, you will get:

X11 forwarding request failed on channel 0

as part of an otherwise working login. As it happens, I am the admin of the remote box in question, so I followed the ArchWiki and went to /etc/ssh/sshd_config and uncommented

X11Forwarding yes
X11DisplayOffset 10 
X11UseLocalhost yes

• This guy, got the same error message for a completely different reason, so you might want to look into that too.

• In the comments, simon04 says there is yet another way for this to happen because of IPv6 issues. So you might want to look into that too.

The more likely cause of trouble is that some clients will try to do things that X thinks are dangerous and end up crashing because of BadRequest. Now is the time to sit on your hands. Do you really want to use that program? Do you really trust the box that it is running on? If the answer to both of those questions is "yes", then the best thing is to use

ssh -Y me@trusted.box

But only on those occasions when you need it. Otherwise, keep using -X or (better!) nothing a all. The rule here is:

ssh    -- a remote trojan can find exploit some hole your ssh client and take over your local account.
ssh -X -- as above, but it can also exploit your X server and thus root your box.
ssh -Y -- as above, but it can also (without needing to find exploits), take screenshots and keylog you.

Have fun.

Since this comment is pretty high on google results I'll write it here:
If you intend to have ipv6 and it sill fails it could be possible that the server cannot bind to ::1, in my case because 'lo' was configured ipv4 only. adding ::1 address to lo solved the problem.

For verbose ssh output, connect with:
ssh -v -X

Make sure that xauth is installed on the remote machine.

Thanks for posting this - the verbose type from @yeison showed our problem was also missing xauth on the remote machine.

Seems can't edit comments... odd, you can elsewhere in GitHub. Anyway - thanks @gurjeet for the ssh verbose and xauth tip :)

http://www.stephensykes.com/blog_perm.html?153

I had to patch the above problem to get it working. The one line formula would be

[ ! -x "$( strings /usr/sbin/sshd | grep bin/xauth )" ] && ln -s $(which xauth) $(strings /usr/sbin/sshd | grep bin/xauth)

I had disabled IPv6 on my Ubuntu 12.04 box a while back while setting up dynDNS. Adding the AddressFamily inet to /etc/ssh/sshd_config from Simon's answer fixed my broken X11 forwarding. Thanks!

Thanks for this. There are a lot of suggestions on how to fix this issue, but your suggestions were key. It seems that in some distributions, X11Forwarding is on, while off in others, by default.

on Xubuntu 15.04 I need X11UseLocalhost no to avoid X11 forwarding request failed on channel 0 (my arch box has the default yes)

If enabling Ipv6 is not an option, so as to our specific environment, message posted by simon04 [commented on Mar 6, 2012] saved a day!
5. Alternatively, adding AddressFamily inet to /etc/ssh/sshd_config would have also worked
And I do confirm: it just worked !

If all else fails, launch a new terminal and try again. Spent hours trying to get xeyes to play ball until I in error closed my original terminal and voila it worked with a fresh terminal!
OS Debian 9.9.

I used to think that

ssh -X me@some.box

"just bloody worked"

Me too

I can confirm all options mentioned here are true and they also worked for me. Thanks