Timeline for SSH tunneling error: "channel 1: open failed: administratively prohibited: open failed"
Current License: CC BY-SA 3.0
41 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 13, 2023 at 9:45 | answer | added | Jakob Egger | timeline score: 1 | |
| Sep 6, 2022 at 19:10 | comment | added | Ti Strga | Another cause of hostname lookup failure on the intermediate system is if it's a CentOS system with systemd, and the /etc/nsswitch.conf file includes myhostname for the hosts: entry. The myhostname extension is systemd's attempt to be smart, and it fails miserably and causes hostname failures. Remove the myhostname (so that the line looks something like hosts: files dns or similar) and then try running a host remote_system_name lookup on its command line. With myhostname it fails, without it everything works. | |
| May 27, 2022 at 21:09 | answer | added | Aaron D. Marasco | timeline score: 0 | |
| May 23, 2022 at 19:22 | comment | added | tishma | In my case it was paired with Escape character is '^]'. Connection closed by foreign host. client side, which suggested that the connection was actually established but dropped immediately. After a while - it turned out to be that nothing was listening on the forwarded port. | |
| Feb 25, 2022 at 3:05 | answer | added | slm♦ | timeline score: 1 | |
| Mar 31, 2021 at 21:37 | answer | added | Lars Nordin | timeline score: 0 | |
| Apr 2, 2020 at 2:22 | comment | added | Manjunath Reddy | Also, it could be that your server credentials are expired. | |
| Feb 23, 2020 at 13:09 | answer | added | gatorback | timeline score: 0 | |
| Jun 3, 2019 at 20:57 | answer | added | Brent Bradburn | timeline score: 0 | |
| Apr 25, 2018 at 20:53 | history | protected | Chris Davies | ||
| Apr 25, 2018 at 18:00 | answer | added | Fjor | timeline score: 0 | |
| Apr 23, 2018 at 17:37 | answer | added | Mnebuerquo | timeline score: 4 | |
| Apr 16, 2018 at 15:04 | comment | added | Brad Dwyer | A slight addition to one of the comments above: "A DNS resolution failure may cause this error" -- also make sure you're spelling your hostname correctly. I just spent over an hour trying to debug all the ssh settings and it turns out I had just misspelled amazonaws in the command which is equivalent to the DNS resolution failure note above. | |
| Dec 30, 2017 at 3:39 | answer | added | tinlyx | timeline score: 10 | |
| May 2, 2017 at 7:54 | answer | added | Pieter Van Gorp | timeline score: 3 | |
| Mar 31, 2017 at 10:11 | answer | added | diyism | timeline score: -1 | |
| Mar 24, 2017 at 17:12 | comment | added | user423430 | A DNS resolution failure may cause this error plus the connection may freeze until it times out: superuser.com/a/700677 | |
| Feb 20, 2017 at 17:48 | answer | added | Data | timeline score: 0 | |
| Jul 22, 2016 at 10:31 | answer | added | lauhub | timeline score: 5 | |
| Mar 10, 2016 at 14:26 | answer | added | Torxed | timeline score: 7 | |
| Oct 23, 2015 at 21:34 | answer | added | Northstrider | timeline score: 0 | |
| Aug 18, 2015 at 18:54 | answer | added | SlavaSt | timeline score: 2 | |
| Jul 21, 2015 at 7:36 | answer | added | Ender | timeline score: 1 | |
| Apr 18, 2015 at 19:44 | answer | added | Mike | timeline score: 1 | |
| Jan 31, 2015 at 7:49 | comment | added | Stéphane Gourichon | As you can see from the dozen of answers below, the error message, despite looking very specific, should be understood as a generic error. Generally, the solution is to open a shell at the remote and try the very same connection, to see the actual cause. You will find in answers below the most common actual causes. | |
| Jun 4, 2014 at 21:16 | answer | added | cobbzilla | timeline score: 80 | |
| Oct 4, 2013 at 14:34 | answer | added | Leonardo Brunnet | timeline score: 2 | |
| Aug 20, 2013 at 7:01 | answer | added | jacquesjtheron | timeline score: 21 | |
| May 28, 2013 at 22:03 | answer | added | user578125 | timeline score: 10 | |
| May 20, 2013 at 12:07 | answer | added | Matej Kovac | timeline score: 14 | |
| Apr 22, 2013 at 16:56 | comment | added | RobM | I found this to mean "Cannot resolve hostname remote" in my case. | |
| Dec 18, 2012 at 9:39 | answer | added | hyperair | timeline score: 218 | |
| Dec 13, 2012 at 20:37 | answer | added | Marciano | timeline score: 4 | |
| Mar 31, 2012 at 10:40 | answer | added | barlop | timeline score: 0 | |
| Jun 3, 2011 at 9:16 | comment | added | Marcel G | Why are you forwarding X11 (-X option) here? If you want to only forward HTTP this is not necessary. And as a side note IMHO ssh might be the wrong solution to make a Webserver available on multiple ports. | |
| Jun 1, 2011 at 22:05 | history | edited | Gilles 'SO- stop being evil' | edited tags | |
| Jun 1, 2011 at 21:23 | answer | added | Marco Solieri | timeline score: 3 | |
| Jun 1, 2011 at 19:28 | answer | added | Shadur-don't-feed-the-AI | timeline score: 7 | |
| Jun 1, 2011 at 17:00 | comment | added | Faheem Mitha | Maybe I'm missing something, but why are you trying to access a web server using a ssh client? | |
| Jun 1, 2011 at 16:59 | answer | added | Neil | timeline score: 32 | |
| Jun 1, 2011 at 16:56 | history | asked | Neil | CC BY-SA 3.0 |