Your n8n works from day one on an HTTPS address of its own, like https://37-114-51-188.astrolnodes.app. Whenever you want, you can serve it on your domain, for example n8n.yourcompany.com. The certificate is issued automatically and the initial address then redirects to the new one.
1. Point the domain to your VPS
In your domain's DNS panel (wherever it is registered, or Cloudflare if you use it), create a record:
- Type: A
- Name: the subdomain you want to use, for example
n8n - Value: your VPS IP
If that name already 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. With the proxy on from the start, the certificate may fail to be issued.
2. Check that it points to your VPS
DNS changes can take a while. Log in to your VPS over SSH as root and run, with your domain:
getent ahostsv4 n8n.yourcompany.com
When your VPS IP shows up, move on to step 3.
3. Change the n8n address
Run, with your domain:
astrol-n8n-domain n8n.yourcompany.com
The command checks that the domain points to your VPS (and warns you if it does not yet), keeps a copy of the proxy configuration, changes the n8n address and restarts it. The HTTPS certificate is requested automatically.
4. Check the result
Open https://n8n.yourcompany.com. The certificate is usually ready within a minute or two. The astrolnodes.app address keeps working and redirects to your domain, so the Open n8n button in your panel still takes you there.
What changes when you move to your domain
- Webhook URLs. They now use your domain. Update them in the external services that call them.
- OAuth credentials (Google, Microsoft, Slack…). Their redirect URL includes the n8n address: change it in each provider's console as well and reconnect the credential.
If you see a certificate warning
- Check that the A record points to your VPS IP and that no old AAAA record is left.
- Check that ports 80 and 443 are still open with
ufw status: without port 80 the certificate cannot be validated. - The exact reason shows up in the proxy log:
cd /opt/n8n && docker compose logs --tail 60 caddy
Getting tangled up with the records? Open a ticket with your domain and your VPS IP and we will give you the exact values. You manage the domain and its DNS; if you registered the domain with us, we will tell you where its DNS settings are in your client area.
Related
- What your application's astrolnodes.app address is
- Getting started with your n8n VPS
- Common n8n issues
Order: n8n VPS in Frankfurt · in Miami
Was this article helpful?
Need more help?
Open a ticket and the support team goes through it with you.