Open the Remote Console (KVM / IPMI) on Your Server — Portal and API

Method 1 — In the portal

Bare-metal servers: the remote console

1. Log in at amoni.app, open Servers and click the server.
2. Click Console in the header, or the Console tab. The same panel opens either way.
3. Your public IP is filled in automatically with the address you are browsing from. Check it. If you will open the console from a different network, or a VPN is about to come up, correct it now.
4. Leave Console mode on Standard. Switch to Web only if Standard turns out not to work with this server's controller; the troubleshooting section says how to tell.
5. Click Launch Console. Preparing the session takes a few seconds.
6. The panel turns green with Console session active and a link. Click it; the console opens in a new tab. The line underneath repeats which address the session admits.

The console opens as a Server Console page: the server's name and a Connected badge in the header, a CTRL + ALT + DEL button, and the machine's screen from power-on onwards, BIOS and boot loader included. On most of our hardware the screen is the controller's own viewer running inside that page, with its menu bar (Virtual Media, Macro, Power Control and so on) along the top of the window. The small toolbar on the left belongs to the page itself: keyboard, clipboard, full screen, settings, disconnect.

If the screen is black, the server is probably powered off: use Start in the portal header (see reboot and power), or the viewer's own Power Control menu.

Boot from an installer or rescue image (virtual media)

The console can present an image from our library to the server as if a USB drive or DVD were plugged into it. That is how you run an installer we do not offer as an automated reinstall, boot a live system to repair or copy data, or run a vendor utility. It works whatever state the installed system is in.

1. In the viewer's menu bar, open Virtual Media → Virtual Storage.
2. On the Device1 tab, set Logical Drive Type to ISO File and click Open Image….
3. Pick an image from the library. It holds current installers (AlmaLinux, Ubuntu Server, Proxmox VE), a recovery image, netboot.xyz for anything else that boots over the network, and vendor tools such as the Intel network boot utility. Click Open.
4. Click Plug in, then OK. The image is now attached; the server sees a new removable drive.
5. Reboot the server (viewer Power Control → Reset, or Reboot in the portal) and open the one-time boot menu during power-on, F11 on most of our machines. Choose the virtual drive from the list; it appears as a USB or CD-ROM entry alongside the installed disks and the network boot entries.
6. When you are done, come back to Virtual Storage and click Plug Out, so the next reboot goes back to the disk.

Installing an operating system this way is a manual install: it does not set the hostname, keys or reverse DNS for you, and the portal will not know which OS is on the machine until you tell it. For the supported images, the automated reinstall is faster and records everything.

Bare-metal servers: management interface access

Lower on the same tab. Use this only when the console above does not work with your hardware, or when you need the controller's own interface.

1. Check Your public IP, the same rule as above.
2. Choose Keep open for: one to four hours. The session closes itself when the time runs out.
3. Click Open management access.
4. The panel shows Access is open with a link to the management interface, a username, and a “view it once” link for the password. Open that link straight away and copy the password: it is revealed once and expires with the session.
5. When you are done, click Close access now rather than leaving it to expire.

The login is a temporary operator account created for this session, never the controller's administrator. It disappears when the session closes.

Cloud instances

1. Open Virtual Machines and click the instance.
2. Click Console in the header. It is available in every power state, stopped included, because the VM that will not boot is exactly the one that needs it.
3. The console opens in a new tab. The link behind it is single-use and valid for one minute, so if the tab was blocked by a pop-up blocker, allow pop-ups for amoni.app and click Console again.

Cloud consoles are not locked to an address; the single-use link is the protection. What you see is the instance's serial terminal: text only, which is why a Linux instance shows a login prompt rather than a desktop. Log in with the root password (see reset the root password if you do not have it). Cloud instances boot images differently; that flow is documented separately once it is available in the portal.

Method 2 — With the API

Console sessions are minted for a browser, so the API's job is to hand you a launch URL; you open it where you sit. You need a key with the Servers scope (servers.write) or the VMs scope (vms.write). Reference: api.amoni.app/v1/docs.

Bare metal: remote console

Pass the public address that will open the console. The API cannot detect it: the machine calling the API is rarely the one with the browser.

MY_IP=$(curl -s https://api.ipify.org)
curl -s "https://api.amoni.app/v1/servers/955/console?authorized_ip=$MY_IP&mode=standard" \
  -H "Authorization: Bearer nr_live_..."

{
  "success": true,
  "data": {
    "available": true,
    "console_url": "https://console.amoni.app/s/7f3a9c2e1b/kvm",
    "mode": "standard",
    "authorized_ip": "198.51.100.77"
  }
}

Open console_url in a browser on 198.51.100.77. mode accepts standard (default) or web.

Bare metal: management interface access

curl -s -X POST https://api.amoni.app/v1/servers/955/bmc-access \
  -H "Authorization: Bearer nr_live_..." \
  -H "Content-Type: application/json" \
  -d '{"authorized_ip": "198.51.100.77", "hours": 2}'

{
  "success": true,
  "data": {
    "url": "https://bmc-4821.access.amoni.app",
    "expires_at": "2026-09-15 17:30",
    "authorized_ip": "198.51.100.77",
    "operator_user": "op-7f3a9c",
    "credentials_url": "https://amoni.app/secret/9Qk2mX"
  }
}

hours is 1 to 4, default 3. The password is not in the response: credentials_url reveals it once, then expires with the session. Fetch it immediately and store it somewhere safe. Close the session when done:

curl -s -X DELETE https://api.amoni.app/v1/servers/955/bmc-access \
  -H "Authorization: Bearer nr_live_..."

{ "success": true, "data": { "message": "Remote access closed." } }

Closing when nothing is open is not an error; the message then says “No remote access session to close.”

Cloud instances

curl -s -X POST https://api.amoni.app/v1/vms/990204/411/console \
  -H "Authorization: Bearer nr_live_..."

{ "success": true, "data": { "launch_url": "/api/v2/portal/pve-launch/Xk29...a1" } }

The launch URL is relative to the portal: open https://amoni.app + launch_url. It is single-use and expires after 60 seconds, so mint it when you are ready to click, not before.

What the API will tell you