[GH-ISSUE #3844] Everything stops working when I disable main domain/www Proxy Host #2525

Open
opened 2026-02-26 07:35:54 +03:00 by kerem · 2 comments
Owner

Originally created by @Airfirewall on GitHub (Jun 30, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3844

Using Nginx Proxy Manager v2.11.2 and cloudflared 2024.6.1

So I don't use www.example.com much anymore and went to disable it but everything stopped working and shows cloudflared cannot connect to respond to nginx proxy manager.

so if I have this everything works but if I disable example.com www.example.com everything stops working.
example.com www.example.com---Enabled
auth.example.com-------------------Enabled
homepage.example.com------------Enabled
overseerr.example.com--------------Enabled

Why would this stop everything from working? when I re-enable the main domain everything works again.
example.com www.example.com---Disabled
auth.example.com-------------------Enabled
homepage.example.com------------Enabled
overseerr.example.com--------------Enabled

Cloudflare config

ingress:

  • hostname: "*.example.com"
    service: https://10.10.0.10:18443
    originRequest:
    originServerName: "example.com"
  • service: http_status:404\

Cloudflared error

2024-06-30T18:31:31Z ERR error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: remote error: tls: unrecognized name" connIndex=0 event=1 ingressRule=0 originService=https://10.10.0.10:18443
2024-06-30T18:31:31Z ERR Request failed error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: remote error: tls: unrecognized name" connIndex=0 dest=https://overseerr.example.com/login event=0 ip=###.###.###.### type=http

Originally created by @Airfirewall on GitHub (Jun 30, 2024). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3844 Using Nginx Proxy Manager v2.11.2 and cloudflared 2024.6.1 So I don't use www.example.com much anymore and went to disable it but everything stopped working and shows cloudflared cannot connect to respond to nginx proxy manager. so if I have this everything works but if I disable example.com www.example.com everything stops working. example.com www.example.com---Enabled auth.example.com-------------------Enabled homepage.example.com------------Enabled overseerr.example.com--------------Enabled Why would this stop everything from working? when I re-enable the main domain everything works again. example.com www.example.com---Disabled auth.example.com-------------------Enabled homepage.example.com------------Enabled overseerr.example.com--------------Enabled Cloudflare config ingress: - hostname: "*.example.com" service: https://10.10.0.10:18443 originRequest: originServerName: "example.com" - service: http_status:404\ Cloudflared error 2024-06-30T18:31:31Z ERR error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: remote error: tls: unrecognized name" connIndex=0 event=1 ingressRule=0 originService=https://10.10.0.10:18443 2024-06-30T18:31:31Z ERR Request failed error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: remote error: tls: unrecognized name" connIndex=0 dest=https://overseerr.example.com/login event=0 ip=###.###.###.### type=http
Author
Owner

@Airfirewall commented on GitHub (Jul 2, 2024):

added example.com into 404 hosts and left the www.example.com disabled in proxy and everything works. Just confused why removing example.com would cause everything to stop working

<!-- gh-comment-id:2201565692 --> @Airfirewall commented on GitHub (Jul 2, 2024): added example.com into 404 hosts and left the www.example.com disabled in proxy and everything works. Just confused why removing example.com would cause everything to stop working
Author
Owner

@github-actions[bot] commented on GitHub (Feb 16, 2025):

Issue is now considered stale. If you want to keep it open, please comment 👍

<!-- gh-comment-id:2661192000 --> @github-actions[bot] commented on GitHub (Feb 16, 2025): Issue is now considered stale. If you want to keep it open, please comment :+1:
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#2525
No description provided.