SSH tunnel to browse localhost, super slow
up vote
0
down vote
favorite
To visit sites/services like jupyter notebooks and rstudio-server on my server I make a ssh tunnel and then just browse them in my webbrowser on my local machine, however, since yesterday, all my services are loading so slow in my browser.
Not sure why or where to even start the troubleshooting. I can ssh into the server and look at file etc. I even tried reinstall one of the services yesterday before I realized that all of my services were slow...
Any ideas or recommendations how to troubleshoot this?
Can also add that if I manage to connect to one services (only manage to connect to deluge) in the browser, it seems that once i'm connected the service runs without delays in the browsers. So seems that it's "just" the connecting that takes forever. (several mins)
Can also add that the ports are open on both my remote and local machine.
I just now realized that in my terminal I get the following message:
channel 3: open failed: connect failed: Connection refused
channel 2: open failed: connect failed: Connection refused
channel 2: open failed: connect failed: Connection refused
channel 3: open failed: connect failed: Connection refused
channel 4: open failed: connect failed: Connection refused
channel 5: open failed: connect failed: Connection refused
The command I used to open up the tunnel:
ssh -N -f -L 8787:localhost:8787 myNick@192.168.1.xx
ssh-tunneling
asked Dec 5 at 11:11
Jesper.Lindberg
62
add a comment |
up vote
0
down vote
favorite
To visit sites/services like jupyter notebooks and rstudio-server on my server I make a ssh tunnel and then just browse them in my webbrowser on my local machine, however, since yesterday, all my services are loading so slow in my browser.
Not sure why or where to even start the troubleshooting. I can ssh into the server and look at file etc. I even tried reinstall one of the services yesterday before I realized that all of my services were slow...
Any ideas or recommendations how to troubleshoot this?
Can also add that if I manage to connect to one services (only manage to connect to deluge) in the browser, it seems that once i'm connected the service runs without delays in the browsers. So seems that it's "just" the connecting that takes forever. (several mins)
Can also add that the ports are open on both my remote and local machine.
I just now realized that in my terminal I get the following message:
channel 3: open failed: connect failed: Connection refused
channel 2: open failed: connect failed: Connection refused
channel 2: open failed: connect failed: Connection refused
channel 3: open failed: connect failed: Connection refused
channel 4: open failed: connect failed: Connection refused
channel 5: open failed: connect failed: Connection refused
The command I used to open up the tunnel:
ssh -N -f -L 8787:localhost:8787 myNick@192.168.1.xx
ssh-tunneling
asked Dec 5 at 11:11
Jesper.Lindberg
62
2
From the fact that just connecting takes a long time, I would suggest looking at your DNS set-up. Even though minutes for a faulty DNS is long, it might be one of the contributing factors. Look at DNS on both server and client side! You might also try127.0.0.1instead oflocalhost. Has any of the hosts enabled IPv6 recently?
– Ljm Dullaart
Dec 5 at 12:29
@LjmDullaart I'm not aware that any of the services has enabled IPv6. Chaning to 127.0.0.1 when opening the tunnel seems like it worked! Thanks!
– Jesper.Lindberg
Dec 5 at 13:09
@LjmDullaart If you want you can add that as a reply and I will accept your solution.
– Jesper.Lindberg
Dec 5 at 16:51
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
To visit sites/services like jupyter notebooks and rstudio-server on my server I make a ssh tunnel and then just browse them in my webbrowser on my local machine, however, since yesterday, all my services are loading so slow in my browser.
Not sure why or where to even start the troubleshooting. I can ssh into the server and look at file etc. I even tried reinstall one of the services yesterday before I realized that all of my services were slow...
Any ideas or recommendations how to troubleshoot this?
Can also add that if I manage to connect to one services (only manage to connect to deluge) in the browser, it seems that once i'm connected the service runs without delays in the browsers. So seems that it's "just" the connecting that takes forever. (several mins)
Can also add that the ports are open on both my remote and local machine.
I just now realized that in my terminal I get the following message:
channel 3: open failed: connect failed: Connection refused
channel 2: open failed: connect failed: Connection refused
channel 2: open failed: connect failed: Connection refused
channel 3: open failed: connect failed: Connection refused
channel 4: open failed: connect failed: Connection refused
channel 5: open failed: connect failed: Connection refused
The command I used to open up the tunnel:
ssh -N -f -L 8787:localhost:8787 myNick@192.168.1.xx
ssh-tunneling
asked Dec 5 at 11:11
Jesper.Lindberg
62
To visit sites/services like jupyter notebooks and rstudio-server on my server I make a ssh tunnel and then just browse them in my webbrowser on my local machine, however, since yesterday, all my services are loading so slow in my browser.
Not sure why or where to even start the troubleshooting. I can ssh into the server and look at file etc. I even tried reinstall one of the services yesterday before I realized that all of my services were slow...
Any ideas or recommendations how to troubleshoot this?
Can also add that if I manage to connect to one services (only manage to connect to deluge) in the browser, it seems that once i'm connected the service runs without delays in the browsers. So seems that it's "just" the connecting that takes forever. (several mins)
Can also add that the ports are open on both my remote and local machine.
I just now realized that in my terminal I get the following message:
channel 3: open failed: connect failed: Connection refused
channel 2: open failed: connect failed: Connection refused
channel 2: open failed: connect failed: Connection refused
channel 3: open failed: connect failed: Connection refused
channel 4: open failed: connect failed: Connection refused
channel 5: open failed: connect failed: Connection refused
The command I used to open up the tunnel:
ssh -N -f -L 8787:localhost:8787 myNick@192.168.1.xx
ssh-tunneling
ssh-tunneling
asked Dec 5 at 11:11
Jesper.Lindberg
62
asked Dec 5 at 11:11
Jesper.Lindberg
62
asked Dec 5 at 11:11
Jesper.Lindberg
62
asked Dec 5 at 11:11
Jesper.Lindberg
62
asked Dec 5 at 11:11
Jesper.Lindberg
62
62
2
From the fact that just connecting takes a long time, I would suggest looking at your DNS set-up. Even though minutes for a faulty DNS is long, it might be one of the contributing factors. Look at DNS on both server and client side! You might also try127.0.0.1instead oflocalhost. Has any of the hosts enabled IPv6 recently?
– Ljm Dullaart
Dec 5 at 12:29
@LjmDullaart I'm not aware that any of the services has enabled IPv6. Chaning to 127.0.0.1 when opening the tunnel seems like it worked! Thanks!
– Jesper.Lindberg
Dec 5 at 13:09
@LjmDullaart If you want you can add that as a reply and I will accept your solution.
– Jesper.Lindberg
Dec 5 at 16:51
add a comment |
2
From the fact that just connecting takes a long time, I would suggest looking at your DNS set-up. Even though minutes for a faulty DNS is long, it might be one of the contributing factors. Look at DNS on both server and client side! You might also try127.0.0.1instead oflocalhost. Has any of the hosts enabled IPv6 recently?
– Ljm Dullaart
Dec 5 at 12:29
@LjmDullaart I'm not aware that any of the services has enabled IPv6. Chaning to 127.0.0.1 when opening the tunnel seems like it worked! Thanks!
– Jesper.Lindberg
Dec 5 at 13:09
@LjmDullaart If you want you can add that as a reply and I will accept your solution.
– Jesper.Lindberg
Dec 5 at 16:51
2
2
From the fact that just connecting takes a long time, I would suggest looking at your DNS set-up. Even though minutes for a faulty DNS is long, it might be one of the contributing factors. Look at DNS on both server and client side! You might also try
127.0.0.1 instead of localhost. Has any of the hosts enabled IPv6 recently?– Ljm Dullaart
Dec 5 at 12:29
From the fact that just connecting takes a long time, I would suggest looking at your DNS set-up. Even though minutes for a faulty DNS is long, it might be one of the contributing factors. Look at DNS on both server and client side! You might also try
127.0.0.1 instead of localhost. Has any of the hosts enabled IPv6 recently?– Ljm Dullaart
Dec 5 at 12:29
@LjmDullaart I'm not aware that any of the services has enabled IPv6. Chaning to 127.0.0.1 when opening the tunnel seems like it worked! Thanks!
– Jesper.Lindberg
Dec 5 at 13:09
@LjmDullaart I'm not aware that any of the services has enabled IPv6. Chaning to 127.0.0.1 when opening the tunnel seems like it worked! Thanks!
– Jesper.Lindberg
Dec 5 at 13:09
@LjmDullaart If you want you can add that as a reply and I will accept your solution.
– Jesper.Lindberg
Dec 5 at 16:51
@LjmDullaart If you want you can add that as a reply and I will accept your solution.
– Jesper.Lindberg
Dec 5 at 16:51
add a comment |
1 Answer
1
active
oldest
votes
up vote
2
down vote
In general, when session set-up is slow, but once the session runs it has acceptable speed, the first thing to look at is the hostname resolution. There are many issues that could cause problems:
- A server and/or DNS suddenly starts using IPv6
- Faulty DNS
- Changes in
/etc/hosts - etc.
Using 127.0.0.1 instead of the hostname bypasses most of these problems (but does not solve them!)
answered Dec 6 at 19:27
Ljm Dullaart
57517
Okay, however I do have127.0.0.1 localhost.localdomain localhostentry in/etc/hostsand can't find any other problems with my DNS?
– Jesper.Lindberg
Dec 7 at 14:20
At the client side but also at the server-side? Has127.0.0.1been assigned with the hostname as well (shouldn't be, but some installations do that) , either at server or at the client? (just another option that is part of the 'etc.' at the end of the list)
– Ljm Dullaart
Dec 7 at 19:53
Without doing anything really, it seems to work fine even with localhost now. Also that localhost entry was on the server-side.
– Jesper.Lindberg
Dec 7 at 21:50
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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',
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2funix.stackexchange.com%2fquestions%2f486127%2fssh-tunnel-to-browse-localhost-super-slow%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
In general, when session set-up is slow, but once the session runs it has acceptable speed, the first thing to look at is the hostname resolution. There are many issues that could cause problems:
- A server and/or DNS suddenly starts using IPv6
- Faulty DNS
- Changes in
/etc/hosts - etc.
Using 127.0.0.1 instead of the hostname bypasses most of these problems (but does not solve them!)
answered Dec 6 at 19:27
Ljm Dullaart
57517
Okay, however I do have127.0.0.1 localhost.localdomain localhostentry in/etc/hostsand can't find any other problems with my DNS?
– Jesper.Lindberg
Dec 7 at 14:20
At the client side but also at the server-side? Has127.0.0.1been assigned with the hostname as well (shouldn't be, but some installations do that) , either at server or at the client? (just another option that is part of the 'etc.' at the end of the list)
– Ljm Dullaart
Dec 7 at 19:53
Without doing anything really, it seems to work fine even with localhost now. Also that localhost entry was on the server-side.
– Jesper.Lindberg
Dec 7 at 21:50
add a comment |
up vote
2
down vote
In general, when session set-up is slow, but once the session runs it has acceptable speed, the first thing to look at is the hostname resolution. There are many issues that could cause problems:
- A server and/or DNS suddenly starts using IPv6
- Faulty DNS
- Changes in
/etc/hosts - etc.
Using 127.0.0.1 instead of the hostname bypasses most of these problems (but does not solve them!)
answered Dec 6 at 19:27
Ljm Dullaart
57517
Okay, however I do have127.0.0.1 localhost.localdomain localhostentry in/etc/hostsand can't find any other problems with my DNS?
– Jesper.Lindberg
Dec 7 at 14:20
At the client side but also at the server-side? Has127.0.0.1been assigned with the hostname as well (shouldn't be, but some installations do that) , either at server or at the client? (just another option that is part of the 'etc.' at the end of the list)
– Ljm Dullaart
Dec 7 at 19:53
Without doing anything really, it seems to work fine even with localhost now. Also that localhost entry was on the server-side.
– Jesper.Lindberg
Dec 7 at 21:50
add a comment |
up vote
2
down vote
up vote
2
down vote
In general, when session set-up is slow, but once the session runs it has acceptable speed, the first thing to look at is the hostname resolution. There are many issues that could cause problems:
- A server and/or DNS suddenly starts using IPv6
- Faulty DNS
- Changes in
/etc/hosts - etc.
Using 127.0.0.1 instead of the hostname bypasses most of these problems (but does not solve them!)
answered Dec 6 at 19:27
Ljm Dullaart
57517
In general, when session set-up is slow, but once the session runs it has acceptable speed, the first thing to look at is the hostname resolution. There are many issues that could cause problems:
- A server and/or DNS suddenly starts using IPv6
- Faulty DNS
- Changes in
/etc/hosts - etc.
Using 127.0.0.1 instead of the hostname bypasses most of these problems (but does not solve them!)
answered Dec 6 at 19:27
Ljm Dullaart
57517
answered Dec 6 at 19:27
Ljm Dullaart
57517
answered Dec 6 at 19:27
Ljm Dullaart
57517
answered Dec 6 at 19:27
Ljm Dullaart
57517
57517
Okay, however I do have127.0.0.1 localhost.localdomain localhostentry in/etc/hostsand can't find any other problems with my DNS?
– Jesper.Lindberg
Dec 7 at 14:20
At the client side but also at the server-side? Has127.0.0.1been assigned with the hostname as well (shouldn't be, but some installations do that) , either at server or at the client? (just another option that is part of the 'etc.' at the end of the list)
– Ljm Dullaart
Dec 7 at 19:53
Without doing anything really, it seems to work fine even with localhost now. Also that localhost entry was on the server-side.
– Jesper.Lindberg
Dec 7 at 21:50
add a comment |
Okay, however I do have127.0.0.1 localhost.localdomain localhostentry in/etc/hostsand can't find any other problems with my DNS?
– Jesper.Lindberg
Dec 7 at 14:20
At the client side but also at the server-side? Has127.0.0.1been assigned with the hostname as well (shouldn't be, but some installations do that) , either at server or at the client? (just another option that is part of the 'etc.' at the end of the list)
– Ljm Dullaart
Dec 7 at 19:53
Without doing anything really, it seems to work fine even with localhost now. Also that localhost entry was on the server-side.
– Jesper.Lindberg
Dec 7 at 21:50
Okay, however I do have
127.0.0.1 localhost.localdomain localhost entry in /etc/hosts and can't find any other problems with my DNS?– Jesper.Lindberg
Dec 7 at 14:20
Okay, however I do have
127.0.0.1 localhost.localdomain localhost entry in /etc/hosts and can't find any other problems with my DNS?– Jesper.Lindberg
Dec 7 at 14:20
At the client side but also at the server-side? Has
127.0.0.1 been assigned with the hostname as well (shouldn't be, but some installations do that) , either at server or at the client? (just another option that is part of the 'etc.' at the end of the list)– Ljm Dullaart
Dec 7 at 19:53
At the client side but also at the server-side? Has
127.0.0.1 been assigned with the hostname as well (shouldn't be, but some installations do that) , either at server or at the client? (just another option that is part of the 'etc.' at the end of the list)– Ljm Dullaart
Dec 7 at 19:53
Without doing anything really, it seems to work fine even with localhost now. Also that localhost entry was on the server-side.
– Jesper.Lindberg
Dec 7 at 21:50
Without doing anything really, it seems to work fine even with localhost now. Also that localhost entry was on the server-side.
– Jesper.Lindberg
Dec 7 at 21:50
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2funix.stackexchange.com%2fquestions%2f486127%2fssh-tunnel-to-browse-localhost-super-slow%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
2
From the fact that just connecting takes a long time, I would suggest looking at your DNS set-up. Even though minutes for a faulty DNS is long, it might be one of the contributing factors. Look at DNS on both server and client side! You might also try
127.0.0.1instead oflocalhost. Has any of the hosts enabled IPv6 recently?– Ljm Dullaart
Dec 5 at 12:29
@LjmDullaart I'm not aware that any of the services has enabled IPv6. Chaning to 127.0.0.1 when opening the tunnel seems like it worked! Thanks!
– Jesper.Lindberg
Dec 5 at 13:09
@LjmDullaart If you want you can add that as a reply and I will accept your solution.
– Jesper.Lindberg
Dec 5 at 16:51