mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #2414] Cloudflare Proxy shows Let'sencrypt Certificate instead of Cloudflare Inc ECC on second domain #1695
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#1695
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 @Faniac on GitHub (Nov 20, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2414
I'm using NPM v2.9.18 on my Unraid Server with two domains. Both domains are proxied over Cloudflare. For some reasons it shows "Cloudflare Inc ECC CA-3" as certificate, but on the second domain there is only the "E1 - LetsEncrypt" certificate. Is that a known error? The proxy works fine, if i ping the website i'll get a answer from Cloudflare servers. I tried to reset my API aswel reinstall NPM but nothing really works.
@the1ts commented on GitHub (Nov 21, 2022):
Have you checked DNS locally and on the internet? Seems like you are hitting NPM directly for your second domain.
Perhaps check from external with something like
ssllabsthis will show if its working as you think in cloudflare and its something on your network that is not going through cloudflare (e.g. host file entry, local dns being different)@github-actions[bot] commented on GitHub (Feb 4, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Mar 21, 2025):
Issue was closed due to inactivity.