Linux – SSH Tunnel yielding “administratively prohibited: open failed” after a few hours

linuxsshssh-tunnelunix

i have a dynamic OpenSSH tunel running as :

ssh -N -D '*:1080' user@example.com

(OpenSSH_5.3p1 Debian-3, OpenSSL 0.9.8n 24 Mar 2010)

which runs perfectly for a few hours, or a few days, but begin to randomly drop connections (not 100%, only some) yielding:

channel 1019: open failed: administratively prohibited: open failed

I googled it but can't find nothing more than this message spowning in cause of server misconfiguration denying completly the tunnel, here the tunnel works some hours before dropping a few requests.

Any idea?

Best Answer

I've seen the same message when trying to do a port forward to an unreachable destination:

ssh example.com -L 1337:example.invalid:80

telnet localhost 1337

me@example.com:~$ channel 3: open failed: administratively prohibited: open failed

Related Solutions

SSH-forwarded X11 display from Linux to Mac lost after some time

The ssh sessions started after I changed the Mac client's /etc/ssh_config to include the line:

ForwardX11Timeout 596h

are all working fine and have been all day. By now they all would have been refusing to start new xterms. So I believe this is the answer, and luckily a simple solution, but the timeout will still happen 3-1/2 weeks from now.

Ssh tunnel refusing connections with “channel 2: open failed”

Problem solved:

$ ssh -L 7000:127.0.0.1:7000 user@host -N -v -v

...apparently, 'localhost' was not liked by the remote host. Yet, remote /etc/hosts contains:

::1                     localhost localhost.
127.0.0.1               localhost localhost.

while the local network interface is

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33184
        inet 127.0.0.1 netmask 0xff000000
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2

Sigh. so much for the bounty of 100rp I put on :)

Best Answer

Related Solutions

SSH-forwarded X11 display from Linux to Mac lost after some time

Ssh tunnel refusing connections with “channel 2: open failed”

Related Topic