can you open devtools (F12) and look for the events.debug_images response in the network tab?
I'm looking for the url of the image coming from the api server
Yes, in fact, if I take the urls of the files that the webserver provides me and I replace the localhost part with that ip I can clearly view the underlying data from my browser
Both the web app and server versions are 2.0.0-613, api is instead 2.31
I only used the env variables I mentioned (I also checked inside the docker-compose.yaml and noticed that only CLEARML_HOST_IP hasn’t a default value, so I tried to set only that env variable, but the result didn’t change). I haven’t any other configuration other than apiserver.conf in /opt/clearml/config with the users. I definitely haven’t seen any configuration.json file for now. Ps: the docker-compose.yaml is just the one inside the repo, without any change to it.
HollowKangaroo53 which version of clearml server are you using?
I set this in the webserver section of the docker-compose, but it didn’t helped (the double quotes are because a problem in the parsing of the arguments , it has been already reported on GitHub where a read about this fix):
environment: WEBSERVER__fileBaseUrl: '"http://192.168.1.83:8081"' WEBSERVER__useFilesProxy: 'true'
can you maybe add a screenshot where things are broken, so I'm sure we are on the same page?
does this solve your issue, or the API server can't be reached as well?
where exactly the webserver provides you with the URL with localhost in it
I noticed th e problem in the preview section of the dataset files: they cannot be shown because they point to localhost, but, if I click on “open image” and then replace localhost with the server ip everything works as expected
it might be an issue with the way clearml.conf is setup
I just checked and indeed the clearml.conf file that of the user that I used to upload the dataset has indeed set the various servers host as localhost (since for this testing that user was on the same machine as the server). Is this an expected behavior ? I would have thought that such a config only influences the the connection between the cli/ask of the user and the server, but once the data is uploaded it’s duty of the server to provide the right url for whoever is accessing the data
I see as this can be a problem at least when someone wants to migrate the machine on a new domain/ip. In any case, a warning in the documentation would be useful, as the default deploy shown is for localhost, but would brake as soon as someone tries to access those data from the local network instead
Using the webserver ? In the pc where I’m accessing the server from I don’t even have a clearml.conf file in my home, nor I would expect it to be used anyway … Is there any other instance of such configuration file in the server that I’m not aware of?
if the UI can't guess the location of fileserver, you can follow the instructions here, to let it know what it is
None
The url there has localhost as host, instead of the ip
did you set apiBaseUrl to something else in a private build or through webserver environment variables which set configuration.json file?
I meant where clearml-data is running, so when you upload images to your version, it set the right url
192.168.1.83 is a local network address, is it accessible from your browser?
Hi HollowKangaroo53
when the UI build for production it points to the reverse proxy set by the environment variables you mentions (e.g. apiBaseUrl: '/api')
API server isn't aware of fileserver location, it's clearml-data responsibility to write the correct path in the server.