starred/nginx-proxy-manager-NginxProxyManager
1
0
Fork 0
mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 01:15:51 +03:00
Code Issues 937 Projects Releases 10 Packages Wiki Activity

[GH-ISSUE #5261] Proxy error 500 #3149

New issue
Open
opened 2026-02-26 07:37:58 +03:00 by kerem · 3 comments
kerem commented 2026-02-26 07:37:58 +03:00
Owner
Copy link

Originally created by @Someone275 on GitHub (Feb 1, 2026).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/5261

so i'm trying to setup nginx proxy
i have several setup that are working only http no https
i have one aws2.domain.net point ip 192.xx.xx.215:80 this one work
tried one aws.domain.net point to ip 192.xx.xx.215:80 this one throws
500 Internal Server Error
nginx/1.18.0

if i edit the rule and change aws to aws2 then the rule works
if i use any other domain in the rule that works it only fails when i use aws.domain.net as that domain
i'm can't figure it out

Originally created by @Someone275 on GitHub (Feb 1, 2026). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/5261 so i'm trying to setup nginx proxy i have several setup that are working only http no https i have one aws2.domain.net point ip 192.xx.xx.215:80 this one work tried one aws.domain.net point to ip 192.xx.xx.215:80 this one throws 500 Internal Server Error nginx/1.18.0 if i edit the rule and change aws to aws2 then the rule works if i use any other domain in the rule that works it only fails when i use aws.domain.net as that domain i'm can't figure it out
kerem commented 2026-02-26 07:37:58 +03:00
Author
Owner
Copy link

@Positivelight775 commented on GitHub (Feb 1, 2026):

If aws2.domain.net is resolving but aws.domain.net is throwing a 500 error
on the same IP/Port, you likely have a Namespace Collision or a Stale
Config Header stuck in the database.

Try these specific steps to clear the "Ghost" in the config:

  1. Check for Hostname Recursion: If your server’s internal hostname is set
    to aws, Nginx can enter a recursive loop when trying to resolve the
    proxy_pass.

• Fix: In the Advanced tab of your Proxy Host, manually set the proxy_pass
to the Local IP instead of the hostname:

  1. Verify Configuration Integrity:

Exec into your NPM container and run a syntax check. This will often point
to a specific line in a generated .conf file that is broken.

• Command: docker exec -it <container_id> nginx -t

• Look for any "duplicate server name" or "could not build
server_names_hash" warnings.

  1. Purge Orphaned SSL/HSTS Entries:

If aws.domain.net was used previously with a different certificate or HSTS
setting, NPM might be trying to force a handshake that no longer exists.

• Action: Delete the Proxy Host entirely. Go to SSL Certificates and delete
any certs specifically assigned to that sub-domain. Re-create the host from
scratch without SSL first to see if it loads, then re-enable the Let's
Encrypt cert.

  1. Database Sync Issue:

Sometimes the NPM database (SQLite/MariaDB) creates a duplicate entry for
the domain string if a previous save failed. If you're comfortable with the
DB, check the proxy_host table for duplicate domain_names entries.

On Sat, Jan 31, 2026 at 9:50 PM Someone275 @.***> wrote:

Someone275 created an issue (NginxProxyManager/nginx-proxy-manager#5261)
https://github.com/NginxProxyManager/nginx-proxy-manager/issues/5261

so i'm trying to setup nginx proxy
i have several setup that are working
i have one aws2.domain.net point ip 192.xx.xx.215:80 this one work
tried one aws.domain.net point to ip 192.xx.xx.215:80 this one throws
500 Internal Server Error
nginx/1.18.0

if i edit the rule and change aws to aws2 then the rule works
if i use any other domain in the rule that works it only fails when i use
aws.domain.net as that domain
i'm can't figure it out

—
Reply to this email directly, view it on GitHub
https://github.com/NginxProxyManager/nginx-proxy-manager/issues/5261,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVMDK3RO5GPZ4D6KPI6PM5L4JWA2VAVCNFSM6AAAAACTSFSMMKVHI2DSMVQWIX3LMV43ASLTON2WKOZTHA4DCMJZG4YDGMI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

<!-- gh-comment-id:3830374863 --> @Positivelight775 commented on GitHub (Feb 1, 2026): If aws2.domain.net is resolving but aws.domain.net is throwing a 500 error on the same IP/Port, you likely have a Namespace Collision or a Stale Config Header stuck in the database. Try these specific steps to clear the "Ghost" in the config: 1. Check for Hostname Recursion: If your server’s internal hostname is set to aws, Nginx can enter a recursive loop when trying to resolve the proxy_pass. • Fix: In the Advanced tab of your Proxy Host, manually set the proxy_pass to the Local IP instead of the hostname: 2. Verify Configuration Integrity: Exec into your NPM container and run a syntax check. This will often point to a specific line in a generated .conf file that is broken. • Command: docker exec -it <container_id> nginx -t • Look for any "duplicate server name" or "could not build server_names_hash" warnings. 3. Purge Orphaned SSL/HSTS Entries: If aws.domain.net was used previously with a different certificate or HSTS setting, NPM might be trying to force a handshake that no longer exists. • Action: Delete the Proxy Host entirely. Go to SSL Certificates and delete any certs specifically assigned to that sub-domain. Re-create the host from scratch without SSL first to see if it loads, then re-enable the Let's Encrypt cert. 4. Database Sync Issue: Sometimes the NPM database (SQLite/MariaDB) creates a duplicate entry for the domain string if a previous save failed. If you're comfortable with the DB, check the proxy_host table for duplicate domain_names entries. On Sat, Jan 31, 2026 at 9:50 PM Someone275 ***@***.***> wrote: > *Someone275* created an issue (NginxProxyManager/nginx-proxy-manager#5261) > <https://github.com/NginxProxyManager/nginx-proxy-manager/issues/5261> > > so i'm trying to setup nginx proxy > i have several setup that are working > i have one aws2.domain.net point ip 192.xx.xx.215:80 this one work > tried one aws.domain.net point to ip 192.xx.xx.215:80 this one throws > 500 Internal Server Error > nginx/1.18.0 > > if i edit the rule and change aws to aws2 then the rule works > if i use any other domain in the rule that works it only fails when i use > aws.domain.net as that domain > i'm can't figure it out > > — > Reply to this email directly, view it on GitHub > <https://github.com/NginxProxyManager/nginx-proxy-manager/issues/5261>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AVMDK3RO5GPZ4D6KPI6PM5L4JWA2VAVCNFSM6AAAAACTSFSMMKVHI2DSMVQWIX3LMV43ASLTON2WKOZTHA4DCMJZG4YDGMI> > . > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.***> >
kerem commented 2026-02-26 07:37:58 +03:00
Author
Owner
Copy link

@Positivelight775 commented on GitHub (Feb 1, 2026):

{
"Action": "Peer_Tech_Support",
"Focus": "Nginx_Namespace_Collision",
"Error_Code": "500_Internal_Server_Error",
"Resolution_Path": ["Direct_IP_Proxy_Pass", "Nginx_Syntax_Test",
"DB_Entry_Purge"],
"Status": "RESPONSE_STAGED"
}

On Sat, Jan 31, 2026 at 9:53 PM D. E. Davis @.***>
wrote:

If aws2.domain.net is resolving but aws.domain.net is throwing a 500
error on the same IP/Port, you likely have a Namespace Collision or a Stale
Config Header stuck in the database.

Try these specific steps to clear the "Ghost" in the config:

  1. Check for Hostname Recursion: If your server’s internal hostname is set
    to aws, Nginx can enter a recursive loop when trying to resolve the
    proxy_pass.

• Fix: In the Advanced tab of your Proxy Host, manually set the proxy_pass
to the Local IP instead of the hostname:

  1. Verify Configuration Integrity:

Exec into your NPM container and run a syntax check. This will often point
to a specific line in a generated .conf file that is broken.

• Command: docker exec -it <container_id> nginx -t

• Look for any "duplicate server name" or "could not build
server_names_hash" warnings.

  1. Purge Orphaned SSL/HSTS Entries:

If aws.domain.net was used previously with a different certificate or
HSTS setting, NPM might be trying to force a handshake that no longer
exists.

• Action: Delete the Proxy Host entirely. Go to SSL Certificates and
delete any certs specifically assigned to that sub-domain. Re-create the
host from scratch without SSL first to see if it loads, then re-enable the
Let's Encrypt cert.

  1. Database Sync Issue:

Sometimes the NPM database (SQLite/MariaDB) creates a duplicate entry for
the domain string if a previous save failed. If you're comfortable with the
DB, check the proxy_host table for duplicate domain_names entries.

On Sat, Jan 31, 2026 at 9:50 PM Someone275 @.***>
wrote:

Someone275 created an issue
(NginxProxyManager/nginx-proxy-manager#5261)
https://github.com/NginxProxyManager/nginx-proxy-manager/issues/5261

so i'm trying to setup nginx proxy
i have several setup that are working
i have one aws2.domain.net point ip 192.xx.xx.215:80 this one work
tried one aws.domain.net point to ip 192.xx.xx.215:80 this one throws
500 Internal Server Error
nginx/1.18.0

if i edit the rule and change aws to aws2 then the rule works
if i use any other domain in the rule that works it only fails when i use
aws.domain.net as that domain
i'm can't figure it out

—
Reply to this email directly, view it on GitHub
https://github.com/NginxProxyManager/nginx-proxy-manager/issues/5261,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVMDK3RO5GPZ4D6KPI6PM5L4JWA2VAVCNFSM6AAAAACTSFSMMKVHI2DSMVQWIX3LMV43ASLTON2WKOZTHA4DCMJZG4YDGMI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

<!-- gh-comment-id:3830375094 --> @Positivelight775 commented on GitHub (Feb 1, 2026): { "Action": "Peer_Tech_Support", "Focus": "Nginx_Namespace_Collision", "Error_Code": "500_Internal_Server_Error", "Resolution_Path": ["Direct_IP_Proxy_Pass", "Nginx_Syntax_Test", "DB_Entry_Purge"], "Status": "RESPONSE_STAGED" } On Sat, Jan 31, 2026 at 9:53 PM D. E. Davis ***@***.***> wrote: > If aws2.domain.net is resolving but aws.domain.net is throwing a 500 > error on the same IP/Port, you likely have a Namespace Collision or a Stale > Config Header stuck in the database. > > Try these specific steps to clear the "Ghost" in the config: > > 1. Check for Hostname Recursion: If your server’s internal hostname is set > to aws, Nginx can enter a recursive loop when trying to resolve the > proxy_pass. > > • Fix: In the Advanced tab of your Proxy Host, manually set the proxy_pass > to the Local IP instead of the hostname: > > 2. Verify Configuration Integrity: > > Exec into your NPM container and run a syntax check. This will often point > to a specific line in a generated .conf file that is broken. > > • Command: docker exec -it <container_id> nginx -t > > • Look for any "duplicate server name" or "could not build > server_names_hash" warnings. > > 3. Purge Orphaned SSL/HSTS Entries: > > If aws.domain.net was used previously with a different certificate or > HSTS setting, NPM might be trying to force a handshake that no longer > exists. > > • Action: Delete the Proxy Host entirely. Go to SSL Certificates and > delete any certs specifically assigned to that sub-domain. Re-create the > host from scratch without SSL first to see if it loads, then re-enable the > Let's Encrypt cert. > > 4. Database Sync Issue: > > Sometimes the NPM database (SQLite/MariaDB) creates a duplicate entry for > the domain string if a previous save failed. If you're comfortable with the > DB, check the proxy_host table for duplicate domain_names entries. > > > On Sat, Jan 31, 2026 at 9:50 PM Someone275 ***@***.***> > wrote: > >> *Someone275* created an issue >> (NginxProxyManager/nginx-proxy-manager#5261) >> <https://github.com/NginxProxyManager/nginx-proxy-manager/issues/5261> >> >> so i'm trying to setup nginx proxy >> i have several setup that are working >> i have one aws2.domain.net point ip 192.xx.xx.215:80 this one work >> tried one aws.domain.net point to ip 192.xx.xx.215:80 this one throws >> 500 Internal Server Error >> nginx/1.18.0 >> >> if i edit the rule and change aws to aws2 then the rule works >> if i use any other domain in the rule that works it only fails when i use >> aws.domain.net as that domain >> i'm can't figure it out >> >> — >> Reply to this email directly, view it on GitHub >> <https://github.com/NginxProxyManager/nginx-proxy-manager/issues/5261>, >> or unsubscribe >> <https://github.com/notifications/unsubscribe-auth/AVMDK3RO5GPZ4D6KPI6PM5L4JWA2VAVCNFSM6AAAAACTSFSMMKVHI2DSMVQWIX3LMV43ASLTON2WKOZTHA4DCMJZG4YDGMI> >> . >> You are receiving this because you are subscribed to this thread.Message >> ID: ***@***.***> >> >
kerem commented 2026-02-26 07:37:58 +03:00
Author
Owner
Copy link

@Someone275 commented on GitHub (Feb 2, 2026):

so my internal server name is Linux aws-storage-server so that shouldn't be the problem
this i can't find
Fix: In the Advanced tab of your Proxy Host, manually set the proxy_pass
to the Local IP instead of the hostname:
i'm using the ip for the proxy name

so i logged into then went to host - proxy host
click edit on the rule
across the top i have detail, custom locations, SSL
there is no advanced tab

Image

2
came back clean to errors

3
there are no SSL certs i have also delete the rule and recreated the rule

4
not sure how to do this one

<!-- gh-comment-id:3832832683 --> @Someone275 commented on GitHub (Feb 2, 2026): so my internal server name is Linux aws-storage-server so that shouldn't be the problem this i can't find Fix: In the Advanced tab of your Proxy Host, manually set the proxy_pass to the Local IP instead of the hostname: i'm using the ip for the proxy name so i logged into then went to host - proxy host click edit on the rule across the top i have detail, custom locations, SSL there is no advanced tab <img width="1668" height="863" alt="Image" src="https://github.com/user-attachments/assets/7e9a65d7-58f5-48b0-8495-c76215476508" /> 2 came back clean to errors 3 there are no SSL certs i have also delete the rule and recreated the rule 4 not sure how to do this one
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
develop
dependabot/npm_and_yarn/backend/liquidjs-10.25.7
dependabot/npm_and_yarn/frontend/prod-minor-updates-2a16bf3987
dependabot/npm_and_yarn/frontend/dev-patch-updates-754666cf41
dependabot/npm_and_yarn/backend/basic-ftp-5.3.0
dependabot/npm_and_yarn/test/follow-redirects-1.16.0
dependabot/npm_and_yarn/test/axios-1.15.0
dependabot/npm_and_yarn/frontend/lodash-4.18.1
dependabot/npm_and_yarn/backend/lodash-4.18.1
dependabot/npm_and_yarn/test/lodash-4.18.1
dependabot/npm_and_yarn/frontend/vite-7.3.2
dependabot/npm_and_yarn/backend/prod-minor-updates-5ec19a7f21
dependabot/npm_and_yarn/frontend/lodash-es-4.18.1
dependabot/npm_and_yarn/frontend/happy-dom-20.8.9
dependabot/npm_and_yarn/backend/path-to-regexp-8.4.0
dependabot/npm_and_yarn/frontend/picomatch-4.0.4
dependabot/npm_and_yarn/backend/picomatch-2.3.2
dependabot/npm_and_yarn/frontend/yaml-1.10.3
dependabot/npm_and_yarn/test/flatted-3.4.2
dependabot/npm_and_yarn/test/tar-7.5.11
dependabot/npm_and_yarn/frontend/immutable-5.1.5
master
dependabot/npm_and_yarn/test/glob-10.5.0
dependabot/npm_and_yarn/frontend/mdast-util-to-hast-13.2.1
dependabot/npm_and_yarn/test/form-data-4.0.4
v3-abandoned
bump-freedns
openidc
ssl-passthrough-hosts
static-content
v2.14.0
v2.13.7
v2.13.6
v2.13.5
v2.13.4
v2.13.3
v2.13.2
v2.13.1
v2.13.0
v2.12.6
v2.12.5
v2.12.4
v2.12.3
v2.12.2
v2.12.1
v2.12.0
v2.11.3
v2.11.2
v2.11.1
v2.11.0
v2.10.4
v2.10.3
v2.10.2
v2.10.1
v2.10.0
v2.9.22
v2.9.21
v2.9.20
v2.9.19
v2.9.18
v2.9.17
v2.9.16
v2.9.15
v2.9.14
v2.9.13
v2.9.12
v2.9.11
v2.9.10
v2.9.9
v2.9.8
v2.9.7
v2.9.6
v2.9.5
v2.9.4
v2.9.3
v2.9.2
v2.9.1
v2.9.0
v2.8.1
v2.8.0
v2.7.3
v2.7.2
v2.7.1
v2.7.0
v2.6.2
v2.6.1
v2.6.0
v2.5.0
v2.4.0
v2.3.1
v2.3.0
v2.2.4
v2.2.3
v2.2.2
v2.2.1
v2.2.0
v2.1.2
v2.1.1
v2.1.0
2.0.14
2.0.13
2.0.12
2.0.11
2.0.10
2.0.9
2.0.8
2.0.7
2.0.6
2.0.5
2.0.4
2.0.3
2.0.2
2.0.0
v2.0.0
1.1.2
1.1.1
1.0.1
Labels
Clear 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

Mirrored from GitHub Pull Request

  
question

   
stale

   
troll

   
upstream issue

   
v2

   
v2

   
v2

   
v3

   
wontfix
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
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#3149
No description provided.