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 Everyone, I Have A Strange Situation Regarding Hosting Clearml On A Public Ip. I Think I Have Configured Everything Well. From My Home Office, Or On A Random Vpn Pc I Can Access The Server Perfectly Fine. However, When I'M At Work (So Connected To Work

Hi everyone, I have a strange situation regarding hosting ClearML on a public IP. I think I have configured everything well.
From my home office, or on a random VPN pc I can access the server perfectly fine. However, when I'm at work (so connected to work wifi network) and at an hpc facility I am getting this:
Retrying after connection broken by 'ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7f8cab5dbb80>, 'Connection to public/ip/address timed out. (connect timeout=3.0)')': /auth.login .

I cannot figure out whether the problem is on the server or on the corporate networks. The networking people are telling me there shouldn't be a port blocking happening or something. Can someone shed some lights on how the authentication protocol is handled and what I can do to circumvent this authentication issue?

I also tried assigning a different port than 8001 to the server, but that seems troublesome. I don't think that's possible easily, is it?

Any help would be greatly appreciated!

  
  
Posted 2 months ago
Votes Newest

Answers 2


Hi @<1577468611524562944:profile|MagnificentBear85> , assuming all the server components are up and running (i.e. if you're using docker-compose, for example, all docker containers should be running and reporting logs), the server will never produce this kind of output - this is almost always a result of some network connectivity issue

  
  
Posted 2 months ago

Ok, thanks, I'll ask the networking people to dig into this.

  
  
Posted 2 months ago
175 Views
2 Answers
2 months ago
2 months ago
Tags
Similar posts