makeplane
[bug]: Not able to docker compose without nginx (docker-compose.hub.yml)
Is there an existing issue for this?
- [X] I have searched the existing issues
Current behavior
When I use docker-compose.hub.yml and comment out nginx (because I have one running), the correct port is missing for the frontend.
I will use my reverse proxy specifically to connect to plane by means of a sub-domain, port 443 (SSH). So in the setup.sh, as an argument, it doesn't make sense to state a port - or should it be 443, then?
Also, I cannot reach it with the internal docker host IP - again, the port info is missing in order to set the right port mapping in docker-compose.hub.yml.
Otherwise, if I runs setup.sh <sub-domain.my-domain.tld>, I cannot reach the frontend because I don't know on which port it listens.
Steps to reproduce
Install via docker-compose.hub.yml with nginx service commented out. Run docker-compose -f docker-compose.hub.yml and try to reach via internal ip.
Browser
Google Chrome
Version
Self-hosted
Hi @schnillerman
My recommendation is you configure your port as 443 for the nginx in .env file.
This is the .env file that you can specify what you would want to do with your configuration for the docker-compose files.
Give it a try !
Hello @schnillerman! We've made some improvements to the docker configuration. To avoid any interference with system ports, we decided to remove the ports for backend (8000) and frontend (3000) as they are common. As a result, we have optimized the port configuration for better performance. We understand the importance of keeping our users informed, so we'll be updating the documentation to provide clear instructions on how to configure the ports. Thank you for your understanding and patience!
@pablohashescobar I'm at the same point. Can you guide us, if it has been updated how to setup this?
Hi, if you already have a reverse proxy running you may have to forward the / to the plane frontend that runs on port 3000 and anything to /api to plane backend which runs on port 8000.
Closing this issue due to inactivity. Please be aware that we have upgraded our self-hosting setup, and the process should now be smooth. For additional information, read our documentation at https://docs.plane.so/self-hosting/.
