Basics Difficulty: Beginner

First steps with a netcup VPS

From a freshly ordered netcup server to a ready-to-use system: SSH login, system updates, a sudo user and the most important first steps.

Jul 13, 2026 · 4 min read ·Duration: approx. 30 minutes

Table of contents

You’ve ordered your first netcup server – congratulations! Before we fire up the kitchen, let’s set the system up cleanly.

What are we building?

By the end of this tutorial, your VPS runs a current Debian 13 with all security updates, and you work with your own user with sudo rights instead of permanently as root. That’s the foundation for all the other recipes in the Serverküche – from hardening SSH to your first application.

Tip

All commands are written for Debian 13. On Ubuntu they work almost identically.

Prerequisites

An ordered netcup server with the credentials from your customer account
A terminal on your machine (Linux/macOS) or an SSH client like PuTTY (Windows)

Not sure which server size you even need? The server calculator estimates the RAM and CPU you’ll need for your planned services and suggests a matching netcup plan.

🍳 Recommendation Ad

VPS 1000 G12

4 vCores · 8 GB RAM · 256 GB NVMe

from €10.36/month

A good start for most self-hosting projects.

Go to netcup →

💶 5 € voucher for new netcup customers: 36nc17844976032 (new customers only, no domains)

Step by step

Step 1: Log in via SSH

Log in with your server’s IP address as root. You’ll find the IP and the password in the credentials from your customer account:

Terminal

ssh root@YOUR_SERVER_IP

On the very first login, SSH asks whether you want to trust the server:

Ausgabe

The authenticity of host 'YOUR_SERVER_IP' can't be established.
...
Are you sure you want to continue connecting (yes/no/[fingerprint])?

Answer yes – your machine remembers the server from now on. After that you land on a prompt like root@v12345:~#.

Step 2: Update the system

Freshly delivered images are rarely up to date. So the first thing to do is fetch all updates – security updates in particular should never wait:

Terminal

apt update && apt upgrade -y

apt update fetches the current package lists, apt upgrade -y installs all available updates without prompting.

Warning

Reboot the server after a kernel update (reboot) so the changes take effect. On a fresh Debian there’s no automation for this yet – the safest bet is a reboot right after the first big update. Debian does not create the marker file /var/run/reboot-required (which indicates a pending reboot) on kernel updates by default – you’ll set up the matching hook later together with automatic updates.

Step 3: Create a sudo user

Don’t work as root permanently: a typo with full rights can wreck the entire system, and having your own user is the prerequisite for disabling root login completely later. Create a user – we’ll call it koch (“cook”) here, but you can pick any name:

Terminal

adduser koch

You’ll be asked for a password and a few optional details (you can skip the details with Enter). After that, give the user sudo rights:

Terminal

usermod -aG sudo koch

Step 4: Test the new user

Check in a new terminal session (keep the root session open!) that login and sudo work:

Terminal

ssh koch@YOUR_SERVER_IP
sudo whoami

After entering your password, sudo whoami should return root. From now on you continue working with this user.

When things go wrong

ssh: connect to host … port 22: Connection timed out. Usually the IP was mistyped or the server isn’t fully provisioned yet. Check the IP in your customer account and whether the server is shown as “online” there. Wait a few minutes after ordering.

Permission denied, please try again on root login. Wrong password – often a copy-paste issue with invisible trailing spaces, or a different keyboard layout. Copy the password without surrounding spaces directly from the credentials.

WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!. The server was reinstalled and has a new host key – SSH rightly raises the alarm. If you reinstalled it, remove the old entry with ssh-keygen -R YOUR_SERVER_IP and reconnect. If you didn’t reinstall, investigate before you connect.

sudo: command not found as the new user. On minimal images the package is sometimes missing. Install it as root: apt install sudo. Then check that the user is in the group: groups koch must contain sudo – otherwise repeat step 3 and log out and back in once.

Maintenance & backups

Updates: You should schedule sudo apt update && sudo apt upgrade at least weekly – or automate security updates with unattended-upgrades.
Snapshots: Create a snapshot in the netcup Server Control Panel (SCP) before bigger changes. It’s your safety line while you don’t have a proper backup strategy yet – but a snapshot does not replace a backup outside the server.
Credentials: Keep the root password safe (password manager). Via the VNC console in the SCP you can still reach the server even when SSH is stuck.

You’ll find both in the server overview of the SCP: the VNC console is under the “Bildschirm” (Display) tab, and the remaining snapshot quota is shown in the status block.