Debian disables root ssh access per default. You need to edit /etc/ssh/sshd_config and uncomment PermitRootLogin if you really want to allow direct remote root access. Set it to prohibit-password to only allow cryptographic key based logins, or yes if you want to allow root to login with a password (please don't). The usual recommendation is to log in as an unprivileged user and use sudo to execute commands with elevated privileges.
Debian disables root ssh access per default. You need to edit /etc/ssh/sshd_config and uncomment PermitRootLogin if you really want to allow direct remote root access. Set it to prohibit-password to only allow cryptographic key based logins, or yes if you want to allow root to login with a password (please don't). The usual recommendation is to log in as an unprivileged user and use sudo to execute commands with elevated privileges.
So, just say that I have to do everything via the Netcup terminal. Why can I literally not update anything like apt-get update, apt update, or install ufw?
It keeps getting stuck at 0%.
You can "fix" your ssh access as described or use the web console. The update fails because of an unresolved name. Try using different name servers or a different mirror.
So, just say that I have to do everything via the Netcup terminal.
No, he does not.
Change the ssh-settings as described and then login with a client.
No, he does not.
Change the ssh-settings as described and then login with a client.
Hier is hoe je je situatie kunt beschrijven:
I followed the suggestion to change PermitRootLogin prohibit-password to PermitRootLogin yes in /etc/ssh/sshd_config, saved the changes, and restarted the SSH service using:
sudo systemctl restart ssh
Despite this, I still cannot log in via the terminal on my MacBook. When I try to connect using:
ssh root@<IP_ADDRESS>
I get a connection timed out error.
Additionally, I updated my /etc/apt/sources.list to use different Debian mirrors, as shown below:
deb http://deb.debian.org/debian bookworm main
deb-src http://deb.debian.org/debian bookworm main
deb http://deb.debian.org/debian-security bookworm-security main
deb-src http://deb.debian.org/debian-security bookworm-security main
deb http://deb.debian.org/debian bookworm-updates main
deb-src http://deb.debian.org/debian bookworm-updates main
Even after making these changes, running apt update still gets stuck at 0%.
Could you provide guidance on what might be causing these issues and how to resolve them?
I followed the suggestion to change PermitRootLogin prohibit-password to PermitRootLogin yes in /etc/ssh/sshd_config, saved the changes, and restarted the SSH service
Is this also set?
PasswordAuthentication yes
And don't forget to check in /etc/ssh/sshd_config/ if there is a file called "50-cloud-init.conf" (for example). If so, there may be an entry that says "
PasswordAuthentication no" - then change this to "yes", because this entry has higher priority.
on the debian images from netcup you dont need to change these lines, normally they are set by cloudinit.
there is a internal problem in the dns. (or something)
i cant ping oder tracert the ip of his vps
tracert 152.53.118.84
Routenverfolgung zu v2202412233766305944.supersrv.de [152.53.118.84]
über maximal 30 Hops:
1 <1 ms <1 ms <1 ms 10.10.10.1
2 25 ms 5 ms 5 ms p3e9bf32c.dip0.t-ipconnect.de [62.155.243.44]
3 13 ms 12 ms 12 ms f-ed11-i.F.DE.NET.DTAG.DE [217.0.192.118]
4 11 ms 12 ms 29 ms 80.156.161.186
5 15 ms 15 ms 15 ms ae1-0.bbr01.anx84.nue.de.anexia-it.net [144.208.208.140]
6 15 ms 15 ms 15 ms ae0-0.bbr02.anx84.nue.de.anexia-it.net [144.208.208.138]
7 * 2020 ms * 144.208.208.243
8 * * * Zeitüberschreitung der Anforderung.
9 * * * Zeitüberschreitung der Anforderung.Is this also set?
PasswordAuthentication yes
Yes i changed now to Media to Ubuntu and when i try to update also stuck on 0%. There is something wrong with the server//
on the debian images from netcup you dont need to change these lines, normally they are set by cloudinit.
there is a internal problem in the dns.
i cant ping oder tracert the ip of his vps
Codetracert 152.53.118.84 Routenverfolgung zu v2202412233766305944.supersrv.de [152.53.118.84] über maximal 30 Hops: 1 <1 ms <1 ms <1 ms 10.10.10.1 2 25 ms 5 ms 5 ms p3e9bf32c.dip0.t-ipconnect.de [62.155.243.44] 3 13 ms 12 ms 12 ms f-ed11-i.F.DE.NET.DTAG.DE [217.0.192.118] 4 11 ms 12 ms 29 ms 80.156.161.186 5 15 ms 15 ms 15 ms ae1-0.bbr01.anx84.nue.de.anexia-it.net [144.208.208.140] 6 15 ms 15 ms 15 ms ae0-0.bbr02.anx84.nue.de.anexia-it.net [144.208.208.138] 7 * 2020 ms * 144.208.208.243 8 * * * Zeitüberschreitung der Anforderung. 9 * * * Zeitüberschreitung der Anforderung.
yeah it is frustrating! server is not working properly
Contact the Support and wait
Contact the Support and wait
Done, i hope they will answer asap..
Hello alih3meed,
Thank you for making us aware of this.
Our network operation center has resolved the issue and it should be working fine now. We apologize for the inconvenience.
I wish you happy holidays.
