Getting connected after delivery
Find credentials in the control panel. Use SSH for Linux and RDP for Windows.
For delivered orders, open the machine details from the control panel. Use the connection address and login details shown for that specific machine.
Check the machine before connecting
AmdMetal does not display machine passwords on public pages. Once payment and delivery are complete, sign in to the account used to place the order, then find the relevant order and machine details in the control panel. Check the machine ID, selected operating system, connection address and login credentials.
Use the order number and machine ID to identify the server. If managing multiple machines, check the memory configuration and operating system first to avoid using credentials for a different machine.
Copy the address, account and authentication details from the machine details. Do not guess the username or port based on a guide. Check for leading or trailing spaces, and never paste a password into a terminal command, screenshot or public discussion.
Use SSH for Linux, FreeBSD and Proxmox VE; use RDP for Windows Server. The connection method depends on the operating system selected for the order, not the operating system on the local computer.
If delivery is not complete or the machine details do not show connection information, do not try to sign in using the example address in this guide. Check order or delivery status through a support ticket in the control panel.
Linux · FreeBSD · Proxmox VE
Enter the connection details shown in the control panel in a local SSH client. If the client can save connection profiles, name each one with its machine ID so every profile corresponds to the right order.
On the first connection, the client may report that the host identity has not yet been saved. Confirm that the address matches the machine details before accepting the identity prompt. If the host key changes, do not simply delete the old record and ignore the warning. Check whether the system was reinstalled, and submit a support ticket if the change cannot be verified.
A first-connection prompt is different from a host identity change warning.
Authenticate using the method shown in the control panel. When entering a password, the terminal may not display any characters; this does not mean the input was ignored. After logging in, check account permissions and the operating system version before updating the system. Use package-management commands that match the selected distribution.
An authentication failure does not mean the network is unreachable.
Keep the private key secure locally and add the public key to the target account. Keep the current session open, then use a separate session to verify that key-based login works before changing password authentication settings or the firewall. Do not close the existing management connection until the new one has been tested.
Test the new connection before restricting the existing one.
Example checks for the 256GB configuration
The excerpts below explain the output fields; they do not show the live status of a machine. The IP address uses a documentation-only range. Replace the account name and connection parameters with the actual details shown in the control panel.
$ ssh -l ACCOUNT_FROM_CONSOLE 203.0.113.10
The authenticity of host cannot be established.
Are you sure you want to continue connecting (yes/no)? yes
$ lscpu
Model name: AMD EPYC 7543P 32-Core Processor
CPU(s): 64
$ free -g
total
Mem: 251
$ nvme list
Node Model Namespace Usage
/dev/nvme0n1 NVMe SSD 1 1.00 TB
/dev/nvme1n1 NVMe SSD 1 1.00 TBCPU(s): 64 represents 64 logical threads. The processor has 32 physical cores; thread count is not the same as physical core count.
Memory: about 251 is the system reading shown in this example for the 256GB configuration. Unit conversion, system usage and the way a tool reports values can all affect the result, so do not rely on a single reading to verify the hardware.
Two NVMe device entries represent two directly attached drives of about 1TB each; they do not indicate that the drives are mirrored. If the relevant tools are not installed, install them using the operating system documentation. A missing tool does not mean a drive is missing.
Do not format disks, wipe partitions or create a storage pool during disk checks. The two NVMe drives have no hardware RAID; customers are responsible for configuring redundancy and backups.
Windows Server
Open an RDP client and connect using the first IPv4 address and login credentials shown in the machine details. The Windows system language is the English, Traditional Chinese or Simplified Chinese option selected when ordering. The language of the local client does not change the remote system language.
Verify the connection address and login account separately. Do not enter the account name in the computer address field. If the client has saved an old password, retrieve the current credentials from the control panel instead of repeatedly trying the old ones.
After the first login, check the operating system version, network settings and firewall rules. Keep the current session open before changing remote desktop settings, and verify the new connection settings to avoid losing access.
The Windows licence version and language are selected during configuration. If a connection fails, record the original client error. A certificate warning, account authentication failure and connection timeout are different issues.
Managing multiple IPv4 addresses
Regardless of how many dedicated IPv4 addresses are assigned, use only the first address listed in the control panel for SSH or RDP. Other addresses are for binding to sites, virtual machines or services within the system. An assigned address is not necessarily available for direct login to the host.
| Address type | Where it is used | Check before connecting |
|---|---|---|
| First IPv4 address | SSH or RDP management connection to the dedicated server | Copy it from the control panel and check the machine ID. |
| Other IPv4 addresses | Bind to a site, virtual machine or service within the system | Check address binding, routing, firewall and service listening settings. |
| Example address | Illustrates command structure and field meanings | Not a delivery address; do not use it to connect. |
When planning additional addresses, record which address is associated with each service and where it is bound within the system. Keep the management connection open before changing network interfaces, bridges or virtual machine networking. Do not assign the host management address to another virtual machine.
After changing network settings
If SSH or RDP stops working after a change to a network interface, route or firewall, record the last change and the client error first. Avoid changing several settings repeatedly, as later changes may obscure the original cause.
The browser-based graphical session in the control panel is for emergency use when remote login is unavailable, such as after a network configuration error. Use SSH or RDP for routine access. Describe the issue and any actions requiring assistance in a support ticket through the control panel.
For an AmdMetal DGX Spark, find the credentials in the control panel and connect over SSH. Hard reboots and reinstallations are handled through a support ticket. For product details, see the DGX Spark overview.
Gather the details in one go
If the connection still fails, submit a support ticket through the AmdMetal control panel. Specify whether the issue is a connection timeout, connection refused, authentication failure or a disconnection after login. Note whether it occurred on the first connection or after an operating system or network change.
Include the machine ID, related order, selected operating system and SSH or RDP client. If managing several machines, identify which one is affected.
Include the full error message or a screenshot, the approximate time and time zone, whether login has ever succeeded, and any recent network or authentication changes. Keep the error visible in screenshots, but hide passwords and private keys.
Note whether the first IPv4 address was verified, the credentials were retrieved again, and the connection was tested from another local network. For disk or system operations, include the backup status. Never paste private keys or account passwords into a support ticket.
AmdMetal is responsible for the hardware and network; customers manage system settings, business data and backups. Accurate incident details help distinguish connection, authentication and system configuration issues.