CloudFlare Authentication and Error 403 when running n8n workflows

Questions
1

So typically I use my internal IP address when working on n8n workflows, my webhooks use my external domain and run fine.

I access n8n externally via CloudFlare Zero Trust, so i visit the external domain, authenticate myself with Cloudflare 2FA and i get access to my n8n instance, this all works fine. I have caching disabled, and can log out and log in on n8n without any errors, but when i try to execute a flow i get the following error message.

Which i read it ask, your are not authenticated (error 403)

image
image469×170 8.71 KB

So i check the logs

image
image1633×355 30.8 KB

however i am logged in, even after signing out and clearing the cache and logging back in again, in the GUI it shows me as signed in.

image
image357×178 3.26 KB

I can use the API playground using the external domain fine, also
domain.com/api/v1/docs/#/Workflow/get_workflows

It hasn’t done this before, any ideas?

2

Hey @RedPacketSec, I am afraid I can’t reproduce this locally or on one of the n8n instances I am running.

You might want to check your webserver access logs (assuming you are running a reverse proxy) with your Cloudflare service enabled vs with the service disabled to check how exactly they manipulate the requests and get an idea of what might need to be changed.

3

If i start a new flow its fine, its only when i open an existing flow and try to execute it.

there are no error logs on the cloudflare side that i can see

4

Hey, i have the same setup. Wondering if you were able to find a solution. I am having trouble getting access to webhooks because of cloudflares zero trust sing in screen. Is there away to let webhook requests bypass this?

5

yeah you can set an exception/bypass for specific URLs etc

6

My workaround is to use email based ‘authentication’ for Zero Trust. Once I’ve logged in, I can run webhooks with no problems. Might not be the most secure system in the world, but I’m not guarding nuclear launch codes … yet.