mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 18:05:54 +03:00
[GH-ISSUE #854] Forwarding login cookie to Calibre Webserver #722
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#722
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jebr on GitHub (Feb 1, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/854
Checklist
Please read the setup instructions
Please read the FAQ
What is troubling you?
I am having problems sending a login cookie trough the proxy manager. I use the calibre-web application and it is automatically logged out after logging in. According to the developer, this has to do with the login cookie not being properly forwarded to the web server. I have performed the suggested actions but they are not having the desired effect. I have already tried ato pass extra values to the proxy manager, but nothing seems to work. When I access the web server locally, I do stay logged in.
Do you have any idea how I can fix this problem?
@petkin700 commented on GitHub (Feb 1, 2021):
Is your cookie set for correct domain which is terminated on npm?
@jebr commented on GitHub (Feb 1, 2021):
Thanks for your quick response. As I can see now it seems that the right domain is associated with the cookie. I have added an image of the data from my browser.
@petkin700 commented on GitHub (Feb 2, 2021):
Hi jebr,
today I bring up the calibre-web from this docker image in my home lab and could not reproduce your issue with authentication when it resides behind npm
@jebr commented on GitHub (Feb 2, 2021):
Thank you very much for testing calibre-web. After your message I checked what kind of traffic is still running between npm and the application.
In the browser I get the following message:
Cookie “remember_token” has been rejected because it is already expired.
I am using Cloudflare (proxy) -> npm -> calibre-web. I have now set the connection to DNS-only in Cloudflare and that seems to solve the problem, I am no longer logged out.
The strange thing is that I use multiple applications behind npm that continue to work when Cloudflare is on proxy. Do you know if I can keep Cloudflare on DNS-only without any problems?

@petkin700 commented on GitHub (Feb 2, 2021):
you could use DNS only, but it's make really a small of sense, because:
tomorrow i'll try to reproduce your setup with my cloudflare account and already deployed calibre-web )))
@petkin700 commented on GitHub (Feb 2, 2021):
ok tomorrow is comes )))
I try to use cloudflare, and also couldn't reproduce your cookie problem, so i think it's cloudflare protection play with you and calibre, try to read cloudflare doc's and may be turn protection level not so hard for begining
@jebr commented on GitHub (Feb 2, 2021):
Thanks for the quick testing. Very strange that this occurs. I will remove the domain from Cloudflare and recreate it, maybe that will help.
@jebr commented on GitHub (Feb 3, 2021):
It was indeed Cloudflare. After deleting the account and waiting for a few hours, I re-added the accounts. Now the page works fine, but after a few minutes and some clicking back and forth I get logged out again. I will contact Cloudflare to find out what is causing this.
The problem is in the Samesite cookies, unfortunately I have no idea what this means, I will read more about it.
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite

@jebr commented on GitHub (Feb 4, 2021):
You can close the issue from me. Unfortunately I am not getting it resolved for calibre-web. It has something to do with the forwarding and storage of cookie data (Samesite = ...). It also has something to do with the way calibre-web handles the login mechanism. This is the only container where I have problems logging in / staying logged in.
I want to thank you very much for your good support!