webserver docker is running nginx, you can mount other setting into the docker, like ssl certificates, and an 443 definition.
or you can start your own nginx and point the reverse proxy to the webserver docker exposed port.
if the reverse proxy uses a location other then root (like /clearml ), you will need more setting to get the UI to work form that path
Fine, but i got certificate only for *.domain.tld, not for *.sub.domain.tld 😕 is there possibility to run it for example on clearml.domain.tld? I know there is multiple containers with ports, so if it is possible, could you add example nginx config to wiki? (I didn't find it.)
similar to the suggested layout here
None
Hi, you mean not from the root path of the server?
I mean in general, to use port 80 (for redirect) and 443.
clearml docker doesn't setup a SSL, you will have to do that in your own nginx configuration probably for each server section that expose clearml services as a subdomain. see:
None
Hi Luaks,
clearml serve the system for paying customers using AWS services and not through Nginx. so I don't have an example config to give you.
maybe this answer on SE can help you map the exposed ports of webapp, API and fileserver to app.domain.tld api.domain.tld and files.domain.tld
None