Ampache VS selfhosted-music-overview

I'm using the nginx config from the installation. I've also tried it via docker as well, but I get the same results there.

I'm not sure if this would fit all your needs aside from running on Linux but Ampache [1][2] has been around for a very long time and has the ability to mesh with other instances. It started as a small project run by some students at OSU and evolved over time.

[1] - https://ampache.org/

[2] - https://github.com/ampache/ampache

Great news! One thing, the 6.0.0-preview1 section of the releases page says the changes are listed at https://github.com/ampache/ampache/wiki/Ampache-Next-Changes but that points to changes in 5.0. The link should be https://github.com/ampache/ampache/wiki/ampache6-details

Check this: https://github.com/basings/selfhosted-music-overview

For the client I'm looking at symfonium as it looks like it has android auto support going off of this github list.

Here's a good overview of the feature sets of most of the popular ones: https://github.com/basings/selfhosted-music-overview

The most liked client is symfonium which works with several different server implementations. It appears that its dev also tries to bundle the subsonic power to improve the subsonic implementation and tries to prevent a sea of subsonic forks. I did not research about music servers in a while but I'll check it out and add it to https://github.com/basings/selfhosted-music-overview . Thank you guys for your experience and insights! It's really helpful to see what the people love and hate about their setups.

You can check https://github.com/basings/selfhosted-music-overview to have an idea of the features you can implement. There is also a lot to be done to properly handle multi value tags, artist relationships, etc. Good luck!