404 Error on n8n Page with Fresh Docker Installation on Ubuntu 20.04

Below is some guidance to troubleshoot your 404 error:

---

Check the Domain/Subdomain Configuration

If you set up n8n using Docker (with Docker Compose or a similar setup), make sure you’re accessing the URL that matches your configuration. For example, if your .env defines:

DOMAIN_NAME=example.com
SUBDOMAIN=n8n

then your URL should be:
  https://n8n.example.com

If you access the wrong domain (or IP address directly), the reverse-proxy rules might not match, which would result in a 404 error.

---

Verify Reverse Proxy Settings

If you’re using a reverse proxy (e.g., Traefik in the Docker Compose setup), check that:

• The labels for the n8n service correctly reference your domain/subdomain.
• The reverse proxy is running and is properly configured to route https requests to the n8n container (it must be mapping the correct ports like 80/443).

For example, in the provided Docker Compose configuration, the n8n service has labels such as:

YAMLCopied
labels:
  - traefik.enable=true
  - traefik.http.routers.n8n.rule=Host(`${SUBDOMAIN}.${DOMAIN_NAME}`)
  - traefik.http.routers.n8n.tls=true

Make sure the environment variables SUBDOMAIN and DOMAIN_NAME have your correct values.

---

Checking n8n Logs

To view n8n logs:

• If using Docker Compose, run:

  BASHCopied
  sudo docker compose logs n8n

• If using plain Docker, find the container name or ID using:

  BASHCopied
  sudo docker ps

  Then view the logs with:

  BASHCopied
  sudo docker logs <container_name_or_id>

Logs should help identify if n8n is encountering any startup errors or if the request isn’t reaching the container as expected.

---

Summary

The 404 error is most likely the result of one of the following:

• Accessing the wrong URL (not matching your configured subdomain and domain).
• A misconfigured reverse proxy that isn’t forwarding requests to the n8n container.
• Container or environment variable misconfiguration.

By checking your domain configuration and proxy settings and then reviewing the container logs, you should be able to narrow down the source of the issue.

Happy troubleshooting, and let me know if you need more assistance!