Skip to content

Server Settings

You can configure various settings for each server from the Appliku dashboard.

Accessing Server Settings

  1. Open the Appliku dashboard
  2. Navigate to the Servers tab
  3. Click on the server you want to configure
  4. Go to the Settings section

Server Alias

You can set a custom alias for your server to make it easier to identify in the dashboard. The alias is a display name only and does not affect the server's hostname or DNS configuration.

This is especially useful when you have multiple servers and want to label them by purpose (e.g., "Production Web", "Staging", "Build Server").

SSH Port

By default, Appliku connects to your server on port 22. If your server uses a non-standard SSH port, you can update it in the server settings.

Changing the SSH port in Appliku does not change the port on the server itself. You must configure the SSH port on the server first, then update it in Appliku to match.

Warning

If you change the SSH port on your server without updating it in Appliku, Appliku will lose the ability to connect to the server. Make sure to update the port in Appliku immediately after changing it on the server.

Removing a Server

You can remove a server from Appliku when you no longer need it. The removal process differs depending on the server type.

Removing a Cloud Provider Server (DigitalOcean / AWS / Hetzner Cloud)

For servers provisioned through DigitalOcean, AWS, or Hetzner Cloud:

  1. Go to the server's Settings page
  2. Click Remove Server
  3. Confirm the removal

Appliku will remove the server from your dashboard. Note that this does not automatically destroy the droplet, EC2 instance, or Hetzner Cloud server at the provider. You should also delete the server from the DigitalOcean, AWS, or Hetzner Cloud console to stop incurring charges.

Automatic status detection

For DigitalOcean, AWS, and Hetzner Cloud servers, Appliku regularly checks the server status via the provider's API. If a server is deleted directly at the provider (for example you terminate the EC2 instance from the AWS Console, destroy the droplet from DigitalOcean, or delete the server from the Hetzner Cloud Console), Appliku will automatically detect this and mark the server as deleted in the dashboard.

Removing a Custom Server

For custom servers connected via SSH:

  1. Go to the server's Settings page
  2. Click Remove Server
  3. Confirm the removal

What removal does and does not do

Removing a custom server from Appliku only removes it from Appliku's records. It does not:

  • Stop or remove any applications running on the server
  • Uninstall Docker or Nginx
  • Shut down or delete the server at your hosting provider

Any applications that were deployed to the server will continue running. If you want to fully decommission the server, you need to stop the applications and delete the server at your hosting provider manually.

Removing a Server That Has Databases

A custom server cannot be removed while it still hosts databases. When you try, Appliku shows which databases block the removal and which applications they belong to. Delete each database from its application's Databases page first, then remove the server.

If the server is dead (for example, you already destroyed it at your hosting provider), you can force remove it instead. The removal dialog offers this option after listing the blocking databases. To confirm, type the server's name.

The dialog may also mention database records that are already scheduled for deletion. These are leftovers from earlier database delete attempts that could not be completed. They do not block removal on their own, and both normal and force removal clean them up automatically.

What force removal does

Force removal removes the server from Appliku in one step: the server is marked as deleted, applications are detached from it (application records are kept), and Appliku's records for the databases on it are permanently deleted, including their backup schedule records and the database connection environment variables of linked applications. It never connects to the server.

Nothing on the server itself is touched. If the server is actually still running, its databases, cron entries, and backup scripts keep running unmanaged.

Cluster roles are still protected

Force removal does not bypass cluster role restrictions. A server that is a cluster's primary manager or load balancer cannot be removed, normally or forcefully, while other active servers remain in the cluster. Reassign the role to another server first, or remove the other servers first.

Next Steps