App version
Production
Issue description
I have Symfonium connected to a Navidrome server using the subsonic connection option, proxied through ngnix with mTLS (cert selected from Android keyring).
When I initially add the server, Symfonium connects without issue and everything appears to function as expected. I can stream music and manage playlists, etc. However, if I attempt to change any settings on the media provider after adding it (such as “Use similar tracks for radio mix”), Symfonium produces an error stating that it cannot get “media provider version,” and refuses to save the change.
Based on the logs (submitted as required), while Symfonium appears to correctly send the required TLS certificates as needed under most circumstances (initial provider connection, playback, etc), it does not appear send the cert when attempting to change a provider setting, resulting in a failed connection.
What I would expect to happen: Symfonium verifies changes using the same process as it does when the provider is initially added. Alternatively, do not re-validate the server if no connection-related fields have been changed (this would also allow making changes while a provider is temporarily unavailable) .
Device type
Phone
Media provider
Navidrome
Steps to reproduce
- Successfully add a working media provider, including selecting required mTLS certs from Android keyring when prompted by Symfonium.
- Return to provider settings.
- Change any setting, such as “Use similar tracks for radio mix” or “Wifi Only”
- Attempt to save the changes.
Additional information
The exported logs are huge and go back to 2025 for some reason.
The useful bits are from today, July 3 and start around 08:38 am.
I searched existing issues first
on
I understand that logs are mandatory
on
Log upload name / description
medianox