Use your own domain with OpenClaw

The OpenClaw 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 agent.yourcompany.com, it takes three steps. Telegram, WhatsApp and the other channels do not depend on the domain: they 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 agent) and your VPS IP as the value. If that name had an AAAA record that does not point to your VPS, delete it.

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

getent ahostsv4 agent.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 OpenClaw the new address

As the openclaw user, with your domain:

su - openclaw
openclaw gateway stop
openclaw config set gateway.publicOrigin https://agent.yourcompany.com
openclaw config set gateway.controlUi.allowedOrigins '["https://agent.yourcompany.com"]' --strict-json
openclaw gateway start

Open https://agent.yourcompany.com and sign in with your token. You may need to approve the browser again with openclaw-admin devices approve, as the first time.

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.

Related

• What your application's astrolnodes.app address is
• Getting started with your OpenClaw VPS
• Common OpenClaw issues

Order: OpenClaw VPS in Frankfurt · in Miami