N8n suddenly unable to log in

Questions
1

Describe the problem/error/question

I discovered that the workflow I had deployed wasn’t producing results at the scheduled time, so I wanted to log in to see what went wrong. After entering my username and password and clicking login, a notification appeared in the bottom right corner:
Problem logging in
Request failed with status code 403
I tried restarting docker compose but it didn’t help.

image

What is the error message (if any)?

Please share your 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

Hey @t4568, while you wait for a response, here are some things that might help:

Suggested resources

Automatically matched to your question.

Docs:

Forum:

@Parintele_Damaskin, @A_A4, @Serkan_Sahin - you’ve helped with similar issues before, can you take a look?

Automatically suggested by n8n’s community bot. It’s a pilot - please share feedback here.

3

@t4568

Since you self host, is your credential correct?

4

Hey @t4568 Welcome to the n8n community!
Can you share your n8n version and the response body for the failed login request? Open your browser’s developer tools, select Network, try logging in again, then click the request returning 403 and copy its Response. Please also share the n8n Docker logs from that attempt if possible

5

Hi @t4568 Welcome!

Open your browser’s Developer Tools > Network, try logging in once, then select the request returning 403 and open Response. Can you paste that response body? That will help tell whether n8n or a proxy is rejecting the login. Share only the response, not the request payload or cookies.

Since your scheduled workflows also stopped producing results, run docker compose logs --tail=100 from your Compose folder and share the relevant n8n errors along with your n8n version. Remove secrets and personal details before posting.

6

@t4568

Are you using CloudFlare or behind any firewall?
This may apply

Your 403 error is likely a Cloudflare Access policy blocking your login credentials. First, check the Security Events log to see the specific block reason, then either adjust your access policy or temporarily bypass Cloudflare Access while troubleshooting.

7

@kjooleng It is indeed behind the firewall. I’ll go ask my colleagues to see if there have been any recent changes. Thank you for the guidance.

8

@Anshul_Namdev

Did you say the following? Sorry, I’m not very familiar with this area

<!doctype html>
 <meta charset="utf-8">
 <meta name=viewport content="width=device-width, initial-scale=1">
 <title>403</title> 
403 Forbidden
9

What about the docker logs?

10

Final check confirmed it was blocked by Google Cloud Armor

11

ah, that’s annoying. a 403 on login usually means something in front of n8n is blocking the request, not the password. are you behind a reverse proxy or cloudflare, and what does the n8n container log show when you hit login?