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'm testing xinference in kubernetes, i've tried loadbalancer, traefik and istio to expose the service, and I notice when using loadbalancer, which url is http://<my_ip> ,everything is ok. When using traefik or istio, which tls cert is correctly configured, 80 to 443 redirection is always on and url is https://<my_domain> , running models page is empty, it shows No Running Models, through web dev tools, I got error in console
Mixed Content: The page at 'https://<my_domain>/ui/#/running_models' was loaded over HTTPS,
but requested an insecure resource 'http://<my_domain>/v1/models'.
This request has been blocked; the content must be served over HTTPS.
Error: TypeError: Failed to fetch
at ds (fetcher.js:19:10)
at index.js:57:7
at index.js:111:5
at ou (react-dom.production.min.js:244:332)
at Sc (react-dom.production.min.js:286:111)
at cc (react-dom.production.min.js:273:185)
at Vo (react-dom.production.min.js:127:105)
at react-dom.production.min.js:283:470
at Cc (react-dom.production.min.js:281:398)
at ac (react-dom.production.min.js:270:269)
(anonymous) @ index.js:104
Promise.catch(async)
(anonymous) @ index.js:103
(anonymous) @ index.js:111
ou @ react-dom.production.min.js:244
Sc @ react-dom.production.min.js:286
cc @ react-dom.production.min.js:273
Vo @ react-dom.production.min.js:127
(anonymous) @ react-dom.production.min.js:283
Cc @ react-dom.production.min.js:281
ac @ react-dom.production.min.js:270
C @ scheduler.production.min.js:13
E @ scheduler.production.min.js:14
when I directly access http://<my_domain>/v1/models or https://<my_domain>/v1/models, I can get the correct data.
To Reproduce
expose and access service using https with valid cert will cause the error
Expected behavior
running models page display current running models
Additional context
i also check the network activity, when using http, the following fetch events triggered by fetcher.js:19:
but when using https, only the first fetch activity happend, and then blocked by browser due to This request has been blocked; the content must be served over HTTPS. as I mentioned above.It is worth noting that in respons headers the Location is http:
qaz-t
changed the title
[BUG] When deploying and accessing services via HTTPS, the 'Running models' page always display 'No Running Models'
[BUG] When deploying and accessing service via HTTPS, the 'Running models' page always display 'No Running Models'
Jan 27, 2024
Describe the bug
i'm testing xinference in kubernetes, i've tried loadbalancer, traefik and istio to expose the service, and I notice when using loadbalancer, which url is
http://<my_ip>
,everything is ok. When using traefik or istio, which tls cert is correctly configured, 80 to 443 redirection is always on and url ishttps://<my_domain>
, running models page is empty, it showsNo Running Models
, through web dev tools, I got error in consolewhen I directly access
http://<my_domain>/v1/models
orhttps://<my_domain>/v1/models
, I can get the correct data.To Reproduce
expose and access service using https with valid cert will cause the error
Expected behavior
running models page display current running models
Additional context
i also check the network activity, when using http, the following fetch events triggered by
fetcher.js:19
:and it cause another fetch activity
but when using https, only the first fetch activity happend, and then blocked by browser due to
This request has been blocked; the content must be served over HTTPS.
as I mentioned above.It is worth noting that in respons headers theLocation
ishttp
:The text was updated successfully, but these errors were encountered: