medariox
commented
4 years ago You need to proxy the websocket protocol when running behind a reverse proxy. See: https://github.com/pymedusa/Medusa/wiki/Reverse-Proxy-setup
Closed zaans2 closed 2 years ago
medariox
commented
4 years ago You need to proxy the websocket protocol when running behind a reverse proxy. See: https://github.com/pymedusa/Medusa/wiki/Reverse-Proxy-setup
zaans2
commented
4 years ago It is sort of fixed. It sometimes still only flashes results at the start, but most cases doing a forced search fixes that. However if a forced search yields no results it doesn't give you an indication that it can't find results. The spinner keeps spinning and there remains no data in the table.
I suppose the 404 error is in this case correct, since the API can't find results for the query given so it returns 404 (Not Found)
Did the setup for running behind a reverse proxy change in ~0.4.1/recently? Before that it all worked fine running behind the reverse proxy the way I had it set up
p0psicles
commented
4 years ago No that didn't change. But I know there is some weird race condition, that results in not showing results at loading of the page. And yes, the 404 is by design
zaans2
commented
4 years ago Is there anything I can do to figure it out?
p0psicles
commented
4 years ago Nah. It's pretty complex. Using api calls mixed with websocket updates. Maybe it's too complex, and I need to address that. But it should be functional. With a refresh you should always get all results.
Maybe you could check for patterns? Like, maybe only visible with specific providers? I dunno.
Will take some time before I dive in. Need to finish the add-show Vueify first.
jeffgus
commented
3 years ago Also seeing this. For me, it seems to work fine on Firefox, but Chrome has this issue.
p0psicles
commented
2 years ago I think this has been fixed already?
Describe the bug Whenever I try to do a manual search on an episode or season it will flash some results in the beginning but they disappear. Force Search just runs endlessly and doesn't return actual results. Refresh results gives me some results some of the time, but not from all providers even though they do have results. This has been happening since 0.4.1 iirc.
To Reproduce Steps to reproduce the behavior:
Expected behavior Getting the results of a manual search shown in the table for longer than half a second and results from all providers (given that a provider has results to the search ofcourse). (And to show the text in a readable color instead of the current white, but thats a different issue)
Medusa (please complete the following information):
Debug logs (at least 50 lines): General > Advanced Settings > Enable debug
Additional context The browser console throws all kinds of errors. I get a
WebSocket connection to 'ws://<my-ip>:<port>/medusa/ws/ui' failed: Error during WebSocket handshake: Unexpected response code: 400error on almost every single page regardless andGET http://<my-ip>:<port>/medusa/api/v2/providers/nyaa/results?limit=1000&season=1&page=1 404 (Not Found)errors whenever I try to manual search for all the providers I selected apart from the 2 that actually show results (but only after I hit the "Refresh Results" button)