hannespr commented on issue #35712:
URL: https://github.com/apache/superset/issues/35712#issuecomment-3912775891
I expierenced the same problem in my Docker Compose dev setup I am running
Superset behind an nginx. The nginx is configured to use a different,
non-standard, port. My nginx configuration looked similar to your updated one.
Superset runs in the app root, `/` - this is a difference to your setup.
My `superset_config.py` has these settings:
```
ENABLE_PROXY_FIX=True
PROXY_FIX_CONFIG={"x_for": 1, "x_proto": 1, "x_host": 1, "x_port": 1,
"x_prefix": 0}
```
After hours of try-and-error I wanted to get more details on what is
actually going and I opened my Chrome Dev Tools which is configured to disable
network caches while being used - and then it worked! Weeks ago, I had an
inappropriate nginx configuration running which did not set the forwarded port
in the header.
So baseline is: Make sure, that the problem is not your browser 🙈. Maybe
this helps some others to save some hours 👍
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
