Skip to content

Search is only available in production builds. Try building and previewing the site to test it out locally.

First Login

After your server is provisioned, you’ll receive an email with your login credentials. This guide covers how to connect for the first time.

Open your terminal and run:

Terminal window
ssh root@YOUR_SERVER_IP

When prompted, enter the root password from your provisioning email.

  1. Download PuTTY
  2. Open PuTTY and enter your server IP in the “Host Name” field
  3. Ensure Port is set to 22 and Connection type is SSH
  4. Click “Open”
  5. Accept the server’s host key when prompted
  6. Login as root with the password from your email

Windows 10/11 includes OpenSSH by default:

Terminal window
ssh root@YOUR_SERVER_IP
  1. Press Win + R to open Run dialog
  2. Type mstsc and press Enter
  3. Enter your server IP address
  4. Click “Connect”
  5. Login with:
    • Username: Administrator
    • Password: From your provisioning email
  1. Download Microsoft Remote Desktop from the App Store
  2. Click “Add PC”
  3. Enter your server IP
  4. Double-click to connect
  5. Enter Administrator credentials

After your first login, we recommend:

Terminal window
# Update system packages
apt update && apt upgrade -y # Debian/Ubuntu
# or
dnf update -y # CentOS/AlmaLinux/Rocky
# Set your timezone
timedatectl set-timezone YOUR_TIMEZONE
# Change root password
passwd
  1. Change the Administrator password immediately
  2. Enable Windows Update
  3. Configure Windows Firewall
  4. Install required software
  1. Change default password - Do this immediately
  2. Set up SSH keys - For secure passwordless login
  3. Configure firewall - Restrict access to necessary ports only
  4. Enable 2FA - Protect your Hostcore account at hostcore.cloud
  • Server may still be booting. Wait 2-3 minutes.
  • Check if the correct port is open (22 for SSH, 3389 for RDP)
  • Verify you’re using the correct username (root for Linux, Administrator for Windows)
  • Check the password is entered correctly (passwords are case-sensitive)
  • Verify the IP address is correct
  • Try accessing via VNC Console from the dashboard