qdrant/qdrant-web-ui

405 Method Not Allowed

samedovzaur opened this issue · 4 comments

I'm keep getting this error do you guys know why?

Visualization Unsuccessful, error: {"message":"Request failed with status code 405","name":"AxiosError","stack":"AxiosError: Request failed with status code 405\n at qte (https://[CENSORED URL]/dashboard/assets/index-22a6d29c.js:295:959)\n at XMLHttpRequest.d (https://[CENSORED URL]/dashboard/assets/index-22a6d29c.js:295:4075)","config":{"transitional":{"silentJSONParsing":true,"forcedJSONParsing":true,"clarifyTimeoutError":false},"adapter":["xhr","http"],"transformRequest":[null],"transformResponse":[null],"timeout":0,"xsrfCookieName":"XSRF-TOKEN","xsrfHeaderName":"X-XSRF-TOKEN","maxContentLength":-1,"maxBodyLength":-1,"env":{},"headers":{"Accept":"application/json, text/plain, /","api-key":"[CENSORED API KEY]","Content-Type":"application/json"},"baseURL":"https://[CENSORED URL]/dashboard/","method":"post","url":"collections/me_BOT/points/scroll","data":"{"limit":500,"color_by":"source","with_vector":true}"},"code":"ERR_BAD_REQUEST","status":405}

Is there any update?

What request are you trying to execute through the web UI?

Are you sure the HTTP method you're using is correct?

We also have this problem. We are running a dockerized qdrant and access it via nginx with TLS. We tried to debug the proxying and everything, but couldn't get it to work.
Accessing the web UI in general works. But clicking on "RUN" in visualize causes the same error as above.
A curl POST call directly on the host also causes a 405, so it looks like it's not an nginx or TLS problem.

curl -v --data '' http://localhost:6333/dashboard/collections/<mycollection>/points/scroll

*   Trying 127.0.0.1:6333...
* Connected to localhost (127.0.0.1) port 6333 (#0)
> POST /dashboard/collections/<mycoellection>/points/scroll HTTP/1.1
> Host: localhost:6333
> User-Agent: curl/7.81.0
> Accept: */*
> Content-Length: 0
> Content-Type: application/x-www-form-urlencoded
> 
* Mark bundle as not supporting multiuse
< HTTP/1.1 405 Method Not Allowed
< content-length: 50
< vary: Origin, Access-Control-Request-Method, Access-Control-Request-Headers
< content-type: text/plain; charset=utf-8
< date: Fri, 09 Feb 2024 15:36:27 GMT
< 
* Connection #0 to host localhost left intact
Request did not meet this resource's requirements.

Any info we can provide to help narrow this down?