Infinite Redirect Loop with Nginx Proxy Manager When Using bin/setup Domain

[boeCD]

Hi,

I’m running Magento inside a container and using Nginx Proxy Manager (NPM) as a reverse proxy. Here’s what I’ve observed:

• Setup

  • Internal testing domain with a local DNS record (similar to editing /etc/hosts) works fine — no redirect issues.

  • When using bin/setup sub.domain.de, NPM is configured with the container’s IP (http, port 80) as the proxy target.

• Problem

  • Accessing the site through NPM with the configured domain leads to an infinite redirect loop (“too many redirects”).

  • Browser shows 301 loops regardless of SSL or browser cache.

  • Example log line from container:

10.0.2.10 - - [17/Sep/2025:08:43:05 +0000] "GET / HTTP/1.1" 301 169 "http://10.0.2.10:81/" ...

• Suspicion

  • It looks like NPM terminates HTTPS and forwards plain HTTP to Magento, but Magento (or its Nginx config) enforces HTTPS again. This creates a loop.

  • Using the internal testing domain bypasses this, which is why it only occurs with the real domain configured via bin/setup.

• Request
  Could you clarify the recommended setup when using NPM (or another reverse proxy in front of Magento)? Should SSL termination happen entirely at NPM, or inside the container as well?
  Any guidance on how to avoid this redirect loop would be appreciated.

Thanks!

[dosubot]

Hi @boeCD! I'm Dosu and I’m helping the docker-magento team.

The redirect loop happens because the Nginx config inside the Magento container always redirects HTTP (port 8000) to HTTPS (port 8443), and Magento itself expects HTTPS for all URLs after running bin/setup and bin/setup-domain (source). If Nginx Proxy Manager terminates SSL and forwards plain HTTP to the container, both Nginx and Magento will keep trying to enforce HTTPS, causing the loop.

The recommended setup is to have Nginx Proxy Manager forward HTTPS traffic directly to the container's HTTPS port (8443), not HTTP (8000). This way, both the proxy and the container agree the connection is secure, and you avoid the redirect loop (source). You do not need to terminate SSL inside the container and at NPM—just forward HTTPS all the way through.

If you need to terminate SSL at NPM and forward HTTP, you would have to customize the container's Nginx config to respect proxy headers like X-Forwarded-Proto, but by default, this is not supported in the docker-magento setup.

TL;DR: Forward HTTPS from NPM to the container's HTTPS port (8443) to avoid the redirect loop.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[boeCD]

This results in Error 502

[Yestrs]

Hi.
I have same problem while using NPM (Nginx Proxy Manager) and this magento docker setup.

Then in NPM it throws this error
2025/11/26 14:41:06 [error] 899#899: *9036 upstream sent too big header while reading response header from upstream, client: 162.158.48.229, server: sub.domain.com, request: "GET / HTTP/2.0", upstream: "https://172.19.0.2:8443/", host: "sub.domain.com", referrer: "https://sub.domain.com/"

I tried this, but have same outcome as @boeCD.

Hi @boeCD! I'm Dosu and I’m helping the docker-magento team.

The redirect loop happens because the Nginx config inside the Magento container always redirects HTTP (port 8000) to HTTPS (port 8443), and Magento itself expects HTTPS for all URLs after running bin/setup and bin/setup-domain (source). If Nginx Proxy Manager terminates SSL and forwards plain HTTP to the container, both Nginx and Magento will keep trying to enforce HTTPS, causing the loop.

The recommended setup is to have Nginx Proxy Manager forward HTTPS traffic directly to the container's HTTPS port (8443), not HTTP (8000). This way, both the proxy and the container agree the connection is secure, and you avoid the redirect loop (source). You do not need to terminate SSL inside the container and at NPM—just forward HTTPS all the way through.

If you need to terminate SSL at NPM and forward HTTP, you would have to customize the container's Nginx config to respect proxy headers like X-Forwarded-Proto, but by default, this is not supported in the docker-magento setup.

TL;DR: Forward HTTPS from NPM to the container's HTTPS port (8443) to avoid the redirect loop.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other