Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escaping: Escape characters +-&|!(){}[]^"~*?:\ with \, e.g. \+
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
Answered
Hi, Thank You So Much For Your Awesome Product! But I Have One Issue, Please Tell Me How To Fix It: I Deployed Clearml-Server On A Corporate Virtual Machine. Its Address 10.68.167.10. I Am Able To Send Requests From All Other Virtual Machines On The Serv

Hi,
Thank you so much for your awesome product! But I have one issue, please tell me how to fix it:

I deployed clearml-server on a corporate virtual machine. Its 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. Although, unlike the API server, it is possible to access the web and the file server. How can I forward the API server to listen it from my home computer?

  
  
Posted one year ago
Votes Newest

Answers 6


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

  
  
Posted one year ago

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 🙂

  
  
Posted one year ago

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.

  
  
Posted one year ago

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?

  
  
Posted one year ago

If I manually enter credential keys after specifying the Web server it continues sending a request to port 8008.

  
  
Posted one year ago

The other way around
- "8011:8008"

  
  
Posted one year ago
770 Views
6 Answers
one year ago
one year ago
Tags