Closed tofuliang closed 1 month ago
After some investigation, Supersonic received a 403 response from Navidrome.
Perhaps changing the User Agent from Go-http-client
to something else might help?
I use Navidrome myself and have not run into this issue so I don't think the user-agent is the issue. Does this only happen with the playlists page? Or do you also get crashes when loading the albums, artists, etc pages? In any case, we don't want to be crashing even if a 403 is returned so I will look into fixing the crash from your stack trace
I figured it out using Charles proxy. I'm using a third-party Navidrome service that is protected by a WAF. The WAF detects the Go User Agent and directly responds with a 403 error.
I tried changing the User Agent to something else on my local machine, and it no longer crashes.
Would changing the User-Agent to "Supersonic" work? Trying to evaluate options for a hardcoded user agent
Yes, "Supersonic" works !
@tofuliang I pushed a fix, if you can build from source it'd be great if you can test it and let me know if it resolves it on your end
Oh, I forgot you can download the Github Actions build to test the fix as well: https://github.com/dweymouth/supersonic/actions/runs/11388277777
@tofuliang I pushed a fix, if you can build from source it'd be great if you can test it and let me know if it resolves it on your end
I built it from source and can confirm that it fixed the issue. Thanks a lot!
Seems navidrome is not respond correctly.
OS Version : x86_64 14.6.1 (23G93)