But in credentials creation it still shows 8008. Are there any other places in docker-compose.yml where port from 8008 to 8011 should be replaced?
I think there is a way to "tell" it what to out there, not sure:
https://clear.ml/docs/latest/docs/deploying_clearml/clearml_server_config#configuration-files
If I manually enter credential keys after specifying the Web server it continues sending a request to port 8008.
Nice, curl http:/10.68.167.10:8011 now works. But in credentials creation it still shows 8008. Are there any other places in docker-compose.yml where port from 8008 to 8011 should be replaced?
Hi MinuteGiraffe30
Thank you so much for your awesome product!
😍 !
s address 10.68.167.10. I am able to send requests from all other virtual machines on the server to the address 10.68.167.10:8008. However, when I try to do this from my own computer connected to the corporate network via VPN, it fails to connect to 8008.
I'm assuming there is a firewall on the VPN connection itself (i.e. the VPN gateway) that blocks 8008 port, as you already tried curl to 8008 is being blocked before getting to the server, I'm sure your IT/DevOps can fix that 🙂
Is it possible to change the port for API server? I tried replacing ports in apiserver section in docker-compose.yml.ports: - "8008:8011"But it didn't help. Now curl http:/10.68.167.10:8011 does not work from the host machine.