Right here.
This should help maybe
Right
Exactly this glitch I had.
So just remove the provider, and add it anew
Unfortunately, reconfiguring the provider (removing and re-adding) didn’t work.
I’ve published a Git repository on GitHub that provides a ready-made Navidrome with a song and a cover, including a basic auth Nginx proxy and a Man-In-The-Middle server. To recreate it, just start the stack with docker-compose up, open the Man-In-The-Middle in the browser, connect the app, and play the song.
I’ve included the description and all the passwords used in the readme.
Not to point fingers, but
Idk, just my assumption, if it were an issue by proxy manager, we’d be seeing a pattern across all the requests, i.e. all the requests made would have repeated headers.
In my case it happened only when Symfonium requested one specific path (from what little info I can read here, also seems to be the case), while other paths worked without an issue
Did you test this?
What did you get when tested independently?
EDIT: so, the test fails when using basic authentication headers, cuz symfonium appears to send the header twice, BUT when using custom header option, and properly configuring that instead to reflect username/password, it worked flawlessly without any errors.
EDIT: i might have previously enabled basic headers earlier, but honestly only today did i learn what’s it used for, but i don’t see how would that cause error on my end, when i never implemented check for that header, so it should have just sent headers and nginx ideally should have ignored it
Currently using the following setup. Using a simple header, with custom header name and value (128 chara long). This works for me without any issues.
Thanks for providing something actionable.
I can finally reproduce, fun one in a library doing that after Symfonium log system.
Will be fixed in next release.
It works now 
Thank you so much 