Changed domain name of n8n hostinger VPS and now I cannot access n8n?

Questions
1

Describe the problem/error/question

Recently purchased n8n vps and a domain name from Hostinger. I followed the steps as defined in their guide to change the domain for n8n exactly. the file was updated with my domain name but when I click on ‘Mange App’ button then it still takes me to old domain name (which was provided as a default).

Do I need to change the “Hostname’ under VPS details section on overview screen of VPS?

Even when I try to manually enter the url with my domain name I get an error message.

What is the error message (if any)?

clicking on ‘Manage App’ still takes me to following address -

https://n8n.srv1071485.hstgr.cloud

which displays ‘404 page not found’ error message

instead of

https://n8n.manuchawla.cloud

Please share your workflow

  1. pointed my VPS to the domain (confirmed that DNS propagation is complete)
    1. created two ‘A’ record entries under DNS/Nameserver section with VPS IP address as per the suggested steps and removed all other ‘A’ ‘AAAA’ & ‘CNAME’ records.
    2. NOTE: I do see some CAA & MX records under DNS/Nameserver section which I have not removed yet.
  2. accessed my VPS through browser terminal
  3. ran the command ‘nano .env’
  4. In the DOMAIN_NAME=srvXXXXX.hstgr.cloud replaced it with following -DOMAIN_NAME=manuchawla.cloud
  5. click ctrl+x then y then ‘enter’
  6. restarted n8n service by executing following commands -
    1. docker compose down
    2. docker compose up -d
(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
2

Steps to Check and Resolve Domain Routing

  • Ensure your n8n configuration file (often .env or similar) is updated to reflect your new domain name under the proper environment variable, such as WEBHOOK_URL, VUE_APP_URL, or DOMAIN_NAME depending on deployment type.

  • Verify that your VPS’s DNS settings and Hostinger domain panel have an A record pointing your domain to your VPS public IP address.

  • Check whether you have set up a reverse proxy (Nginx, Apache, etc.) on your VPS, and update the server block (vhost) configuration to point to your new domain and redirect accordingly.

  • The “Hostname” field in Hostinger’s VPS settings is for system identification and does not directly affect n8n’s app URLs or routing.

  • If you manually visit your new domain and get an error, check whether n8n is running and listening on the correct port, and ensure firewall rules allow inbound traffic on that port.

Additional Troubleshooting Tips

  • Restart n8n and your web server (if using a reverse proxy) after making config changes to apply them.

  • Clear browser cache and DNS cache if you recently updated DNS records.

  • Test direct access to n8n via your VPS IP and port to confirm the service is running.