SSH to remote Ubuntu machine: sometimes works sometimes not [closed]
up vote
0
down vote
favorite
I set up a remote Ubuntu machine and I'm usually able to ssh into it without any problem. The IP of the machine is static, port forwarding seems to be working properly. The only problem is the IP of the router: it's still not static but for what this message concerns, we can safely assume it is.
Here's the situation. Yesterday, suddenly the machine stopped working and I was not able to ssh into it. I then found out that the IP of the router had changed. Now I changed the IP for HostName on my local laptop and yesterday, before going to bed, I was able to connect to the remote machine (and the machine remained turned on the all night, doing nothing, as usual). This morning, the problem reappears: Operation timed out.
When I changed IP address, yesterday, I was still not able to ssh into the remote machine: I was able to solve the issue by simply re-booting the machine physically. Now, since the IP did not change during the night, I guess I would be able to ssh into it if my parents simply re-boot it. And this would solve the problem, temporary.
Based on this (probably vague) description of the problem, can somebody provide me with some possible causes?
Some other information, just in case. When I set it up, I had to put acpi=off because otherwise I was not able to boot the USB stick with the image of Ubuntu. But before yesterday's event, I never had any problem. Also, I leave the machine at the login page, then ssh into it remotely.
ubuntu ssh remote router acpi
asked Nov 25 at 10:03
sensitive_scientist
1012
closed as too broad by Rui F Ribeiro, RalfFriedl, n.st, 0xC0000022L, Isaac Nov 25 at 21:07
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
up vote
0
down vote
favorite
I set up a remote Ubuntu machine and I'm usually able to ssh into it without any problem. The IP of the machine is static, port forwarding seems to be working properly. The only problem is the IP of the router: it's still not static but for what this message concerns, we can safely assume it is.
Here's the situation. Yesterday, suddenly the machine stopped working and I was not able to ssh into it. I then found out that the IP of the router had changed. Now I changed the IP for HostName on my local laptop and yesterday, before going to bed, I was able to connect to the remote machine (and the machine remained turned on the all night, doing nothing, as usual). This morning, the problem reappears: Operation timed out.
When I changed IP address, yesterday, I was still not able to ssh into the remote machine: I was able to solve the issue by simply re-booting the machine physically. Now, since the IP did not change during the night, I guess I would be able to ssh into it if my parents simply re-boot it. And this would solve the problem, temporary.
Based on this (probably vague) description of the problem, can somebody provide me with some possible causes?
Some other information, just in case. When I set it up, I had to put acpi=off because otherwise I was not able to boot the USB stick with the image of Ubuntu. But before yesterday's event, I never had any problem. Also, I leave the machine at the login page, then ssh into it remotely.
ubuntu ssh remote router acpi
asked Nov 25 at 10:03
sensitive_scientist
1012
closed as too broad by Rui F Ribeiro, RalfFriedl, n.st, 0xC0000022L, Isaac Nov 25 at 21:07
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
1
StackExchange with its question+answer format doesn't really lend itself to debugging problems step-by-step — instead it's usually limited to questions that have a single right answer that can also help other visitors later on. For your particular problem, you'll probably find more specific and immediate help in an IRC channel (something like #linux or #ubuntu on Freenode) or on a forum related to the topic.
– n.st
Nov 25 at 16:02
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I set up a remote Ubuntu machine and I'm usually able to ssh into it without any problem. The IP of the machine is static, port forwarding seems to be working properly. The only problem is the IP of the router: it's still not static but for what this message concerns, we can safely assume it is.
Here's the situation. Yesterday, suddenly the machine stopped working and I was not able to ssh into it. I then found out that the IP of the router had changed. Now I changed the IP for HostName on my local laptop and yesterday, before going to bed, I was able to connect to the remote machine (and the machine remained turned on the all night, doing nothing, as usual). This morning, the problem reappears: Operation timed out.
When I changed IP address, yesterday, I was still not able to ssh into the remote machine: I was able to solve the issue by simply re-booting the machine physically. Now, since the IP did not change during the night, I guess I would be able to ssh into it if my parents simply re-boot it. And this would solve the problem, temporary.
Based on this (probably vague) description of the problem, can somebody provide me with some possible causes?
Some other information, just in case. When I set it up, I had to put acpi=off because otherwise I was not able to boot the USB stick with the image of Ubuntu. But before yesterday's event, I never had any problem. Also, I leave the machine at the login page, then ssh into it remotely.
ubuntu ssh remote router acpi
asked Nov 25 at 10:03
sensitive_scientist
1012
I set up a remote Ubuntu machine and I'm usually able to ssh into it without any problem. The IP of the machine is static, port forwarding seems to be working properly. The only problem is the IP of the router: it's still not static but for what this message concerns, we can safely assume it is.
Here's the situation. Yesterday, suddenly the machine stopped working and I was not able to ssh into it. I then found out that the IP of the router had changed. Now I changed the IP for HostName on my local laptop and yesterday, before going to bed, I was able to connect to the remote machine (and the machine remained turned on the all night, doing nothing, as usual). This morning, the problem reappears: Operation timed out.
When I changed IP address, yesterday, I was still not able to ssh into the remote machine: I was able to solve the issue by simply re-booting the machine physically. Now, since the IP did not change during the night, I guess I would be able to ssh into it if my parents simply re-boot it. And this would solve the problem, temporary.
Based on this (probably vague) description of the problem, can somebody provide me with some possible causes?
Some other information, just in case. When I set it up, I had to put acpi=off because otherwise I was not able to boot the USB stick with the image of Ubuntu. But before yesterday's event, I never had any problem. Also, I leave the machine at the login page, then ssh into it remotely.
ubuntu ssh remote router acpi
ubuntu ssh remote router acpi
asked Nov 25 at 10:03
sensitive_scientist
1012
asked Nov 25 at 10:03
sensitive_scientist
1012
asked Nov 25 at 10:03
sensitive_scientist
1012
asked Nov 25 at 10:03
sensitive_scientist
1012
asked Nov 25 at 10:03
sensitive_scientist
1012
1012
closed as too broad by Rui F Ribeiro, RalfFriedl, n.st, 0xC0000022L, Isaac Nov 25 at 21:07
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
closed as too broad by Rui F Ribeiro, RalfFriedl, n.st, 0xC0000022L, Isaac Nov 25 at 21:07
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
1
StackExchange with its question+answer format doesn't really lend itself to debugging problems step-by-step — instead it's usually limited to questions that have a single right answer that can also help other visitors later on. For your particular problem, you'll probably find more specific and immediate help in an IRC channel (something like #linux or #ubuntu on Freenode) or on a forum related to the topic.
– n.st
Nov 25 at 16:02
add a comment |
1
StackExchange with its question+answer format doesn't really lend itself to debugging problems step-by-step — instead it's usually limited to questions that have a single right answer that can also help other visitors later on. For your particular problem, you'll probably find more specific and immediate help in an IRC channel (something like #linux or #ubuntu on Freenode) or on a forum related to the topic.
– n.st
Nov 25 at 16:02
1
1
StackExchange with its question+answer format doesn't really lend itself to debugging problems step-by-step — instead it's usually limited to questions that have a single right answer that can also help other visitors later on. For your particular problem, you'll probably find more specific and immediate help in an IRC channel (something like #linux or #ubuntu on Freenode) or on a forum related to the topic.
– n.st
Nov 25 at 16:02
StackExchange with its question+answer format doesn't really lend itself to debugging problems step-by-step — instead it's usually limited to questions that have a single right answer that can also help other visitors later on. For your particular problem, you'll probably find more specific and immediate help in an IRC channel (something like #linux or #ubuntu on Freenode) or on a forum related to the topic.
– n.st
Nov 25 at 16:02
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
1
StackExchange with its question+answer format doesn't really lend itself to debugging problems step-by-step — instead it's usually limited to questions that have a single right answer that can also help other visitors later on. For your particular problem, you'll probably find more specific and immediate help in an IRC channel (something like #linux or #ubuntu on Freenode) or on a forum related to the topic.
– n.st
Nov 25 at 16:02