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

[leardinet]

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.

[NekoSuneVR]

to follow up this to clearify yes i having this issue too after i updated it on docker i faceing a lot error 500, 514 and ssl handshake errors with using cloudflare even lets encypt did same on cloudflare way so something they broken SSL on latest so had to roll back myself get my ssl back online after multi tempt finding issue myself.

atleast im not only one having this issue with SSL

i need follow up update so i know im safe update on docker if this fixed fully.

[leardinet]

Thanks for the reply, so you had to failback too. Maybe a bug? But did you finally fix it?

[NekoSuneVR]

for update i got mine fixed 2.13.5

they released 2.13.5 and to get it work is have to update docker partly. because when i was on old version docker and docker compose it was keep crashing because it requires latest client api that docker deployed

so recomended update 2.13.5 and keep midn im not dev this program just im trobbleshooting person because i was having this error before then i was confused wasnt working but since i updated to 2.13.5 and updaed my docker it fixed issue my end. and all SSL workign again.

so to codernates if using older version docker on latest NPM it crashes alot in background so recomended update all your docker images after updating docker. because lot changes happent on docker fixes.

[leardinet]

Hi, I want to report my experience regarding the issue I previously had with “SSL handshake failed” and broken SSL management after updating Nginx Proxy Manager inside an LXC container on Proxmox.

After several tests, the root cause is now clear:

The problem comes from the Proxmox community script used to install NPM inside an LXC (community-scripts/nginxproxymanager.sh).

This script applies patches to the frontend and custom modifications that are not compatible with the latest versions of Nginx Proxy Manager (2.13.x).

As a result:

the GUI becomes partially broken

the SSL certificates page turns white

custom certificates stop working

the frontend fails to load correctly

“SSL handshake failed” appears on all hosts

I tested the same configuration with a clean, official installation using Docker (outside of the Proxmox script), and everything works correctly:

Docker installation is clean

NPM starts without frontend issues

SSL certificates work

I was able to restore my old /data directory

All proxy hosts work immediately

No more “SSL handshake failed”

Conclusion:

The issue is not related to Nginx Proxy Manager itself, but to the Proxmox community script installation. A clean Docker-based installation works perfectly, even after restoring old data.

Hope this helps others who may run into the same issue.

Thanks.

[NekoSuneVR]

sadly mine wouldnt work because contabo VPs uses proxmox server and no way unlift it less i got my 2nd pc build that goign take months and months do and for ssl i give up with it and using cloudflare tunnel for now till if is going be fix