NginxProxyManager / NginxProxyManager/nginx-proxy-manager

Server shows offline when assigned a cert, online without it.

Open
#4,352 19 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

bug stale
Dominant language
TypeScript
Stars
34.2k
Forks
3.9k
Avg merge
21h 12m
Merged PRs (30d)
20

Description

Checklist

  • Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
    • Yes
  • Are you sure you're not using someone else's docker image?
    • Yes
  • Have you searched for similar issues (both open and closed)?
    • Yes

Describe the bug

I have 34 Proxy Hosts, 33 of them work correctly, the 1 that does not is Authentik. It works properly as long as I do not assign it a Cert in NPM. If I assign it a Cert, the server shows as offline. To reiterate, when there is no cert assigned I can click on the link in NPM, type in the FQDN in the browser, or the IP:Port and it will load Authentik without a cert. However, if I assign it a cert, then the system shows offline, if I click on the link in NPM or use the FQDN in the browser I get the server isn't responding error. If I type in the IP:Port, then I get to Authentik. And to again, the other 33 that work all have certs assigned and work fine.

Nginx Proxy Manager Version

v2.12.3

To Reproduce
Steps to reproduce the behavior:

  1. Add Proxy Host
  2. Put IP and Port for Authentic
  3. Create the Host and see server is online
  4. Edit the Host and add a Cert
  5. Save Host and see the server is offline
  6. Edit the Host and remove the Cert
  7. Confirm the server is back online.

Expected behavior

A server being online or offline should not be determined by if a cert is assigned to it. I am guessing there is some error happening in the background and instead of giving an error it's marking offline.

Screenshots

Image

Image

Image

Operating System

Unraid

Additional context

Unraid 7.0.0
All browsers
Latest NPM, Latest Authentik

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the reported behavior with the v2.12.3 Docker image by following the Proxy Host and certificate steps, using Authentik as the upstream service. Compare the host status and access behavior with and without the certificate, then verify that assigning a certificate no longer causes the host to report offline or prevents access through its FQDN.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, nginx, typescript
Domain
backend, infrastructure, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.