Issues with SSH'ing to Ubuntu 18.04 on VirtualBox [closed]
up vote
0
down vote
favorite
I've installed mini version of Ubuntu 18.04 on VirtualBox using Windows 7 as host. In order to be able to SSH onto guest system in VirtualBox I've forwarded port 2222 on localhost onto port 22 on guest. Afterwards I was able to ssh onto the guest machine, but... As soon as I try to connect by either Putty on my Windows host machine or through my laptop by trying to ssh through forwarded port the connection closes instantly with message like this:
"Connection closed by: 192.168.0.31 port 2222"
Any ideas on how to fix this issue?
virtualbox
asked Dec 5 at 17:56
Stormwaker
63
closed as off-topic by Thomas Ward♦ Dec 5 at 18:48
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This describes a problem that can't be reproduced, that seemingly went away on its own or was only relevant to a very specific period of time. It's off-topic as it's unlikely to help future readers." – Thomas Ward
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've installed mini version of Ubuntu 18.04 on VirtualBox using Windows 7 as host. In order to be able to SSH onto guest system in VirtualBox I've forwarded port 2222 on localhost onto port 22 on guest. Afterwards I was able to ssh onto the guest machine, but... As soon as I try to connect by either Putty on my Windows host machine or through my laptop by trying to ssh through forwarded port the connection closes instantly with message like this:
"Connection closed by: 192.168.0.31 port 2222"
Any ideas on how to fix this issue?
virtualbox
asked Dec 5 at 17:56
Stormwaker
63
closed as off-topic by Thomas Ward♦ Dec 5 at 18:48
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This describes a problem that can't be reproduced, that seemingly went away on its own or was only relevant to a very specific period of time. It's off-topic as it's unlikely to help future readers." – Thomas Ward
If this question can be reworded to fit the rules in the help center, please edit the question.
1
Did you check/var/log/syslogor/var/log/auth.logto see if there's any error messages spat out there by the server (in the VM) when you attempt to connect?
– Thomas Ward♦
Dec 5 at 18:27
I did not. But I think I might have located the issue. I didn't realize that mini version will need more than 2 GB of HDD and so set virtual hard drive for that size. After using "df" command I've realized that 100% of the HDD was in use which might have somehow been connected to the issue. I've installed Ubuntu again with a bigger virtual drive and now it's working.
– Stormwaker
Dec 5 at 18:45
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I've installed mini version of Ubuntu 18.04 on VirtualBox using Windows 7 as host. In order to be able to SSH onto guest system in VirtualBox I've forwarded port 2222 on localhost onto port 22 on guest. Afterwards I was able to ssh onto the guest machine, but... As soon as I try to connect by either Putty on my Windows host machine or through my laptop by trying to ssh through forwarded port the connection closes instantly with message like this:
"Connection closed by: 192.168.0.31 port 2222"
Any ideas on how to fix this issue?
virtualbox
asked Dec 5 at 17:56
Stormwaker
63
I've installed mini version of Ubuntu 18.04 on VirtualBox using Windows 7 as host. In order to be able to SSH onto guest system in VirtualBox I've forwarded port 2222 on localhost onto port 22 on guest. Afterwards I was able to ssh onto the guest machine, but... As soon as I try to connect by either Putty on my Windows host machine or through my laptop by trying to ssh through forwarded port the connection closes instantly with message like this:
"Connection closed by: 192.168.0.31 port 2222"
Any ideas on how to fix this issue?
virtualbox
virtualbox
asked Dec 5 at 17:56
Stormwaker
63
asked Dec 5 at 17:56
Stormwaker
63
asked Dec 5 at 17:56
Stormwaker
63
asked Dec 5 at 17:56
Stormwaker
63
asked Dec 5 at 17:56
Stormwaker
63
63
closed as off-topic by Thomas Ward♦ Dec 5 at 18:48
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This describes a problem that can't be reproduced, that seemingly went away on its own or was only relevant to a very specific period of time. It's off-topic as it's unlikely to help future readers." – Thomas Ward
If this question can be reworded to fit the rules in the help center, please edit the question.
closed as off-topic by Thomas Ward♦ Dec 5 at 18:48
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This describes a problem that can't be reproduced, that seemingly went away on its own or was only relevant to a very specific period of time. It's off-topic as it's unlikely to help future readers." – Thomas Ward
If this question can be reworded to fit the rules in the help center, please edit the question.
1
Did you check/var/log/syslogor/var/log/auth.logto see if there's any error messages spat out there by the server (in the VM) when you attempt to connect?
– Thomas Ward♦
Dec 5 at 18:27
I did not. But I think I might have located the issue. I didn't realize that mini version will need more than 2 GB of HDD and so set virtual hard drive for that size. After using "df" command I've realized that 100% of the HDD was in use which might have somehow been connected to the issue. I've installed Ubuntu again with a bigger virtual drive and now it's working.
– Stormwaker
Dec 5 at 18:45
add a comment |
1
Did you check/var/log/syslogor/var/log/auth.logto see if there's any error messages spat out there by the server (in the VM) when you attempt to connect?
– Thomas Ward♦
Dec 5 at 18:27
I did not. But I think I might have located the issue. I didn't realize that mini version will need more than 2 GB of HDD and so set virtual hard drive for that size. After using "df" command I've realized that 100% of the HDD was in use which might have somehow been connected to the issue. I've installed Ubuntu again with a bigger virtual drive and now it's working.
– Stormwaker
Dec 5 at 18:45
1
1
Did you check
/var/log/syslog or /var/log/auth.log to see if there's any error messages spat out there by the server (in the VM) when you attempt to connect?– Thomas Ward♦
Dec 5 at 18:27
Did you check
/var/log/syslog or /var/log/auth.log to see if there's any error messages spat out there by the server (in the VM) when you attempt to connect?– Thomas Ward♦
Dec 5 at 18:27
I did not. But I think I might have located the issue. I didn't realize that mini version will need more than 2 GB of HDD and so set virtual hard drive for that size. After using "df" command I've realized that 100% of the HDD was in use which might have somehow been connected to the issue. I've installed Ubuntu again with a bigger virtual drive and now it's working.
– Stormwaker
Dec 5 at 18:45
I did not. But I think I might have located the issue. I didn't realize that mini version will need more than 2 GB of HDD and so set virtual hard drive for that size. After using "df" command I've realized that 100% of the HDD was in use which might have somehow been connected to the issue. I've installed Ubuntu again with a bigger virtual drive and now it's working.
– Stormwaker
Dec 5 at 18:45
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
I think the issue was somehow connected with no disk space available. After installing Ubuntu on bigger virtual drive the issue disappeared.
answered Dec 5 at 18:46
Stormwaker
63
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
I think the issue was somehow connected with no disk space available. After installing Ubuntu on bigger virtual drive the issue disappeared.
answered Dec 5 at 18:46
Stormwaker
63
add a comment |
up vote
0
down vote
I think the issue was somehow connected with no disk space available. After installing Ubuntu on bigger virtual drive the issue disappeared.
answered Dec 5 at 18:46
Stormwaker
63
add a comment |
up vote
0
down vote
up vote
0
down vote
I think the issue was somehow connected with no disk space available. After installing Ubuntu on bigger virtual drive the issue disappeared.
answered Dec 5 at 18:46
Stormwaker
63
I think the issue was somehow connected with no disk space available. After installing Ubuntu on bigger virtual drive the issue disappeared.
answered Dec 5 at 18:46
Stormwaker
63
answered Dec 5 at 18:46
Stormwaker
63
answered Dec 5 at 18:46
Stormwaker
63
answered Dec 5 at 18:46
Stormwaker
63
63
add a comment |
add a comment |
1
Did you check
/var/log/syslogor/var/log/auth.logto see if there's any error messages spat out there by the server (in the VM) when you attempt to connect?– Thomas Ward♦
Dec 5 at 18:27
I did not. But I think I might have located the issue. I didn't realize that mini version will need more than 2 GB of HDD and so set virtual hard drive for that size. After using "df" command I've realized that 100% of the HDD was in use which might have somehow been connected to the issue. I've installed Ubuntu again with a bigger virtual drive and now it's working.
– Stormwaker
Dec 5 at 18:45