Halloween

Up to 35% off servers Up to 35% off Starts in --d --:--:--

Menu
Free trial

Try it free for 24 hours

We keep two servers open, one in Germany and one in Miami. Join from Java or Bedrock, on whatever version you run, and see how they perform before paying for anything.

If after the trial you decide it's not for you, you pay nothing. If you keep it, billing starts the next day at the regular price.

Use your own domain with Hermes Agent

Serve the Hermes Agent panel on a domain of your own with HTTPS: A record, proxy change and the new address in the panel configuration.

53 views Updated 17 Oct 2026

The Hermes panel works from day one on an HTTPS address of its own, like https://37-114-51-188.astrolnodes.app. If you prefer your domain, for example hermes.yourcompany.com, it takes three steps. Channels (Telegram, Discord, WhatsApp…) do not depend on the domain and keep working as before.

1. Point the domain to your VPS

In your domain's DNS panel, create an A record with the subdomain you want (for example hermes) and your VPS IP as the value. If that name had an AAAA record that does not point to your VPS, delete it.

Important: if you use Cloudflare, keep the record as DNS only (grey cloud) at least until the certificate has been issued.

Check from your VPS that it already points there (its IP should show up):

getent ahostsv4 hermes.yourcompany.com

2. Change the name in the proxy

As root, edit /etc/caddy/Caddyfile (for example with nano /etc/caddy/Caddyfile), replace 37-114-51-188.astrolnodes.app with your domain, save and reload:

caddy validate --config /etc/caddy/Caddyfile
systemctl reload caddy

The HTTPS certificate for your domain is requested automatically.

3. Give the panel the new address

Edit /home/hermes/.hermes/.env, change the HERMES_DASHBOARD_PUBLIC_URL= line to HERMES_DASHBOARD_PUBLIC_URL=https://hermes.yourcompany.com and restart the panel:

su - hermes -c 'systemctl --user restart hermes-dashboard'

Open https://hermes.yourcompany.com and sign in with your username and password.

If you see a certificate warning

  • Check the A record and that no old AAAA record is left.
  • Check that ports 80 and 443 are still open with ufw status.
  • The exact reason shows up with journalctl -u caddy --no-pager -n 60.

Getting tangled up with the records? Open a ticket with your domain and your VPS IP and we will give you the exact values.

Order: Hermes Agent VPS in Frankfurt · in Miami

Was this article helpful?

Need more help?

Open a ticket and the support team goes through it with you.

Open a ticket