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
When trying to log in to a self hosted ClearML server with a user specified in the documentation, I kept receiving HTTP error 401 (Unauthorized).
I could only get the new users to work after a full reinstall (following this page until step 11) and creating /opt/clearml/config/apiserver.conf with hashed passwords BETWEEN steps 11 and 12, that is, before docker-compose -f /opt/clearml/docker-compose.yml up -d.
Proceed to the (next recommended page)[https://clear.ml/docs/latest/docs/deploying_clearml/clearml_server_config#using-hashed-passwords] to set up some hashed passwords in /opt/clearml/config/apiserver.conf (e.g., jane with password 123456). Don't forget to restart ClearML server.
Run tail -f /opt/clearml/logs/apiserver.log to monitor when the server is done re-initializing, and to check whether the users are successfully created.
Proceed to http://localhost:8080 on your web browser.
Press F12 and activate the Network tab in Developer Tools.
Try to sign in with one of the new credentials. In my case, I've got error "Unauthorized (invalid credentials) (failed to locate provided credentials)".
6.1 This can also be tested using curl -u jane:123456 http://localhost:8008/auth.login
Once I was able to successfully set up user jane with password 123456 while tweaking users and passwords from step 2, then repeating steps 3 to 6. But it was only temporary, and after the next tweak, even jane couldn't log in anymore.
Expected behaviour
In my opinion, ClearML server should successfully accept a new password after restarting with new settings in apiserver.conf. While it does seem to TRY to do that, apparently it fails unless installation is fresh.
Describe the bug
When trying to log in to a self hosted ClearML server with a user specified in the documentation, I kept receiving HTTP error 401 (
Unauthorized
).I could only get the new users to work after a full reinstall (following this page until step 11) and creating
/opt/clearml/config/apiserver.conf
with hashed passwords BETWEEN steps 11 and 12, that is, beforedocker-compose -f /opt/clearml/docker-compose.yml up -d
.To reproduce
/opt/clearml/config/apiserver.conf
(e.g.,jane
with password123456
). Don't forget to restart ClearML server.tail -f /opt/clearml/logs/apiserver.log
to monitor when the server is done re-initializing, and to check whether the users are successfully created.http://localhost:8080
on your web browser.6.1 This can also be tested using
curl -u jane:123456 http://localhost:8008/auth.login
jane
with password123456
while tweaking users and passwords from step 2, then repeating steps 3 to 6. But it was only temporary, and after the next tweak, evenjane
couldn't log in anymore.Expected behaviour
In my opinion, ClearML server should successfully accept a new password after restarting with new settings in
apiserver.conf
. While it does seem to TRY to do that, apparently it fails unless installation is fresh.Environment
clearml
PIP package not installedThe text was updated successfully, but these errors were encountered: