Proxy error 500

[Someone275]

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

[Positivelight775]

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) <#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 <#5261>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVMDK3RO5GPZ4D6KPI6PM5L4JWA2VAVCNFSM6AAAAACTSFSMMKVHI2DSMVQWIX3LMV43ASLTON2WKOZTHA4DCMJZG4YDGMI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Positivelight775]

{ "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) > <#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 > <#5261>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AVMDK3RO5GPZ4D6KPI6PM5L4JWA2VAVCNFSM6AAAAACTSFSMMKVHI2DSMVQWIX3LMV43ASLTON2WKOZTHA4DCMJZG4YDGMI> > . > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.***> >

[Someone275]

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

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