Emergency Console allows you to connect to your server to investigate issues when regular remote access methods like SSH (Linux) or RDP (Windows) are unavailable.
Usually, the Emergency Console is accessible right from your client area web interface. However, sometimes the web console may not work correctly, or you may simply want to use a different connection method. For such cases, on the same emergency console page, we also provide VNC connection information that will allow you to connect to the server by using third-party VNC clients.
You can use any third-party VNC client or remote connection apps that support VNC. For example, we recommend using:
In this guide, we will use TigerVNC, however the principle is the same for all VNC clients, so you can apply it to any app.
1. Generate Emergency Console
First, you have to generate Emergency Console for your server. To do this, follow these steps:
Login to the Clients Area;
At the top of the page, select Services ---> VPS;
Press the "Manage" button;
Choose the "Emergency Console" button from the side menu on the left;
Choose how many hours the Web Console should be active and click "Launch Emergency Console". The Emergency Console will work for the selected time.
After starting the emergency console generation process, you will see a window with a notification that your server is launching the web console. Usually this is quick process, but sometimes it can take longer (about 5-15 minutes).
2. Find and copy VNC credentials
Once the emergency console is generated, you will see a page with a link to web console and just below that, the credentials for connecting via VNC that you will have to use:
You will have to copy VNC Host and VNC Password (press "Click here to show password" to display the VNC password).
Please note that these credentials are temporary and will expire at the time specified on the Emergency Console page (see screenshot above). You will not be able to connect with them once they expire.
3. Connect by using your VNC client
On your computer, open VNC client by your choice (TigerVNC in our case) and you will see the address bar. In this bar, paste the VNC Host that you copied in step 2:
Then click "Connect". In some applications, simply pressing Enter is enough to continue.
Next, enter or paste (press Ctrl + V) the VNC password from step 2:
If you receive an error stating that the connection cannot be established, your credentials and the emergency console have likely expired. In this case, you will need to regenerate emergency console.
4. Enter your root/administrator credentials
After entering your VNC password, you'll be redirected to the emergency console. There, you'll need to enter your root (if you're using Linux) or Administrator (if you're using a Windows VPS) credentials.
You can find root/administrator credentials in client area:
Login to the Clients Area;
At the top of the page, select Services ---> VPS;
Press the "Manage" button;
Click on "Login details" from the side menu on the left.
4.1 Linux (Linux VPS, Container VPS, Storage VPS)
On Linux, you will see this window:
First enter username and then password. Please note that the password will not be visible in Linux.
Copying and pasting also does not work in the emergency console. Simply enter the password manually and press Enter.
4.2 Windows VPS
On Windows VPS, you will see the default authorization window:
Next, you should send Ctrl-Alt-Del to the screen. The way to do this varies from program to program, but there should usually be a menu that allows you to send output (in this case Ctrl-Alt-Del) to the Windows screen to unblock it.
In TigerVNC, press F8 on your keyboard. The menu with different options will appear. Click "Send Ctrl-Alt-Del":
Then, enter your administrator password:
Copying and pasting won't work. Enter the password manually, then press Enter.
5. Final Notes
That's it! You have connected to your server and can now troubleshoot the issue you are having with your server (by checking logs, resource usage, network settings, disk storage, custom settings, etc.).
We have guides that will help you to investigate the issue with your server:
Find even more helpful guides to help you troubleshoot server issues in our knowledgebase.








