-
Notifications
You must be signed in to change notification settings - Fork 131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Http 401 in Reports section #218
Comments
Hi @mathrb, ClearML Server contains a reverse proxy that should allow calls to |
Hi @jkhenning , |
And the cookie set on the main WebApp page, can you share its details? |
Hello @jkhenning Here is the cookie when a request is made to
For standard requests to
|
Can you share the cookie's properties? domain, secure, etc.? |
In the cookies section, I've got 2:
|
These look OK... |
Is the issue my web browser (firefox/chrome) not forwarding the cookie to the |
If that were the case than the WebApp would not work at all |
Hello,
We have a selfhosted version of clearml. Everything works fine but the reports section, where widget integration (for example to display tasks plots/scalars) does not work.
Looking at the request being made by the web browser shows a 401 Http error:
POST
https://app.clearml.<REDACTED>.com/api/v2.24/reports.get_task_data?
Other requests made by the front to the API look like this and work:
POST
https://api.clearml.<REDACTED>.com/v2.24/projects.get_model_tags
It look likes widgets don't use the right hostname to perform api queries.
Any idea of what is misconfigured?
The stack is deployed via docker-compose on a linux server
Update:
Could it be because of this code found in the clearml-web repository:
https://github.com/allegroai/clearml-web/blob/aa038f4f8253f45558efe78cc43cf24045ff13d7/src/app/app.constants.ts#L82
As I understand it, it reroute to url + api. In my case, it should be
https://api.clearml.<REDACTED>.com/
instead ofhttps://app.clearml.<REDACTED>.com/api
. Any possible workaround?Thanks
The text was updated successfully, but these errors were encountered: