App version
Production
Issue description
Out of nowhere Symfonium isn’t able to play any of my music anymore. It just tries to load the song a few times and then fails either with “Error playing media, ensure that your player support it.” or with “Too many errors, stopping playback.” This happens both for cached and uncached songs, but doesn’t happen when I’m offline.
Device type
Phone
Media provider
Navidrome
Steps to reproduce
- Be connected to the server
- Try playing anything
Additional information
The navidrome server is secured behind basic auth.
I searched existing issues first
on
I understand that logs are mandatory
on
Log upload name / description
promptly
Your server returns errors 400 check it’s logs to know why.
Thanks for the response. It took me a while to check it out.
Apparently Symfonium adds custom headers twice to requests to /rest/stream.view which didn’t play nice with my reverse-proxy. I believe this is a bug as I didn’t add the headers twice in the “Send custom headers” section and they’re not being sent twice in any other requests.
Most of the report for headers are proxy config that do redirect and duplicate them.
Describe exactly your config and settings.
Ok, so I added my navidrome server as a subsonic provider. I have the server running behind an nginx reverse proxy for TLS and authentication. I configured the symfonium provider in the “Send custom headers” option of the “Proxy authentication” section to send a Proxy-Authorization header.
This works fine for the most part but like I mentioned the HTTP requests for streaming send the header twice for some reason. I also tried adding a Test header and it was also sent twice, so it’s not specific to Proxy-Authorization. I noticed the duplicated headers in the requests coming directly from Symfonium with no proxy in between, so I’m pretty sure it’s a bug on Symfonium’s side.
I don’t see anything else config-wise that could be relevant. If you need anything else please let me know.
I forgot to mention that the “Send basic authentication headers” feature works properly in this case, so I’m using it as a workaround instead of Proxy-Authorization.