-
-
Notifications
You must be signed in to change notification settings - Fork 2k
Updated Part-DB and get Invalid CSRF token #7443
-
Hello,
I updated my Part-DB container and now I'm getting the error message "Invalid CSRF token" when trying to log in. I don't get this message when I log in locally on the network. Only when I log in via my domain using Cloudflare and Pihole. But is that possibly the cause, and what do I need to configure where? Thank you.
Beta Was this translation helpful? Give feedback.
All reactions
Replies: 3 comments 7 replies
-
Maybe Default_uri add into .env?
Beta Was this translation helpful? Give feedback.
All reactions
-
Beta Was this translation helpful? Give feedback.
All reactions
-
Oh yeah, sorry, I missed that. Unfortunately, it didn't work. But I did notice that when I enter my URL there, the " at the end isn't white.
part-01
Beta Was this translation helpful? Give feedback.
All reactions
-
Remove the comments below, maybe a " is missing above
And you need to restart the Container after Change
Beta Was this translation helpful? Give feedback.
All reactions
-
No, unfortunately, it only works locally. As I said, I use Cloudflare and Nginx Proxy Manager, and since updating Part-DB, I've been getting an error message when I try to connect via Cloudflare.
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 1
-
Then maybe ask in there repo? I dont use NPM (annoying Tool), only Caddy with Cloudflare and all my LXC working fine. Idk what NPM do :/
Beta Was this translation helpful? Give feedback.
All reactions
-
not sure if you fixed it, for me it was the TRUSTED_PROXIES=127.0.0.0/8,::1,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16 that was missing.
now it works :)
Beta Was this translation helpful? Give feedback.
All reactions
-
🎉 1
-
If your Nginx Proxy Manager is also a docker container TRUSTED_PROXIES=172.16.0.0/12 should be enough to do the trick without finding the exact IP address of the docker container.
Beta Was this translation helpful? Give feedback.
All reactions
-
I'm also running into the same issue with cloudflare. I tried to set CORS_ALLOW_ORIGIN but that also didn't fix this.
Beta Was this translation helpful? Give feedback.