thomasrea0113 commented on issue #32187: URL: https://github.com/apache/superset/issues/32187#issuecomment-3381493222
> Seems there are two different problems: > > * people using the wrong port (we should find a way to make it more clear that we moved to 9000) > * people for whom 9000 doesn't work (personally cannot reproduce this, maybe docker setting/version related?) I think the docs could overall use a lot more clarity regarding which port to use and how to debug the frontend in general. In the past (on 4.1) we used port 80 with Nginx without much issue. After upgrading to 5.0, we ran into the issue mentioned here. Nginx didn't work at all, even AFTER the fix in https://github.com/apache/superset/pull/32362 was implemented. The proxy still failed because the superset-node container did not define the "host.docker.internal:host-gateway" host. Ultimately, I got it to load with port 9000 after adding the host, but port 80 still doesn't work with the following changes to the compose file: 1. add the host.docker.internal:host-gateway host to the node service 2. change the superset env for the node service to nginx superset: "http://host.docker.internal:80"; 3. bind port 9000 to all interfaces with these changes, I did confirm that the nginx container can communicate with the node container, but after logging in the loading screen just spins. What port am I expected to use with the default configuration, and how can I set it up to use nginx like before? it's also worth noting that breakpoints in the frontend have never worked consistently, even after upgrading to 5.0.0. If I open dev tools and set a breakpoint in the browser, the breakpoint will hit in my vscode instance, opening the correct file. But setting breakings in vscode directly does not work consistently. -- 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]
