Hi @<1750327622178443264:profile|CleanOwl48> , it's not a cookie domain issue, when a P{lotly background image is set, Plotly used JS to fetch it, but it omits the cookie when the image and webapp are not on the same site.
we have a workaround, if you properly set the fileserver URL for webserver nginx it will redirect calls from /files to fileserver, and if the UI has WEBSERVER__fileBaseUrl set it will allow the UI to rewrite the call for the image through nginx reverse proxy.
this way the request to fetch Plotly background image stays on the same site and auth cookie get sent.
@<1523701070390366208:profile|CostlyOstrich36> There's still issue in the frontend. The frontend for plots does not include the cookie when requesting the images, but it does when showing the debug samples. (I am using the open source and self-hosting with k8s)
This approach disable file server auth service. Another fix is to set the correct cookie domain.
@<1750327622178443264:profile|CleanOwl48> ,
Are you using the community server or are you using the open source and self hosting?
Also I tried follow None
but it have some SSL issues. The ssl cert only allow for 1 subdomain level (only 1 dot). Is there any work around? I am currently using http only.
Hi, I am getting the same error as well.
On my local setup, everything works fine with a local ip address.
When I request the image directly on my local setup, the browser use the following cookie:
clearml_token_basic: XXX
domian: 192.168.51.60
When I request the image on my k8s cluster, the browser cannot find the cookie and return a 401 respond.
The default cookie level is different as well:
clearml_token_basic: XXX
domain: app.xxx.com
I try plugging the cookie when request from files.xxx.com but it does not works.
@<1523701070390366208:profile|CostlyOstrich36>
Hi @<1762286410452176896:profile|ExcitedFrog68> , if you open dev tools (F12) do you see any console errors?