Skip to content

netcup Documentation

Server

Troubleshooting Server Login

Common causes and solutions for login problems on your vServer.

There may be several reasons why you are having trouble logging in to your vServer. See below for some possible causes and solutions. If the problem persists, please contact Customer Support.

1. Standard Login Details for the Operating System of a vServer

We provide our vServers with a Debian operating system by default.

  • The default username is always “root”.
  • You received the password via email after the server was provided.

The password was sent to you in a separate email. This password is different from the one you use to log in to the Server Control Panel or Customer Control Panel.

2. Login via the Screen in the Server Control Panel

You can access your server via the menu item Screen in the Server Control Panel (SCP). If you are using the pre-installed operating system, you can use the default username “root” and the saved password.

 

Please note the following:

  • For security reasons, entries in the password field are hidden.
  • You cannot copy and paste text.
  • The keyboard layout on the screen may differ from the layout on your keyboard. Check in the user field to see if the entries are being transmitted correctly. If this is not the case, adjust the VNC keyboard layout under the menu item Settings.
Highlighted section in the SCP for changing the keyboard layout.

3. Login via Remote Connections

Secure Shell (SSH)

Getting Started

  1. First, check whether you can log in via the screen in the Server Control Panel (SCP). If you cannot log in, the login details you are using may be incorrect.
  2. Also verify that the server has an active internet connection. You can ping your server to check this: ping 1.2.3.4
Server Ping

If the server does not have an active internet connection, go to: Troubleshooting Network Issues

Access via Screen possible and Internet Connection Active

If you can access via the screen and there is an active internet connection, check the following settings:

  • Verify that SSH is active: systemctl status sshd
Checking SSH
  • Check whether SSH access is allowed for “root”: /etc/ssh/sshd_config

PermitRootLogin yes > SSH access via the user “root” is allowed.

PermitRootLogin no > SSH access via the user “root” is not allowed.

For security reasons, we recommend creating a separate user for SSH and disabling SSH access via “root”.

  • Check whether the SSH port is open: If an error message such as “Port 22: Connection refused” appears, check whether SSH is running and whether the port is open. It is possible that a firewall is blocking access.

Common Error Messages

Remote Desktop Protocol (RDP)

Please note that RDP is not preinstalled. Therefore, remote access via RDP is only possible if you have installed and configured it yourself.

4. Frequently Asked Questions (FAQ)

Last update: 24 April 2026

Was this article helpful?