starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 17:35:52 +03:00

[GH-ISSUE #2591] 2 CORS / Access-Control-Allow-Origin headers headers #1804

New issue

Closed

opened 2026-02-26 07:32:31 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 07:32:31 +03:00

Owner

Originally created by @lorana94 on GitHub (Feb 5, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2591

Hi there!

I'm using NPM on a docker server and have a proxy to route my Home Assistant to an SSL host with NPM. However the strange thing is that I'm getting 2 Access-Control-Allow-Origin headers headers, one is coming from Home Assistant, and the other one is - I think - from NPM.

When I look a the NGINX config I don't see anything that suggests that the Access-Control-Allow-Origin headers has been added / set.

NMP host info:

OFF: Cache Assets
ON: Block Common Exploits
ON: Websockets Support
Access List: Publicly
Custom locations: none
SSL: on
SSL: ON - Force SSL
SSL: OFF - HTTP/2 Support
SSL: OFF - HSTS Enabled
SSL: OFF - HSTS Subdomains
Advanced: none

Chrome screenshot: https://www.loom.com/i/202960379d964cabbe12f5dede81b3c2
NGINX config (auto generated by NPM): https://pastebin.com/3VWdJ29k

Anyone an idea?

Originally created by @lorana94 on GitHub (Feb 5, 2023). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2591 Hi there! I'm using NPM on a docker server and have a proxy to route my Home Assistant to an SSL host with NPM. However the strange thing is that I'm getting 2 Access-Control-Allow-Origin headers headers, one is coming from Home Assistant, and the other one is - I think - from NPM. When I look a the NGINX config I don't see anything that suggests that the Access-Control-Allow-Origin headers has been added / set. NMP host info: - OFF: Cache Assets - ON: Block Common Exploits - ON: Websockets Support - Access List: Publicly - Custom locations: none - SSL: on - SSL: ON - Force SSL - SSL: OFF - HTTP/2 Support - SSL: OFF - HSTS Enabled - SSL: OFF - HSTS Subdomains - Advanced: none Chrome screenshot: https://www.loom.com/i/202960379d964cabbe12f5dede81b3c2 NGINX config (auto generated by NPM): https://pastebin.com/3VWdJ29k Anyone an idea?

kerem

2026-02-26 07:32:31 +03:00

closed this issue
added the
stale
label

kerem commented

2026-02-26 07:32:32 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jan 28, 2024):

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

@github-actions[bot] commented on GitHub (Jan 28, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 07:32:32 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 14, 2025):

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (Mar 14, 2025): Issue was closed due to inactivity.

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#1804

No description provided.

Rows
Columns