Can’t log in to n8n

Questions
1

Describe the problem/error/question

Can’t log in to n8n

What is the error message (if any)?

When I click sign in I get “Cannot GET /signin”

Please share your workflow

(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

Hi @randons Welcome!
Have you tried using this https://app.n8n.cloud/magic-link ?

3

Hi @randons

The error “Cannot GET /signin” is essentially a “Page Not Found” message. It means your n8n server is running and responding, but it doesn’t recognize the specific web address you are trying to reach. Instead of showing you the login screen, the server is telling you that the “signin” page doesn’t exist at that exact location.

One of the most common causes is a “path” mismatch. If you configured n8n to run on a subpath (for example, yourdomain.com/n8n/), the login page is no longer at the root /signin address. In this case, you simply need to make sure you are typing the full address, including that subpath (e.g., yourdomain.com/n8n/signin), otherwise the server won’t know where to send you.

Another likely culprit is your “reverse proxy”—the software (like Nginx or Traefik) that acts as a gatekeeper between the internet and your n8n instance. Sometimes the proxy is configured incorrectly and “strips” part of the web address before it reaches n8n, or it blocks the specific type of connection (WebSockets) that n8n needs to load its interface. This makes the server think you are asking for a page that isn’t there.

It could also be a technical glitch with the app’s internal files. n8n is a modern web app that relies on JavaScript files to build the page in your browser. If these files are missing, corrupted, or blocked by a browser extension, the app can’t load the login screen properly. This often happens after a messy update or if the N8N_PATH variable was accidentally left blank.

To fix this, the best first step is to “bypass the middleman.” Try accessing n8n directly using your server’s IP address and port (like http://123.456.78.9:5678). If the login page works there, you know the problem is with your reverse proxy settings. If it still doesn’t work, the issue is likely with your n8n configuration variables or a corrupted installation that needs a fresh update.

4

hi @randons welcome to the n8n community.
Could you help us by sharing a bit more about your situation?