Can I access n8n through a custom domain?

Introduction

After installing n8n on your Virtual Private Server (VPS), you may want to access it using a custom domain instead of your server’s IP address. Using a custom domain not only makes your automation dashboard easier to access but also improves security, professionalism, and branding.

In this article, you’ll learn how to access n8n through a custom domain, why it’s beneficial, and how to configure your domain for a secure VPS setup. For reliable VPS hosting to run n8n smoothly, check out BigCloudy plans.

Why Use a Custom Domain for n8n?

Accessing n8n at a URL like automation.yourdomain.com is far better than using a raw IP address. It enhances the user experience and provides strong security advantages.

Benefits of Using a Custom Domain

• Professional Access: Looks polished and credible for businesses and teams.
• Easier Management: Simple to remember and convenient for frequent access.
• Improved Security: Enables HTTPS using SSL certificates.
• Custom Branding: Aligns your automation platform with your brand identity.

Requirements Before Setting Up a Custom Domain

1. Running n8n Instance

You should have n8n already installed and running on your VPS — via Node.js, PM2, or Docker.

2. Registered Domain Name

You’ll need an active domain from a registrar like Namecheap, GoDaddy, or Google Domains.

3. DNS Access

You must be able to edit your domain’s DNS settings to point the domain to your VPS IP address.

Step 1: Point Your Domain to the VPS

To connect your custom domain to your VPS, create a new A record in your DNS settings.

Create an A Record:

• Type: A
• Host: automation
• Value: your_vps_ip
• TTL: Automatic or 3600

Example:
If your domain is example.com and your VPS IP is 192.168.1.100, then:

automation.example.com → 192.168.1.100

DNS propagation typically completes within minutes but may take up to 24 hours.

Step 2: Install and Configure a Reverse Proxy (NGINX)

To access n8n using your custom domain and secure it with HTTPS, you’ll need a reverse proxy like NGINX.

Install NGINX

sudo apt install nginx -y

Create a New NGINX Configuration File

sudo nano /etc/nginx/sites-available/n8n.conf

Add the configuration:

server {

    listen 80;

    server_name automation.example.com;

    location / {

        proxy_pass http://localhost:5678/;

        proxy_set_header Host $host;

        proxy_set_header X-Real-IP $remote_addr;

        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

        proxy_set_header X-Forwarded-Proto $scheme;

    }

}

Enable the configuration:

sudo ln -s /etc/nginx/sites-available/n8n.conf /etc/nginx/sites-enabled/

sudo nginx -t

sudo systemctl restart nginx

Visit http://automation.example.com to verify your dashboard loads.

Step 3: Secure n8n with HTTPS (SSL Certificate)

To protect your login and workflow data, enable HTTPS using Let’s Encrypt.

Install Certbot

sudo apt install certbot python3-certbot-nginx -y

Generate and Apply SSL Certificate

sudo certbot --nginx -d automation.example.com

Certbot will automatically verify your domain, configure HTTPS, and set up auto-renewal.

Visit your secure n8n domain: https://automation.example.com

Step 4: Enable Basic Authentication (Optional)

If Running n8n Directly

export N8N_BASIC_AUTH_ACTIVE=true

export N8N_BASIC_AUTH_USER=admin

export N8N_BASIC_AUTH_PASSWORD=securepassword

If Using Docker

Add the following environment variables in your Docker Compose:

environment:

  – N8N_BASIC_AUTH_ACTIVE=true

  – N8N_BASIC_AUTH_USER=admin

  – N8N_BASIC_AUTH_PASSWORD=securepassword

Restart n8n to apply changes.

Step 5: Test and Verify

Visit:

https://automation.example.com

You should see your secure n8n dashboard. If authentication is enabled, you’ll be prompted to log in.

Troubleshooting Tips

1. DNS Not Resolving? Use dnschecker.org to verify propagation.
2. NGINX Issues? Check configuration with sudo nginx -t.
3. Firewall Blocking? Ensure ports 80 and 443 are open:

sudo ufw allow 80

sudo ufw allow 443

1. SSL Issues? Test certificate renewal:

sudo certbot renew --dry-run