Servers

Our enterprise-grade servers offer several features such as real-time provisioning, private networks, nested virtualization, and autorecovery. You can tailor your requirements to seamlessly scale complex architectures across multiple hardware profiles.

Billing #

Servers are only billed while they are turned on. Within a server’s operating system, it is possible to put it into a suspended or sleeping a state, which we do not recognize. These servers will still be billed, and if the server has to be migrated to another node, we will wake the server up.

Affinity Zones #

By configuring your servers in different Affinity Zones, you can selectively distribute your servers (physical distance) or selectively consolidate them (low physical distance).

You can choose between three Affinity Zones (Zones A, B or C). If you choose “Auto”, your server can work with the best performance at that moment. By default, servers are created with the “Auto” setting.

User Data #

You can use User Data to automate the process of configuring your cloud instance when it boots.

To make this process even easier, you can now add your User Data when creating a Server, both in the Cloud Panel as well as directly in the related API call.

User Data for Linux Users #

For Linux systems, we support Cloud-init, which is a tool that reads your User Data and uses it to configure your instance at launching time. You can use Cloud-init to perform a variety of tasks, including installing packages, running scripts, and creating users.

User Data for Windows Users #

For Windows systems, we support Cloudbase-init which provides the same features as Cloud-init.

By using User Data and Cloud-init or Cloudbase-init, you can save time and effort in setting up and configuring your cloud instances.

Autorecovery #

With autorecovery you define whether or not you wish us to automatically restart your server in case of an error and thus try to recover it. It increases server availability by restarting the server within a specified time after a system hangs. Autorecovery is enabled by default, and can be configured.

Hardware Profile #

Our hardware profile defines a standard set of hardware configuration settings. Using a hardware profile ensures that a consistent hardware configuration is used in the server and your server meets the right specific technical requirements.

Note: all profiles or custom combinations, except Q35, are deprecated and will eventually be removed.

Warning: We do not support profiles other than Q35 under our SLA, which includes limited support for servers running profiles other than Q35.

We currently offer the following preset hardware profiles:

Custom Configurations #

You can completely configure these combinations yourself via advanced settings.

VNC (Remote Console) #

Access to the VNC console requires user and password access to the server.

When booting from an ISO image, using the VNC console is recommended.

Networks #

Up to eight networks can be connected to one server. One of them can be the public network (Internet).

More information on Networking and IP address can be found in the Network section.

IP Addresses #

We support one IPv4 and one IPv6 address via our API.

More information regarding linked IPs can be found in the Network section.

Storages #

A total of eight storages, or 15 for managed Kubernetes can be connected to one server. However, only one of the Rocket Storages can be connected to a server (with additional Distributed Storages).

ISO Images #

A total of one ISO image can be mounted on a server.

Firewall #

One firewall template can be created per server network connection, with additional local firewall rules per server network connection.

Running Server #

Please note that as long as the server is switched on, the following actions are blocked:

• Change Network Settings (IPv4/6)
• Change Hardware Profile
• Disconnect/Connect Storage

Shutdown Server #

Servers can be started and stopped via the power button at the right corner. The safest way to switch off your server is via ACPI shutdown.

Delete Server #

In order to delete a server, it needs to be turned off first.

FAQs #

How do I connect to a server? #

We offer direct VNC access from within the Panel. Using the VNC, you can access the server’s hardware console to install, configure and restore your server. The VNC console is intended more as an emergency rescue console.

For daily use and best performance, connect to your cloud server via SSH client (Linux, Mac) to establish a remote terminal connection. For Windows, install a third-party application like PuTTY. For Windows machines, use Windows Remote Desktop/RDP.

How can I delete a server? #

Click on the item you want to delete and drag and drop it to the trash can that appears as soon as you click on it.

Are my servers assigned to a physical host system? #

No. Your servers are optimally distributed in the cluster according to load and to ensure the best possible redundancy using our smart proactive algorithms to optimize the cluster and the servers running on it without impairments.

How do I request or delete IP addresses? #

You can manage your IP addresses within the IP Manager IP Manager. The independent IP Manager offers you the greatest possible flexibility.