How to config SSL? about clearml-server

[bmartinn]

Hi @GeoffreyChen777
As you can see in the installation instruction here, just under the diagram:
trains-server supports two types of configurations:

    Single IP (domain) with the following open ports
        Web application on port 8080
        API service on port 8008
        File storage service on port 8081

    Sub-Domain configuration with default http/s ports (80 or 443)
        Web application on sub-domain: app.*.*
        API service on sub-domain: api.*.*
        File storage service on sub-domain: files.*.*

This means you have to setup the Nginx to forward the following subdomains (yes, only these subdomains are supported):

  app.*.* -> http://<trains_server_ip>:8080
  api.*.* -> http://<trains_server_ip>:8008
  files.*.* -> http://<trains_server_ip>:8081

[GeoffreyChen777]

@bmartinn Hi, thanks for your reply.

I tried to set my Nginx with the configuration:

server {
    listen 80;

    server_name app.mydomain.com;

    location / {
        proxy_pass       http://127.0.0.1:8080;
        proxy_set_header Host      $host;
        proxy_set_header X-Real-IP $remote_addr;
    }
}


server {
    listen 80;

    server_name api.mydomain.com;

    location / {
        proxy_pass       http://127.0.0.1:8008;
        proxy_set_header Host      $host;
        proxy_set_header X-Real-IP $remote_addr;
    }
}

server {
    listen 80;

    server_name files.mydomain.com;

    location / {
        proxy_pass       http://127.0.0.1:8081;
        proxy_set_header Host      $host;
        proxy_set_header X-Real-IP $remote_addr;
    }
}

Can not solve it.

Do I need to add three A record (api, app, files) to my domain's DNS console?

[bmartinn]

@GeoffreyChen777 regrading the DNS entry:
First make sure you get the correct IP with :
ping app.mydomain.com
(If you do not, then yes you need to configure the DNS records of your domain)

BTW:
I would recommend using:
app.trains.mydomain.com , api.trains.mydomain.com , files.trains.mydomain.com ,

[GeoffreyChen777]

@bmartinn

Now I have added app.trains.mydomain.com , api.trains.mydomain.com , files.trains.mydomain.com to my DNS console. When I ping app.trains.mydomain.com, I can get the correct IP.

I also set my nginx to forward the subdomian to the corresponding port. When I open https://api.trains.mydomain.com, I can get:

{"meta":{"id":"7c828bb4526846f29018f44ffaccb4b7","trx":"7c828bb4526846f29018f44ffaccb4b7","endpoint":{"name":"","requested_version":1.0,"actual_version":null},"result_code":400,"result_subcode":0,"result_msg":"Invalid request path /","error_stack":null},"data":{}}

I think it means that I can access apiserver(port 8008) through api.trains.mydomain.com.

I think, now, I need to change some configuration files of trains-server.
Because I found that the trains-server still tries to access port 8008:

[bmartinn]

The Web App will access the API server based on the address it is served from:
i.e. If browsing to http://localhost:8080 it will look for the Api server at https://localhost:8008
and if browsing to http://app.trains.mydomain.com it will look for http://api.trains.mydomain.com

Try clearing cookies, restarting the browser and opening http://app.trains.mydomain.com

[GeoffreyChen777]

After I refresh my cookies cache, everything works fine now!

Thanks for you help! @bmartinn

Have a nice day!