[GH-ISSUE #4155] SSL Unrecognized Name Alert #2694

Open
opened 2026-02-26 07:36:29 +03:00 by kerem · 19 comments
Owner

Originally created by @AmFerra on GitHub (Nov 12, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4155

Checklist

  • Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?

  • Are you sure you're not using someone else's docker image?

    • No
  • Have you searched for similar issues (both open and closed)?

    • Yes

Describe the bug

accessing the website through cloudflare on HTTPS returns an ERR_SSL_UNRECOGNIZED_NAME_ALERT error. I am using the dns challenge

Nginx Proxy Manager Version

2.12.1

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior

to see the default welcome wbepage

Screenshots

image

Operating System

TrueNAS

Additional context

latest truenas version, reinstalled, tried using the custom certificate, using port 8443 because 443 was acting wierd

Originally created by @AmFerra on GitHub (Nov 12, 2024). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4155 <!-- Are you in the right place? - If you are looking for support on how to get your upstream server forwarding, please consider asking the community on Reddit. - If you are writing code changes to contribute and need to ask about the internals of the software, Gitter is the best place to ask. - If you think you found a bug with NPM (not Nginx, or your upstream server or MySql) then you are in the *right place.* --> **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? - Are you sure you're not using someone else's docker image? - No - Have you searched for similar issues (both open and closed)? - Yes **Describe the bug** <!-- A clear and concise description of what the bug is. --> accessing the website through cloudflare on HTTPS returns an ERR_SSL_UNRECOGNIZED_NAME_ALERT error. I am using the dns challenge **Nginx Proxy Manager Version** <!-- What version of Nginx Proxy Manager is reported on the login page? --> 2.12.1 **To Reproduce** Steps to reproduce the behavior: 1. Go to '...' 2. Click on '....' 3. Scroll down to '....' 4. See error **Expected behavior** <!-- A clear and concise description of what you expected to happen. --> to see the default welcome wbepage **Screenshots** <!-- If applicable, add screenshots to help explain your problem. --> ![image](https://github.com/user-attachments/assets/e17ecbc8-4188-4251-a257-1c3d2e6e31cb) **Operating System** <!-- Please specify if using a Rpi, Mac, orchestration tool or any other setups that might affect the reproduction of this error. --> TrueNAS **Additional context** <!-- Add any other context about the problem here, docker version, browser version, logs if applicable to the problem. Too much info is better than too little. --> latest truenas version, reinstalled, tried using the custom certificate, using port 8443 because 443 was acting wierd
Author
Owner

@ruderthanyou commented on GitHub (Nov 13, 2024):

I'm using truenas 24.10.0.2 and NPM 2.12.1. I am also getting the same error when accessing internally from my network. No issues accessing from external, seems to always work.

One more note, from an android device running chrome I always will get ERR_SSL_UNRECOGNIZED_NAME_ALERT error. From Windows using Edge or Chrome I get ERR_QUIC_PROTOCOL_ERROR and if I disable QUIC then I get the SSL_UNREGCONIZED error. And as I mentioned, occasionally I get thru to the host without issue, but it doesn't last very long and breaks again.

Regards

<!-- gh-comment-id:2474290423 --> @ruderthanyou commented on GitHub (Nov 13, 2024): I'm using truenas 24.10.0.2 and NPM 2.12.1. I am also getting the same error when accessing internally from my network. No issues accessing from external, seems to always work. One more note, from an android device running chrome I always will get ERR_SSL_UNRECOGNIZED_NAME_ALERT error. From Windows using Edge or Chrome I get ERR_QUIC_PROTOCOL_ERROR and if I disable QUIC then I get the SSL_UNREGCONIZED error. And as I mentioned, occasionally I get thru to the host without issue, but it doesn't last very long and breaks again. Regards
Author
Owner

@AmFerra commented on GitHub (Nov 13, 2024):

I am accessing it from the external network to get this error, i am using a custom certificate from cloudflare but it seems like that cant be applied to the website, but the DNS challenge ssl doesnt seem to work either

<!-- gh-comment-id:2474773889 --> @AmFerra commented on GitHub (Nov 13, 2024): I am accessing it from the external network to get this error, i am using a custom certificate from cloudflare but it seems like that cant be applied to the website, but the DNS challenge ssl doesnt seem to work either
Author
Owner

@ruderthanyou commented on GitHub (Nov 14, 2024):

I believe I figured out my issue. It seems related to DNS and some cname records that were not configured. Using unifi for DNS and they still don't support creating cname records. Anyway, switching to Adguard Home and creating the proper records seems to have solved my issue. Still testing, but looks good so far.

<!-- gh-comment-id:2476887495 --> @ruderthanyou commented on GitHub (Nov 14, 2024): I believe I figured out my issue. It seems related to DNS and some cname records that were not configured. Using unifi for DNS and they still don't support creating cname records. Anyway, switching to Adguard Home and creating the proper records seems to have solved my issue. Still testing, but looks good so far.
Author
Owner

@Tagnard commented on GitHub (Nov 15, 2024):

+1

<!-- gh-comment-id:2479069544 --> @Tagnard commented on GitHub (Nov 15, 2024): +1
Author
Owner

@AmFerra commented on GitHub (Nov 15, 2024):

it now says ssl handshake failed, I have no idea what I am doing and there is not a lot of documentation that I can find

<!-- gh-comment-id:2479415690 --> @AmFerra commented on GitHub (Nov 15, 2024): it now says ssl handshake failed, I have no idea what I am doing and there is not a lot of documentation that I can find
Author
Owner

@leogout commented on GitHub (Nov 17, 2024):

Hi, just resolved a similar problem two minutes ago. I had created a stream from the port 22 to a local port on my network. Strangely when I deactivated it everything fell into place and I no longer was having the SSL_ERROR_UNRECOGNIZED_NAME_ALERT. If @Ferrarisrex you need more info on my config @ me here and I'll create a ticket to tell the whole story and the steps to reproduce the error. If it is normal behavior feel free to ignore this message. I don't have a good enough understanding of networks to tell the difference...

<!-- gh-comment-id:2481306511 --> @leogout commented on GitHub (Nov 17, 2024): Hi, just resolved a similar problem two minutes ago. I had created a stream from the port 22 to a local port on my network. Strangely when I deactivated it everything fell into place and I no longer was having the SSL_ERROR_UNRECOGNIZED_NAME_ALERT. If @Ferrarisrex you need more info on my config @ me here and I'll create a ticket to tell the whole story and the steps to reproduce the error. If it is normal behavior feel free to ignore this message. I don't have a good enough understanding of networks to tell the difference...
Author
Owner

@jjmmbb commented on GitHub (Nov 22, 2024):

Same issue here... When accessing SSL port direct or using Cloudflare Tunnel, same error.

<!-- gh-comment-id:2493899225 --> @jjmmbb commented on GitHub (Nov 22, 2024): Same issue here... When accessing SSL port direct or using Cloudflare Tunnel, same error.
Author
Owner

@mrin commented on GitHub (Nov 25, 2024):

Same issue

<!-- gh-comment-id:2498065854 --> @mrin commented on GitHub (Nov 25, 2024): Same issue
Author
Owner

@Recentiv commented on GitHub (Dec 5, 2024):

+1

<!-- gh-comment-id:2521108905 --> @Recentiv commented on GitHub (Dec 5, 2024): +1
Author
Owner

@FedeAbella commented on GitHub (Dec 14, 2024):

Same issue here

<!-- gh-comment-id:2542686139 --> @FedeAbella commented on GitHub (Dec 14, 2024): Same issue here
Author
Owner

@umutbesler commented on GitHub (Feb 3, 2025):

Same issue, any fix for this?

<!-- gh-comment-id:2630780227 --> @umutbesler commented on GitHub (Feb 3, 2025): Same issue, any fix for this?
Author
Owner

@doozybytes commented on GitHub (Feb 3, 2025):

Same issue, any fix for this?

For me the issue went away after I rebooted my nginx proxy container.

<!-- gh-comment-id:2630785990 --> @doozybytes commented on GitHub (Feb 3, 2025): > Same issue, any fix for this? For me the issue went away after I rebooted my nginx proxy container.
Author
Owner

@moogfennec commented on GitHub (Mar 7, 2025):

Hi, I have the same problem here. Everything was working fine until it was not.

<!-- gh-comment-id:2707272630 --> @moogfennec commented on GitHub (Mar 7, 2025): Hi, I have the same problem here. Everything was working fine until it was not.
Author
Owner

@mrxehmad commented on GitHub (Mar 8, 2025):

.

I'm using truenas 24.10.0.2 and NPM 2.12.1. I am also getting the same error when accessing internally from my network. No issues accessing from external, seems to always work.

One more note, from an android device running chrome I always will get ERR_SSL_UNRECOGNIZED_NAME_ALERT error. From Windows using Edge or Chrome I get ERR_QUIC_PROTOCOL_ERROR and if I disable QUIC then I get the SSL_UNREGCONIZED error. And as I mentioned, occasionally I get thru to the host without issue, but it doesn't last very long and breaks again.

Regards

hi @ruderthanyou I am also facing this problem, if you got some fix can you let me know what should I do.
i am facing this issue since December last year 💔

<!-- gh-comment-id:2708384593 --> @mrxehmad commented on GitHub (Mar 8, 2025): . > I'm using truenas 24.10.0.2 and NPM 2.12.1. I am also getting the same error when accessing internally from my network. No issues accessing from external, seems to always work. > > One more note, from an android device running chrome I always will get ERR_SSL_UNRECOGNIZED_NAME_ALERT error. From Windows using Edge or Chrome I get ERR_QUIC_PROTOCOL_ERROR and if I disable QUIC then I get the SSL_UNREGCONIZED error. And as I mentioned, occasionally I get thru to the host without issue, but it doesn't last very long and breaks again. > > Regards hi @ruderthanyou I am also facing this problem, if you got some fix can you let me know what should I do. i am facing this issue since December last year 💔
Author
Owner

@gunrunner20 commented on GitHub (May 9, 2025):

Same issue, any fix for this?

For me the issue went away after I rebooted my nginx proxy container.

Same here.
I added another sub domain name to an existing proxied host, while the cert allows per wildcard for all subdomains (just internal setup).
the old entry still worked, the new one didn't.

After a reboot the new subdomain entry and another completely new entry for another host which didn't work before work now.

<!-- gh-comment-id:2867745823 --> @gunrunner20 commented on GitHub (May 9, 2025): > > Same issue, any fix for this? > > For me the issue went away after I rebooted my nginx proxy container. Same here. I added another sub domain name to an existing proxied host, while the cert allows per wildcard for all subdomains (just internal setup). the old entry still worked, the new one didn't. After a reboot the new subdomain entry and another completely new entry for another host which didn't work before work now.
Author
Owner

@TheOverpassArsonist commented on GitHub (Sep 25, 2025):

I'm getting this but I've noticed strangely the error doesn't occur when the computer is connecting to itself, only when something else tries to connect to it. I've tried rebooting the container, wiping it and retrying, etc. several times and nothing has seemed to work. I don't know what changed, (it was working before fine) but this is definitely still an issue and it's hitting my setup hard no matter what I try to do.

Editing to not spam with something that might be unnecessary - Anyone having this problem please react to this post with a party popper IF you are using Zerotier specifically for connections. I can't explain it, but for me the issue was specifically Zerotier and I'm not sure if it was just me having that issue, or if that's actually a significant number of people who are having this issue. If you are currently using zerotier, I'd suggest giving Netbird a look, as it seems to function as-expected. (and is significantly less fussy than Tailscale)

<!-- gh-comment-id:3335205361 --> @TheOverpassArsonist commented on GitHub (Sep 25, 2025): I'm getting this but I've noticed strangely the error doesn't occur when the computer is connecting to itself, only when something else tries to connect to it. I've tried rebooting the container, wiping it and retrying, etc. several times and nothing has seemed to work. I don't know what changed, (it was working before fine) but this is definitely still an issue and it's hitting my setup hard no matter what I try to do. Editing to not spam with something that might be unnecessary - Anyone having this problem please react to this post with a party popper IF you are using Zerotier specifically for connections. I can't explain it, but for me the issue was specifically Zerotier and I'm not sure if it was just me having that issue, or if that's actually a significant number of people who are having this issue. If you are currently using zerotier, I'd suggest giving Netbird a look, as it seems to function as-expected. (and is _significantly_ less fussy than Tailscale)
Author
Owner

@digitaluc342587 commented on GitHub (Sep 29, 2025):

i have the same issue, seems te be intermittend after some time everything works fine once more. only appearse when connecting from a local lan. not when connting from wan.

<!-- gh-comment-id:3346294407 --> @digitaluc342587 commented on GitHub (Sep 29, 2025): i have the same issue, seems te be intermittend after some time everything works fine once more. only appearse when connecting from a local lan. not when connting from wan.
Author
Owner

@Bugi82 commented on GitHub (Nov 5, 2025):

+1

<!-- gh-comment-id:3493106759 --> @Bugi82 commented on GitHub (Nov 5, 2025): +1
Author
Owner

@titiviking commented on GitHub (Feb 19, 2026):

same for me... intermittent (but periods of working are short) so very hard to troubleshoot... nothing seems to fix it

<!-- gh-comment-id:3929942853 --> @titiviking commented on GitHub (Feb 19, 2026): same for me... intermittent (but periods of working are short) so very hard to troubleshoot... nothing seems to fix it
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#2694
No description provided.