-
Hi, i'am trying to deploy Magic to my existing nginx server, On my server port 80 and 443 is already used by Nginx, is there a way to solve this problem? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
You can try to edit the ports, but even if you succeed you'd end up with "funny URLs" where you'd have to use an alternative port to access the thing. However, the It might be you could configure a reverse proxy for the |
Beta Was this translation helpful? Give feedback.
You can try to edit the ports, but even if you succeed you'd end up with "funny URLs" where you'd have to use an alternative port to access the thing. However, the
docker-compose.yml
file also automatically creates a LetsEncrypt SSL certificate for you, which assumes port 80 to verify ownership of the site. Implying even if you succeed editing the port, you'd probably not get SSL working, and even if you get SSL working, you'd end up with "sub-optimal" URLs ...It might be you could configure a reverse proxy for the
Host
name you want to use for Magic, and forward this into an internal port you could expose in thedocker-compose.yml
file. The latter would probably be your best solution, a…