NginxProxyManager / NginxProxyManager/nginx-proxy-manager

After updating from 2.12.6 to 2.13.4 → “SSL handshake failed” (had to restore backup to get back online)

Open
#4,947 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Hello,
I want to report an issue after updating Nginx Proxy Manager from version 2.12.6 to 2.13.4.

Right after the update, all my proxy hosts behind Cloudflare started returning:

SSL handshake failed

Additionally, the SSL Certificates page inside NPM turned completely white, and custom certificates were no longer processed correctly.

To get my system back online, I had to restore a full backup of version 2.12.6, where everything immediately started working again.

It seems there is a problem with SSL handling in version 2.13.x.

ps:

/data/custom_ssl/npm-3/

fullchain.pem
privkey.pem

Thank you.

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

Start with the custom certificate files at /data/custom_ssl/npm-3/fullchain.pem and /data/custom_ssl/npm-3/privkey.pem, then compare SSL handling between versions 2.12.6 and 2.13.4. Check the SSL Certificates page and a Cloudflare proxy host after updating; done means the page renders, custom certificates process correctly, and proxy hosts no longer return “SSL handshake failed”.

Written by the indexing model from the issue text.

Assessment

Tech stack
nginx
Domain
backend, frontend, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.