You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey, where you able to solve this issue? I'm facing the same and didn't realize how to use https-portal for several containers, even using reverse-proxy it's failing.
Can we add more containers in the same host, something like modifying the ports (9443 instead of 443, 9080 instead of 80)
No. Let's Encrypt (where we get the HTTPS certificate from demands the port to be 80 and 443).
But you can use two different domains, both listening on 80 and 443. For example:
Nice, I tried to run an isolated https-portal per docker-compose file, now I've deployed a separated container only for ssl + reverse proxy for all my apps and worked pefectly. I guess it was the expected way to use but wasn't very clear for me.
@SteveLTN
Can we add more containers in the same host, something like modifying the ports (9443 instead of 443, 9080 instead of 80)
Like below:
Default Container:
Additional Container:
is this ok, or we will face any issues in the future while updating the certs, etc?
The text was updated successfully, but these errors were encountered: