Open JeremyMahieu opened 1 year ago
The problem boils down to this. The server thinks it's on http, but its really on https via a proxy. And therefore the agent tries to reach the api on http also.
The protocol part of the url in the config isn't being taken into account.
When using the following config, where both the api and the web server are on https, the agent gives 0 output, no errors, nothing. Even when doing
--foreground
and running it as verbose. At most it will sayUsing environment access key.....
Same when running deamon, or execute mode.However when we put the api server on http, it seems to work, it finished experiments from the queue but reports back the wrong URL. For example
ClearML results page: http://example.com/projects/<stuff>/experiments/<stuff>/output/log
, notice this is on http while the web server is on https. So this url is wrong but otherwise it's working.The clearml-server is set up as http, none of the SSL fucntions are used. However a reverse proxy handles SSL. Here is the nginx config. Some nginx config for all 3 subdomains.