mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #17] Checking authentication... #18
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#18
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 @Aerya on GitHub (Sep 11, 2018).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/17
Hi,
Don't really know if it's about this (awesome) proxy or on the other side but trying to use it with Cardigann (and Nginx auth) I got this error:
Checking authentication...Cardigann source: https://hub.docker.com/r/linuxserver/cardigann/
Nginx-proxy-manager: https://i.imgur.com/nRCh4ZX.png
Nginx auth (working with my others containers):
auth_basic "Restricted Content";auth_basic_user_file /data/htpasswd/cardigann;@jc21 commented on GitHub (Sep 11, 2018):
Just to clarify, are you using an Access List in NPM for this Proxy Host, or are your putting those
auth_basiclines in the Advanced config for the Proxy Host? Or as part of Cardigan itself?@Aerya commented on GitHub (Sep 11, 2018):
I use the advanced config on the proxy host. It works well for all containers (Wordpress, Jackett, Medusa...) but have this error for Cardigann. That's why I wonder if its on "your" side or Cardiganns.
@jc21 commented on GitHub (Sep 11, 2018):
I highly doubt it's NPM's side. I run other services that have built in basic auth behind NPM without issue as well. In some cases I also disable auth for the service and only use NPM for auth.
The best way to test is to hit Cardigan directly and see if auth is still failing
@Aerya commented on GitHub (Sep 11, 2018):
Thanks, I'm discovering Cardigann, I'll look for its own auth process.
@Aerya commented on GitHub (Sep 23, 2018):
Cardigann is a totally f*cked tool. Not on your side. Thanks for support anyway.