Can ping ubuntu server, but not connect with putty
I'm just wondering if this is common. And if there is a way around this problem.
I have a webserver at home running on ubuntu 16.04. I manage this through putty.
My problem happened when I was managing my server via putty. My computer did a update/restart while I was eating.
After this I cannot connect to the server via putty anymore. I can ping it. And the webserver is up and running.
Maybe the session I had via putty before the computer shutdown didn't close the session correct. I'm just guessing now.
Is there a workaround without fysically restart the webserver?
Appreciate any ideas on this. Thanks.
ssh terminal putty ubuntu-16.04
asked Jan 24 at 7:53
sumpensumpen
1033
add a comment |
I'm just wondering if this is common. And if there is a way around this problem.
I have a webserver at home running on ubuntu 16.04. I manage this through putty.
My problem happened when I was managing my server via putty. My computer did a update/restart while I was eating.
After this I cannot connect to the server via putty anymore. I can ping it. And the webserver is up and running.
Maybe the session I had via putty before the computer shutdown didn't close the session correct. I'm just guessing now.
Is there a workaround without fysically restart the webserver?
Appreciate any ideas on this. Thanks.
ssh terminal putty ubuntu-16.04
asked Jan 24 at 7:53
sumpensumpen
1033
add a comment |
I'm just wondering if this is common. And if there is a way around this problem.
I have a webserver at home running on ubuntu 16.04. I manage this through putty.
My problem happened when I was managing my server via putty. My computer did a update/restart while I was eating.
After this I cannot connect to the server via putty anymore. I can ping it. And the webserver is up and running.
Maybe the session I had via putty before the computer shutdown didn't close the session correct. I'm just guessing now.
Is there a workaround without fysically restart the webserver?
Appreciate any ideas on this. Thanks.
ssh terminal putty ubuntu-16.04
asked Jan 24 at 7:53
sumpensumpen
1033
I'm just wondering if this is common. And if there is a way around this problem.
I have a webserver at home running on ubuntu 16.04. I manage this through putty.
My problem happened when I was managing my server via putty. My computer did a update/restart while I was eating.
After this I cannot connect to the server via putty anymore. I can ping it. And the webserver is up and running.
Maybe the session I had via putty before the computer shutdown didn't close the session correct. I'm just guessing now.
Is there a workaround without fysically restart the webserver?
Appreciate any ideas on this. Thanks.
ssh terminal putty ubuntu-16.04
ssh terminal putty ubuntu-16.04
asked Jan 24 at 7:53
sumpensumpen
1033
asked Jan 24 at 7:53
sumpensumpen
1033
asked Jan 24 at 7:53
sumpensumpen
1033
asked Jan 24 at 7:53
sumpensumpen
1033
asked Jan 24 at 7:53
sumpensumpen
1033
1033
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The issue is likely 1 of 2 things - sshd is not running or the firewall has changed to disallow connections on port 22.
Uf you have physical access to the server, try restarting ssh with
sudo systemctl restart sshd
If that does not work, try adding a firewall rule to the running system
sudo /sbin/iptables -I INPUT -p tcp --dport 22 -j ACCEPT
answered Jan 24 at 8:05
davidgodavidgo
44.5k75292
Hi, The restart of ssh didnt do anything. But the second command worked. But after restart of server I got the same problme again which was solved by entering the command again. Do I have to go to the server after each restart to do this command? I had the server running for more than one year, and now it starts to make a fuss.
– sumpen
Jan 24 at 19:15
So we know the problem is that the firewall is blocking incoming requests on port 22, and we need to allow it. Depending on your setup and skill, there are different ways to fix this. You could add the command to /etc/rc.local before the "exit 1" (but that is not a good way of doing things). If you use UFW (which is installed by default in Ubuntu 16.04) then the best way to do this would probably be to type "sudo ufw allow 22"
– davidgo
Jan 24 at 23:21
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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%2fsuperuser.com%2fquestions%2f1397807%2fcan-ping-ubuntu-server-but-not-connect-with-putty%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
The issue is likely 1 of 2 things - sshd is not running or the firewall has changed to disallow connections on port 22.
Uf you have physical access to the server, try restarting ssh with
sudo systemctl restart sshd
If that does not work, try adding a firewall rule to the running system
sudo /sbin/iptables -I INPUT -p tcp --dport 22 -j ACCEPT
answered Jan 24 at 8:05
davidgodavidgo
44.5k75292
Hi, The restart of ssh didnt do anything. But the second command worked. But after restart of server I got the same problme again which was solved by entering the command again. Do I have to go to the server after each restart to do this command? I had the server running for more than one year, and now it starts to make a fuss.
– sumpen
Jan 24 at 19:15
So we know the problem is that the firewall is blocking incoming requests on port 22, and we need to allow it. Depending on your setup and skill, there are different ways to fix this. You could add the command to /etc/rc.local before the "exit 1" (but that is not a good way of doing things). If you use UFW (which is installed by default in Ubuntu 16.04) then the best way to do this would probably be to type "sudo ufw allow 22"
– davidgo
Jan 24 at 23:21
add a comment |
The issue is likely 1 of 2 things - sshd is not running or the firewall has changed to disallow connections on port 22.
Uf you have physical access to the server, try restarting ssh with
sudo systemctl restart sshd
If that does not work, try adding a firewall rule to the running system
sudo /sbin/iptables -I INPUT -p tcp --dport 22 -j ACCEPT
answered Jan 24 at 8:05
davidgodavidgo
44.5k75292
Hi, The restart of ssh didnt do anything. But the second command worked. But after restart of server I got the same problme again which was solved by entering the command again. Do I have to go to the server after each restart to do this command? I had the server running for more than one year, and now it starts to make a fuss.
– sumpen
Jan 24 at 19:15
So we know the problem is that the firewall is blocking incoming requests on port 22, and we need to allow it. Depending on your setup and skill, there are different ways to fix this. You could add the command to /etc/rc.local before the "exit 1" (but that is not a good way of doing things). If you use UFW (which is installed by default in Ubuntu 16.04) then the best way to do this would probably be to type "sudo ufw allow 22"
– davidgo
Jan 24 at 23:21
add a comment |
The issue is likely 1 of 2 things - sshd is not running or the firewall has changed to disallow connections on port 22.
Uf you have physical access to the server, try restarting ssh with
sudo systemctl restart sshd
If that does not work, try adding a firewall rule to the running system
sudo /sbin/iptables -I INPUT -p tcp --dport 22 -j ACCEPT
answered Jan 24 at 8:05
davidgodavidgo
44.5k75292
The issue is likely 1 of 2 things - sshd is not running or the firewall has changed to disallow connections on port 22.
Uf you have physical access to the server, try restarting ssh with
sudo systemctl restart sshd
If that does not work, try adding a firewall rule to the running system
sudo /sbin/iptables -I INPUT -p tcp --dport 22 -j ACCEPT
answered Jan 24 at 8:05
davidgodavidgo
44.5k75292
answered Jan 24 at 8:05
davidgodavidgo
44.5k75292
answered Jan 24 at 8:05
davidgodavidgo
44.5k75292
answered Jan 24 at 8:05
davidgodavidgo
44.5k75292
44.5k75292
Hi, The restart of ssh didnt do anything. But the second command worked. But after restart of server I got the same problme again which was solved by entering the command again. Do I have to go to the server after each restart to do this command? I had the server running for more than one year, and now it starts to make a fuss.
– sumpen
Jan 24 at 19:15
So we know the problem is that the firewall is blocking incoming requests on port 22, and we need to allow it. Depending on your setup and skill, there are different ways to fix this. You could add the command to /etc/rc.local before the "exit 1" (but that is not a good way of doing things). If you use UFW (which is installed by default in Ubuntu 16.04) then the best way to do this would probably be to type "sudo ufw allow 22"
– davidgo
Jan 24 at 23:21
add a comment |
Hi, The restart of ssh didnt do anything. But the second command worked. But after restart of server I got the same problme again which was solved by entering the command again. Do I have to go to the server after each restart to do this command? I had the server running for more than one year, and now it starts to make a fuss.
– sumpen
Jan 24 at 19:15
So we know the problem is that the firewall is blocking incoming requests on port 22, and we need to allow it. Depending on your setup and skill, there are different ways to fix this. You could add the command to /etc/rc.local before the "exit 1" (but that is not a good way of doing things). If you use UFW (which is installed by default in Ubuntu 16.04) then the best way to do this would probably be to type "sudo ufw allow 22"
– davidgo
Jan 24 at 23:21
Hi, The restart of ssh didnt do anything. But the second command worked. But after restart of server I got the same problme again which was solved by entering the command again. Do I have to go to the server after each restart to do this command? I had the server running for more than one year, and now it starts to make a fuss.
– sumpen
Jan 24 at 19:15
Hi, The restart of ssh didnt do anything. But the second command worked. But after restart of server I got the same problme again which was solved by entering the command again. Do I have to go to the server after each restart to do this command? I had the server running for more than one year, and now it starts to make a fuss.
– sumpen
Jan 24 at 19:15
So we know the problem is that the firewall is blocking incoming requests on port 22, and we need to allow it. Depending on your setup and skill, there are different ways to fix this. You could add the command to /etc/rc.local before the "exit 1" (but that is not a good way of doing things). If you use UFW (which is installed by default in Ubuntu 16.04) then the best way to do this would probably be to type "sudo ufw allow 22"
– davidgo
Jan 24 at 23:21
So we know the problem is that the firewall is blocking incoming requests on port 22, and we need to allow it. Depending on your setup and skill, there are different ways to fix this. You could add the command to /etc/rc.local before the "exit 1" (but that is not a good way of doing things). If you use UFW (which is installed by default in Ubuntu 16.04) then the best way to do this would probably be to type "sudo ufw allow 22"
– davidgo
Jan 24 at 23:21
add a comment |
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1397807%2fcan-ping-ubuntu-server-but-not-connect-with-putty%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
