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
<no title>

None

  
  
Posted 8 months ago
Votes Newest

Answers 8


I shouldn't have to, just trying to be as verbose as possible so it works. I don't think the proxy is at fault because it works over the same proxy but http instead of https, and it works with the same proxy for the web endpoint, just not for the api endpoint.

  
  
Posted 8 months 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.

  
  
Posted 8 months ago

The server is set up as http, but I reverse proxy it as https.

  
  
Posted 8 months ago

Why do you need to specify the 443 port?

  
  
Posted 8 months ago

See here on how a user did that in the past: None

  
  
Posted 8 months ago

@<1547028017774071808:profile|LazyGoat32> , the agent can only communicate using HTTPS with the server is the server was set up with SSL termination (i.e. supporting HTTPS).
HTTPS support is not part of the basic server set up and can be added on top of it (see the documentation here , as well as several threads on this both here and in the clearml-server github issues).

  
  
Posted 8 months ago

The server is basically oblivious to https - any reverse proxy implementing SSL termination should handle HTTPS and forward the decoded requests to the server upstream using HTTP - if your reverse proxy doesn't do that, than you're effectively no doing SSL termination but simply forwarding whatever you get to the server, and the server won't handle HTTPS

  
  
Posted 8 months ago

So probably there's something wrong with the proxy?

  
  
Posted 8 months ago
357 Views
8 Answers
8 months ago
8 months ago
Tags
Similar posts