Loading...

Knowledge Base
Home 
 
/
 Bluehost Self-Managed VPS: What is Console and How to Use It?
Categories: VPS

Bluehost Self-Managed VPS: What is Console and How to Use It?

The Self-Managed VPS Console is a web-based direct terminal window. It gives you “direct keyboard and monitor” access to your server, even if SSH is blocked, the network is down, or there is a configuration issue. It’s the “emergency access” method for your VPS, just like plugging a keyboard and monitor into a physical server.

When Should I Use the Console?

  • You’ve broken your firewall/SSH and can’t log in remotely.
  • The network is misconfigured, and the server can’t be reached via SSH.
  • Your VPS is booting into emergency/rescue mode or single-user mode.
  • You need to troubleshoot login or OS problems directly.
  • OS upgrades, boot, or configuration failures have locked you out.

How to Access the Console

  1. Log in to your Bluehost Portal.
  2. In the left-hand menu, click Hosting.

    Self Managed VPS
     

  1. Find your Self-Managed VPS/server instance and click Launch Console.

    Self-Managed VPS - Launch Console

  2. The Console login page will appear. Type root in the login field and press Enter.

    Self-Managed VPS - Console - Log in

  3. When prompted, enter your password (you won't see characters as you type). Press Enter.

    Self-Managed VPS - Console - Enter Password

  4. Once logged in, you will see the Console prompt.

    Self-Managed VPS - Console -Promp

Important Troubleshooting Commands

1. Check Disk Usage

df -h

Example output:

Filesystem      Size  Used Avail Use% Mounted on
/dev/vda1        40G   15G   24G  39% /
tmpfs           391M     0  391M   0% /dev/shm

2. View Running Processes

top

Example output (top row):

top - 15:41:23 up 3 days,  2:10,  2 users,  load average: 0.10, 0.03, 0.05
Tasks: 101 total,   1 running, 100 sleeping,   0 stopped,   0 zombie
%Cpu(s):  1.0 us,  0.8 sy,  0.0 ni, 98.0 id,  0.0 wa,  0.0 hi,  0.2 si,  0.0 st

3. Check SSH Service Status

sudo systemctl status sshd

Example output:

● sshd.service - OpenSSH server daemon
   Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled)
   Active: active (running) since Wed 2024-06-26 15:00:20 UTC; 1h 2min ago

4. Restart SSH Service

sudo systemctl restart sshd

5. Reset the Root/User Password

passwd

Example output:

Changing password for user root.
New password:
Retype new password:
passwd: all authentication tokens updated successfully.

6. Edit Config Files (nano/vi)

nano /etc/ssh/sshd_config
# Example shows nano editor with the file content loaded

7. View System Logs

journalctl -xe

Example output (portion):

Jun 26 15:41:35 vps-name systemd[1]: Starting OpenSSH server daemon...
Jun 26 15:41:35 vps-name sshd[7451]: Server listening on 0.0.0.0 port 22.

8. Fix Broken Firewall Rules

sudo systemctl stop firewalld
sudo ufw disable

(One or both, depending on your firewall)

9. Check Network Interfaces

ip a

Example output:

2: eth0:  mtu 1500 ...
    inet 198.51.100.23/24 brd 198.51.100.255 scope global eth0

10. Ping an External Server

ping 8.8.8.8

Example output:

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=107 time=14.1 ms

11. Remount Disks (in Rescue Mode)

mount -o remount,rw /

Troubleshooting Commands Table

Command/Purpose Example Description
Check disk usage df -h See if disk space is full (can block logins or app startup).
View running processes top, htop Shows CPU, RAM, load, and active processes.
Check SSH service status sudo systemctl status sshd Shows if SSH is running. Restart it if necessary.
Restart SSH service sudo systemctl restart sshd Restart OpenSSH server.
Reset root/user password passwd Change the password if account is locked out.
Edit config file nano /etc/ssh/sshd_config Fix misconfiguration, e.g., in SSH setup.
View logs journalctl -xe Boot/service error messages and details.
Disable firewall sudo systemctl stop firewalld
sudo ufw disable		 Allows access if you locked yourself out via firewall rules.
Check network interfaces ip a Review your assigned IPs to ensure network is up.
Test connectivity ping 8.8.8.8 Confirm outbound network access is working.
Remount / as read/write mount -o remount,rw / For "read-only filesystem" errors in rescue mode.

Tips & Precautions

  • The Console is more “basic” than SSH—text only, may lack copy-paste, and can sometimes lag.
  • Be careful when running destructive commands: the Console has full root power.
  • Always check your keyboard layout (sometimes it defaults to US QWERTY), especially for passwords!
  • Use sudo only as needed.
  • Log out when finished.

Summary

The Console is your safety net when everything else fails to connect via SSH. Essentially, you will be using the same commands that you would use if you were connecting normally via SSH; just doing it via a virtual screen and keyboard. Remember to test every command and watch out for errors.

Loading...