You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have an instance of ClearML running on a GCP VM within an VPC network.
This server is accessed in two ways:
Through internet on the adresse (my-clearml.com), which is bound to the external IP of the server. The ingress on this is strictly controlled and only allows a few IPs
Through the local VPC, where its accssed through its internal IP - 10.0.0.11.11. All ingress within the VPC is allowed.
The main source of logging to the ClearML server is Vertex AI through the VPC. Since custom containers running on GCP dont have a static IP, they do their logging using the internal IP of the ClearML server (10.0.11.11:8080)
My problem is as follows:
When we access the server through the public adresse, my-clearml.com, the URL of the "Debug Samples" image are using the internal IP (or more precise, they are using the URL which the client who did the loggig had configured).
So even though the ClearML server is accssesed from my-clearml.com it will give the image url http://10.0.11.11:8081/"project path"/image.jpg to the client, which cannot be accessed from outside.
Do you have any idea on how to fix this? Ideally it would be possible to set the ClearML host somewhere and that would be used in the client.
The text was updated successfully, but these errors were encountered:
Hi @andwaal-esmart, since the server's URL is used when registering debug images, this is indeed an issue.
You might want to try out the path substitution settings which allow you to substitute a prefix of a URL when uploading data from a client - this would be set on the clients accessing the server using IP, and should basically replace the IP in the registered URL with the externally visible domain name
Hi,
I have an instance of ClearML running on a GCP VM within an VPC network.
This server is accessed in two ways:
The main source of logging to the ClearML server is Vertex AI through the VPC. Since custom containers running on GCP dont have a static IP, they do their logging using the internal IP of the ClearML server (10.0.11.11:8080)
My problem is as follows:
So even though the ClearML server is accssesed from my-clearml.com it will give the image url http://10.0.11.11:8081/"project path"/image.jpg to the client, which cannot be accessed from outside.
Do you have any idea on how to fix this? Ideally it would be possible to set the ClearML host somewhere and that would be used in the client.
The text was updated successfully, but these errors were encountered: