IMIDC Dedicated Server Control Panel Guide: Power, VNC Console, Rescue Mode, Password Reset, Reinstall and Traffic

Every IMIDC dedicated server comes with a self-service control panel in the client area. From one page you can power the server on and off, open a browser console that works even when the network is down, boot a rescue system, reset the system password, reinstall the operating system and watch live traffic. This guide walks through each part of the page, what every button does and when to use it.

Where to Find the Panel

1. Log in to the IMIDC client area.
2. Open Services → My Services and click your dedicated server.
3. The control panel appears under the product card, which shows the due date, price and the Renew, Invoices and Tickets buttons.

The panel has five parts: the dark blue Hardware card with the action buttons, Login Details, Bandwidth & Traffic, IP Addresses, and Server details at the bottom with the traffic graph and the current task.

The Hardware Card: IP, Status and Specs

The top left shows the server ID and the primary IP (the copy icon copies it). Under it are the CPU, memory and disks of your machine. The status pill on the right shows Running, Powered off or Status unknown; click its refresh icon to read the power state again.

Power On, Power Off and Reboot

• Power On starts a server that is off.
• Power Off cuts power like holding the power button. Running services stop immediately and unsaved data can be lost, so shut down from inside the OS first when you can (shutdown -h now on Linux).
• Reboot is a hard reset. Use it when the server is frozen and you cannot log in. If you can still log in, reboot from the OS is gentler.

Wait a minute after any power action, then click the refresh icon on the status pill. Do not send power commands while a reinstall or rescue task is running.

VNC Console

The VNC Console button in the top right corner opens the server's screen in your browser. It does not depend on the server's network, SSH or RDP, so it is the tool for situations like these:

• You changed the firewall or SSH port and locked yourself out.
• The network configuration is broken after an edit (a wrong IP, gateway or bridge on a Proxmox host).
• The server stops at a boot error, a file system check or a GRUB prompt.

The console opens in a new window, so allow pop-ups for imidc.com if nothing appears. Log in with the system user and password shown in Login Details.

Rescue Mode

Rescue Mode restarts the server into a small system that runs from the network instead of your disks. Choose Linux or Windows and confirm. Use it when the installed system will not boot or you need to copy data off before a reinstall. Follow progress in Server details → Current Task and work in the rescue system through the VNC console. When you are done, click Exit Rescue in Current Task to boot from your disks again.

What to do inside the rescue system, from mounting disks to repairing GRUB, is covered step by step in using rescue mode to repair a server that won't boot.

Reset Password

Reset Password sets a new password for the operating system account. Type a new password or click Generate, optionally enter a user name (leave it empty for the default administrator account), and confirm. The server may restart to apply it. Use a long random password and store it in a password manager; better still, switch Linux servers to key login as described in setting up SSH key login.

Reinstall OS

Reinstall OS installs a fresh system from the image list:

1. Choose the operating system and the install template.
2. Choose the boot mode and partition layout. The default partitioning suits most users.
3. Generate or enter the new system password.
4. Read the warning and confirm.

Progress appears in Current Task with the current step and a percentage. If you started a reinstall by mistake, click Stop Task while it is still running; this restores disk boot and restarts the server.

Login Details

This card lists the primary IP, system user name, password (hidden until you click Show) and remote port, each with a copy button. Under them is a ready-made connection command, for example ssh [email protected] -p 22 for Linux or the RDP address for Windows. Copy it straight into your terminal. If you are new to this, see logging in via SSH or connecting with Remote Desktop.

Bandwidth & Traffic

• Live inbound / Live outbound: the current traffic rate from the switch port, refreshed every 30 seconds. A green dot means the value is live. No live data means the switch has not reported a sample in the last five minutes.
• Purchased bandwidth: the inbound and outbound port bandwidth configured for your server.
• Traffic this cycle: data used in the current billing cycle. Click it to jump to the traffic graph.
• Current Task: Idle, or the running task. Click it to see details.

IP Addresses

All IPv4 addresses on the server are grouped by subnet. Each row shows the subnet, how many IPs it holds and a Copy button that copies every IP in that subnet, one per line. The subnet with your primary IP is listed first and labelled. Click Expand to see the individual addresses, or Copy all IPs to copy everything at once. This is handy for site-cluster servers with several /24 blocks: paste the list into your binding script from binding a /24 block on Linux. IPv6 subnets appear here too when your server has them.

Traffic Graph

The Traffic tab at the bottom shows the current cycle's usage and a bandwidth graph. Pick a range from 1 hour to the full history. Blue is inbound and teal is outbound; dashed lines mark each direction's 95th percentile and the orange line marks the combined 95th percentile. The table under the graph lists the latest, average and maximum rate for each direction. To understand what the 95th percentile means, read 95th percentile bandwidth billing explained.

FAQ

A button shows an error

Click the status refresh icon, wait a minute and try again. If it still fails, open a ticket with the server IP, the button you used and the exact message.

The VNC window is blank or does not open

Allow pop-ups for imidc.com and try again. The console link is valid for a short time, so open it from the panel each time rather than bookmarking it.

Can I see who logged in to my server?

The panel controls the hardware; logins happen inside the OS. See auditing SSH and panel logins with Telegram alerts.

Still stuck after following these steps? Open a support ticket and the IMIDC 24/7 technical team will help. Include the server IP, what you clicked and a screenshot of the panel so we can pinpoint the issue faster.