[ask]trouble with ssh

[El_makong]

i have tried to log in to ssh via putty.
i use root,with the password i set on install...but it has denied the access...why is that?
and then,if i reinstall openssh,is it gonna be faulty with proxmox services?
why i want to do this?
well,proxmox's shell is suddenly closed when i open it too long..well,i do some wget to download ISOs...as i am on a long distance with my server and my home connection to upload the iso is too bad...gonna take a long time if i upload ISOs via web interface...

 

[athompso]

Obvious solution:

 # apt-get install screen
# screen

(then, from inside screen

 # wget [URL]http://whatever[/URL]

If you get disconnected for any reason, just log back in and run "screen -R" to reconnect to the running session.
Run

 # man screen

for more information.

However... if you can't log in, how do you know the proxmox session times out if left open too long???

Reinstalling openssh from the repository should not affect PVE in any way, but it also won't solve your problem, whatever that problem is.

-Adam

 

[El_makong]

Obvious solution:

 # apt-get install screen
# screen

(then, from inside screen

 # wget [URL]http://whatever[/URL]

If you get disconnected for any reason, just log back in and run "screen -R" to reconnect to the running session.
Run

 # man screen

for more information.

However... if you can't log in, how do you know the proxmox session times out if left open too long???

Reinstalling openssh from the repository should not affect PVE in any way, but it also won't solve your problem, whatever that problem is.

-Adam

well then..i haven't thought about screen...
then,about closed session,solution accepted..lol

its not the proxmox session..but proxmox shell window suddenly closed and then reconnected as if i open a new shell window...

 

[mir]

Firewall involved which terminates session when idle for some time?

 

[El_makong]

Firewall involved which terminates session when idle for some time?

maybe sessions...btw,its not idle i think..because its on wget process...

but i have resolved this by:
adding new user login,
set ssh no root login
shh login AcceptUsers new user
and then change ssh port. so its still secure..

 

[thheo]

You could use nohup. Just issue nohup wget...etc .

 

[athompso]

Regardless, you're (almost certainly) describing a network problem, not a PVE problem. You should find out what causes this behaviour before running production VMs on that network.
-Adam