ssh as socks proxy - channel 5: open failed: connect failed: Connection refused
I experience difficulty using ssh as socks proxy.
Some details...
I connect to remote host using yakuake
ssh user@remote.host.domain -D5902
also I use 127.0.0.1:5902 as my socks v5 proxy in browser.
Everything works fine, but after some time I begin to receive errors in yakuake:
channel 57: open failed: connect failed: Connection refused
channel 12: open failed: connect failed: Connection refused
channel 13: open failed: connect failed: Connection refused
channel 5: open failed: connect failed: Connection refused
channel 13: open failed: connect failed: Connection refused
channel 5: open failed: connect failed: Connection refused
channel 10: open failed: connect failed: Connection refused
channel 6: open failed: connect failed: Connection refused
channel 5: open failed: connect failed: Connection refused
channel 5: open failed: connect failed: Connection refused
channel 9: open failed: connect failed: Connection refused
channel 22: open failed: connect failed: Connection refused
channel 5: open failed: connect failed: Connection refused
channel 9: open failed: connect failed: Connection refused
channel 15: open failed: connect failed: Connection refused
channel 16: open failed: connect failed: Connection refused
channel 9: open failed: connect failed: Connection refused
channel 29: open failed: connect failed: Connection refused
channel 16: open failed: connect failed: Connection refused
In the same time, I experience slow work in browser.
Then I break session in yakuake and start new one, it helps for some time, then the situation repeats again.
Remote host:
Ubuntu 14.04.3 LTS (GNU/Linux 2.6.32-042stab111.12 x86_64)
Local host:
$ lsb_release -aNo LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.3 LTS
Release: 14.04
Codename: trusty
Any help on how to solve it without breaking session? I would rather set sime bigger timeout (if it is possible at all) instead to receive these errors.
networking ssh proxy
edited Jan 18 '16 at 20:07
Jakuje
5,23471831
asked Jan 18 '16 at 18:51
marchellomarchello
1114
add a comment |
I experience difficulty using ssh as socks proxy.
Some details...
I connect to remote host using yakuake
ssh user@remote.host.domain -D5902
also I use 127.0.0.1:5902 as my socks v5 proxy in browser.
Everything works fine, but after some time I begin to receive errors in yakuake:
channel 57: open failed: connect failed: Connection refused
channel 12: open failed: connect failed: Connection refused
channel 13: open failed: connect failed: Connection refused
channel 5: open failed: connect failed: Connection refused
channel 13: open failed: connect failed: Connection refused
channel 5: open failed: connect failed: Connection refused
channel 10: open failed: connect failed: Connection refused
channel 6: open failed: connect failed: Connection refused
channel 5: open failed: connect failed: Connection refused
channel 5: open failed: connect failed: Connection refused
channel 9: open failed: connect failed: Connection refused
channel 22: open failed: connect failed: Connection refused
channel 5: open failed: connect failed: Connection refused
channel 9: open failed: connect failed: Connection refused
channel 15: open failed: connect failed: Connection refused
channel 16: open failed: connect failed: Connection refused
channel 9: open failed: connect failed: Connection refused
channel 29: open failed: connect failed: Connection refused
channel 16: open failed: connect failed: Connection refused
In the same time, I experience slow work in browser.
Then I break session in yakuake and start new one, it helps for some time, then the situation repeats again.
Remote host:
Ubuntu 14.04.3 LTS (GNU/Linux 2.6.32-042stab111.12 x86_64)
Local host:
$ lsb_release -aNo LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.3 LTS
Release: 14.04
Codename: trusty
Any help on how to solve it without breaking session? I would rather set sime bigger timeout (if it is possible at all) instead to receive these errors.
networking ssh proxy
edited Jan 18 '16 at 20:07
Jakuje
5,23471831
asked Jan 18 '16 at 18:51
marchellomarchello
1114
add a comment |
I experience difficulty using ssh as socks proxy.
Some details...
I connect to remote host using yakuake
ssh user@remote.host.domain -D5902
also I use 127.0.0.1:5902 as my socks v5 proxy in browser.
Everything works fine, but after some time I begin to receive errors in yakuake:
channel 57: open failed: connect failed: Connection refused
channel 12: open failed: connect failed: Connection refused
channel 13: open failed: connect failed: Connection refused
channel 5: open failed: connect failed: Connection refused
channel 13: open failed: connect failed: Connection refused
channel 5: open failed: connect failed: Connection refused
channel 10: open failed: connect failed: Connection refused
channel 6: open failed: connect failed: Connection refused
channel 5: open failed: connect failed: Connection refused
channel 5: open failed: connect failed: Connection refused
channel 9: open failed: connect failed: Connection refused
channel 22: open failed: connect failed: Connection refused
channel 5: open failed: connect failed: Connection refused
channel 9: open failed: connect failed: Connection refused
channel 15: open failed: connect failed: Connection refused
channel 16: open failed: connect failed: Connection refused
channel 9: open failed: connect failed: Connection refused
channel 29: open failed: connect failed: Connection refused
channel 16: open failed: connect failed: Connection refused
In the same time, I experience slow work in browser.
Then I break session in yakuake and start new one, it helps for some time, then the situation repeats again.
Remote host:
Ubuntu 14.04.3 LTS (GNU/Linux 2.6.32-042stab111.12 x86_64)
Local host:
$ lsb_release -aNo LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.3 LTS
Release: 14.04
Codename: trusty
Any help on how to solve it without breaking session? I would rather set sime bigger timeout (if it is possible at all) instead to receive these errors.
networking ssh proxy
edited Jan 18 '16 at 20:07
Jakuje
5,23471831
asked Jan 18 '16 at 18:51
marchellomarchello
1114
I experience difficulty using ssh as socks proxy.
Some details...
I connect to remote host using yakuake
ssh user@remote.host.domain -D5902
also I use 127.0.0.1:5902 as my socks v5 proxy in browser.
Everything works fine, but after some time I begin to receive errors in yakuake:
channel 57: open failed: connect failed: Connection refused
channel 12: open failed: connect failed: Connection refused
channel 13: open failed: connect failed: Connection refused
channel 5: open failed: connect failed: Connection refused
channel 13: open failed: connect failed: Connection refused
channel 5: open failed: connect failed: Connection refused
channel 10: open failed: connect failed: Connection refused
channel 6: open failed: connect failed: Connection refused
channel 5: open failed: connect failed: Connection refused
channel 5: open failed: connect failed: Connection refused
channel 9: open failed: connect failed: Connection refused
channel 22: open failed: connect failed: Connection refused
channel 5: open failed: connect failed: Connection refused
channel 9: open failed: connect failed: Connection refused
channel 15: open failed: connect failed: Connection refused
channel 16: open failed: connect failed: Connection refused
channel 9: open failed: connect failed: Connection refused
channel 29: open failed: connect failed: Connection refused
channel 16: open failed: connect failed: Connection refused
In the same time, I experience slow work in browser.
Then I break session in yakuake and start new one, it helps for some time, then the situation repeats again.
Remote host:
Ubuntu 14.04.3 LTS (GNU/Linux 2.6.32-042stab111.12 x86_64)
Local host:
$ lsb_release -aNo LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.3 LTS
Release: 14.04
Codename: trusty
Any help on how to solve it without breaking session? I would rather set sime bigger timeout (if it is possible at all) instead to receive these errors.
networking ssh proxy
networking ssh proxy
edited Jan 18 '16 at 20:07
Jakuje
5,23471831
asked Jan 18 '16 at 18:51
marchellomarchello
1114
edited Jan 18 '16 at 20:07
Jakuje
5,23471831
asked Jan 18 '16 at 18:51
marchellomarchello
1114
edited Jan 18 '16 at 20:07
Jakuje
5,23471831
edited Jan 18 '16 at 20:07
Jakuje
5,23471831
edited Jan 18 '16 at 20:07
Jakuje
5,23471831
5,23471831
asked Jan 18 '16 at 18:51
marchellomarchello
1114
asked Jan 18 '16 at 18:51
marchellomarchello
1114
asked Jan 18 '16 at 18:51
marchellomarchello
1114
1114
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
this works for me with socks/socks5 on google-chrome :
ssh -D 8080 -C -N user@remote.host.domain
google-chrome --proxy-server="socks://localhost:8080"
google-chrome --proxy-server="socks5://localhost:8080"
answered Jan 18 '16 at 19:20
bistocobistoco
1,039717
bistoco, it does work. But as I said in my original post, it starts to show errors after some time. Now with -N option it doesn't show anything, but I do see slow work of browser after some time. And it does work fine again after session break and reconnect. Any other hints maybe to set timeout?
– marchello
Jan 18 '16 at 20:03
Also I'd someone to explain how -C option does work. My guess is that it compresses traffic between my local PC and remote server where I connect to via ssh. So, it seems doesn't really help when my need is to increase timeout when I wait for responce from some web site.
– marchello
Jan 18 '16 at 20:06
add a comment |
I can't speak to your specific errors, but the reason you're seeing them is because your browser is trying to make connections that your SSH server will not allow. The SOCKS5 proxy I'm using is throwing tons of errors because I have 13,000+ entries in my /etc/hosts file to resolve ad servers as 0.0.0.0, and every time it tries to load an ad, an error is thrown, as 0.0.0.0 refuses the connection. I find it quite satisfying actually.
answered Feb 16 '16 at 21:27
bahuabahua
11
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f722625%2fssh-as-socks-proxy-channel-5-open-failed-connect-failed-connection-refused%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
this works for me with socks/socks5 on google-chrome :
ssh -D 8080 -C -N user@remote.host.domain
google-chrome --proxy-server="socks://localhost:8080"
google-chrome --proxy-server="socks5://localhost:8080"
answered Jan 18 '16 at 19:20
bistocobistoco
1,039717
bistoco, it does work. But as I said in my original post, it starts to show errors after some time. Now with -N option it doesn't show anything, but I do see slow work of browser after some time. And it does work fine again after session break and reconnect. Any other hints maybe to set timeout?
– marchello
Jan 18 '16 at 20:03
Also I'd someone to explain how -C option does work. My guess is that it compresses traffic between my local PC and remote server where I connect to via ssh. So, it seems doesn't really help when my need is to increase timeout when I wait for responce from some web site.
– marchello
Jan 18 '16 at 20:06
add a comment |
this works for me with socks/socks5 on google-chrome :
ssh -D 8080 -C -N user@remote.host.domain
google-chrome --proxy-server="socks://localhost:8080"
google-chrome --proxy-server="socks5://localhost:8080"
answered Jan 18 '16 at 19:20
bistocobistoco
1,039717
bistoco, it does work. But as I said in my original post, it starts to show errors after some time. Now with -N option it doesn't show anything, but I do see slow work of browser after some time. And it does work fine again after session break and reconnect. Any other hints maybe to set timeout?
– marchello
Jan 18 '16 at 20:03
Also I'd someone to explain how -C option does work. My guess is that it compresses traffic between my local PC and remote server where I connect to via ssh. So, it seems doesn't really help when my need is to increase timeout when I wait for responce from some web site.
– marchello
Jan 18 '16 at 20:06
add a comment |
this works for me with socks/socks5 on google-chrome :
ssh -D 8080 -C -N user@remote.host.domain
google-chrome --proxy-server="socks://localhost:8080"
google-chrome --proxy-server="socks5://localhost:8080"
answered Jan 18 '16 at 19:20
bistocobistoco
1,039717
this works for me with socks/socks5 on google-chrome :
ssh -D 8080 -C -N user@remote.host.domain
google-chrome --proxy-server="socks://localhost:8080"
google-chrome --proxy-server="socks5://localhost:8080"
answered Jan 18 '16 at 19:20
bistocobistoco
1,039717
answered Jan 18 '16 at 19:20
bistocobistoco
1,039717
answered Jan 18 '16 at 19:20
bistocobistoco
1,039717
answered Jan 18 '16 at 19:20
bistocobistoco
1,039717
1,039717
bistoco, it does work. But as I said in my original post, it starts to show errors after some time. Now with -N option it doesn't show anything, but I do see slow work of browser after some time. And it does work fine again after session break and reconnect. Any other hints maybe to set timeout?
– marchello
Jan 18 '16 at 20:03
Also I'd someone to explain how -C option does work. My guess is that it compresses traffic between my local PC and remote server where I connect to via ssh. So, it seems doesn't really help when my need is to increase timeout when I wait for responce from some web site.
– marchello
Jan 18 '16 at 20:06
add a comment |
bistoco, it does work. But as I said in my original post, it starts to show errors after some time. Now with -N option it doesn't show anything, but I do see slow work of browser after some time. And it does work fine again after session break and reconnect. Any other hints maybe to set timeout?
– marchello
Jan 18 '16 at 20:03
Also I'd someone to explain how -C option does work. My guess is that it compresses traffic between my local PC and remote server where I connect to via ssh. So, it seems doesn't really help when my need is to increase timeout when I wait for responce from some web site.
– marchello
Jan 18 '16 at 20:06
bistoco, it does work. But as I said in my original post, it starts to show errors after some time. Now with -N option it doesn't show anything, but I do see slow work of browser after some time. And it does work fine again after session break and reconnect. Any other hints maybe to set timeout?
– marchello
Jan 18 '16 at 20:03
bistoco, it does work. But as I said in my original post, it starts to show errors after some time. Now with -N option it doesn't show anything, but I do see slow work of browser after some time. And it does work fine again after session break and reconnect. Any other hints maybe to set timeout?
– marchello
Jan 18 '16 at 20:03
Also I'd someone to explain how -C option does work. My guess is that it compresses traffic between my local PC and remote server where I connect to via ssh. So, it seems doesn't really help when my need is to increase timeout when I wait for responce from some web site.
– marchello
Jan 18 '16 at 20:06
Also I'd someone to explain how -C option does work. My guess is that it compresses traffic between my local PC and remote server where I connect to via ssh. So, it seems doesn't really help when my need is to increase timeout when I wait for responce from some web site.
– marchello
Jan 18 '16 at 20:06
add a comment |
I can't speak to your specific errors, but the reason you're seeing them is because your browser is trying to make connections that your SSH server will not allow. The SOCKS5 proxy I'm using is throwing tons of errors because I have 13,000+ entries in my /etc/hosts file to resolve ad servers as 0.0.0.0, and every time it tries to load an ad, an error is thrown, as 0.0.0.0 refuses the connection. I find it quite satisfying actually.
answered Feb 16 '16 at 21:27
bahuabahua
11
add a comment |
I can't speak to your specific errors, but the reason you're seeing them is because your browser is trying to make connections that your SSH server will not allow. The SOCKS5 proxy I'm using is throwing tons of errors because I have 13,000+ entries in my /etc/hosts file to resolve ad servers as 0.0.0.0, and every time it tries to load an ad, an error is thrown, as 0.0.0.0 refuses the connection. I find it quite satisfying actually.
answered Feb 16 '16 at 21:27
bahuabahua
11
add a comment |
I can't speak to your specific errors, but the reason you're seeing them is because your browser is trying to make connections that your SSH server will not allow. The SOCKS5 proxy I'm using is throwing tons of errors because I have 13,000+ entries in my /etc/hosts file to resolve ad servers as 0.0.0.0, and every time it tries to load an ad, an error is thrown, as 0.0.0.0 refuses the connection. I find it quite satisfying actually.
answered Feb 16 '16 at 21:27
bahuabahua
11
I can't speak to your specific errors, but the reason you're seeing them is because your browser is trying to make connections that your SSH server will not allow. The SOCKS5 proxy I'm using is throwing tons of errors because I have 13,000+ entries in my /etc/hosts file to resolve ad servers as 0.0.0.0, and every time it tries to load an ad, an error is thrown, as 0.0.0.0 refuses the connection. I find it quite satisfying actually.
answered Feb 16 '16 at 21:27
bahuabahua
11
answered Feb 16 '16 at 21:27
bahuabahua
11
answered Feb 16 '16 at 21:27
bahuabahua
11
answered Feb 16 '16 at 21:27
bahuabahua
11
11
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f722625%2fssh-as-socks-proxy-channel-5-open-failed-connect-failed-connection-refused%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
