I find your comment very unfair, as two different users did try to help you and answered your initial topic.
There appears to be a bug in the docs. I opened a PR to address this: fix: don't refer to obsolete proxy config in docs by regisb · Pull Request #462 · overhangio/tutor · GitHub
It’s only now that I’ve had time to take a look at this, and yes, there seems to be a problem in the MFE plugin when running behind a web proxy. Basically, the MFE web server is not available from the host. There are two ways to address this:
- We proxy the MFE web server with nginx, as you do with your custom plugin. In the general case, this means that a request follows this rather long path: Caddy (from the caddy container)
Nginx Caddy (from the MFE container). - When
RUN_CADDY=falsewe expose the MFE service on the host (on port 8002). In such a case the user needs to manually configure the nginx/apache proxy to point to localhost:8002.
I’m not sure what’s the best approach here, but this use case needs to be addressed. Any opinion @developers @experts?
EDIT: I created an issue to keep track of this bug The MFE apps are unavailable when Tutor runs behind a web proxy (`RUN_CADDY=false`) · Issue #6 · overhangio/tutor-mfe · GitHub