How hard do you suppose it would be to add integration with Qobuz?
this post was submitted on 04 Jan 2026
439 points (99.3% liked)
Selfhosted
54450 readers
833 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 2 years ago
MODERATORS
I could look into it. Open an issue on Github if you like, and I'll see what I can do. Thanks!
Done
Awesome!! I had been wanting to make something like this, but never got around to it. Excited to try it out tomorrow
Connects to Lidarr
So, I don't run the 'arr stack', and am not interested in downloading, but I would like recommendations on new music. I am running Navidrome which scrobbles to Listenbrainz. How would Mixarr fit into this scenario?
I pushed an update that adds a "review only" mode, with Lidarr no longer being a required connection.
https://github.com/aquantumofdonuts/mixarr/releases/tag/v1.1.1
Add any Subscription and set the result handling to "add to review queue". Then, just look in the Review Queue tab for your recommendations.
Oh snap! Man, you didn't have to do all that just for one dipshit who didn't understand what Mixarr was. I should have done a bit more reading. I feel embarrassed. I will spin this up in an hour or two when I get my chores done. Thank you so much!
Haha no worries! It's a useful feature. No reason to lock the subscription engine behind a Lidarr connection.
But I think I will rest for a while now lol.
Why would you need this for your scenario? If you're not downloading you can simply check the listenbrainz recommendations in the playlists that it creates for you
Because I'm a dumbass who didn't really understand what was going on. Kindly disregard the doddering old man.
Oh lol I see, it happens
Been playing around with it over the last few days and I love it. I don't use Spotify, but it does a great job at looking at my Plex library and recommending similar artists.
Great job, and thanks!!
Thank you so much! Glad you are enjoying it.
This is such good news to see this on my frontpage today, I'll definitelybe giving this one a try later. Mad respect and appreciation for the amount of time this must have taken for you to make this. Thank you so much!
I appreciate the positive feedback, hope you find it useful
really liking this.. i've been using SoulSync, but its very buggy, and its mainly a soulseek driven downloader.. lidarr is the way to go,
which trackers are good for music? should i just try and get a red invite?
I am trying to put this behind Haproxy but not having much luck, I keep getting "client sent an HTTP request to an HTTPS server".
Anyone have a clue how to resolve this?
I understand this image has its own caddy reverse proxy, not sure how to bypass that at the moment.
Hi, I think you can resolve this by forwarding your reverse proxy to http://mixarr-ip:3010/. That bypasses Caddy altogether. Give that a try, and let me know how it goes.
I am running in docker, I got 443 pointed at 3443.
I saw the 3010 setting in the docs, i just can't figure out if 3010 is pointed at 80?
3010 is the web port, on the web container itself (direct connection the the web ui). 3443->443 and 3080->80 are the Caddy ports, which also point to the web ui (just proxied through Caddy). Hopefully that's not too confusing.
Understood, though it's still kicking my butt TBH.
Exposing port 3010:3010 seems to get me a connection refused. But I can still connect to port 3443:443. Both ports are set to TCP.
Guess I'm just exhausted, will play around with it more tomorrow. Thanks for your help.
Sure thing. Can you share your docker-compose.yml or docker cli string? Maybe I can help.
First, thank you for making this. Seems very useful.. That being said I'm having the same issue, even after mapping port 80, it redirects to https/443 no matter what I do.
services:
mixarr:
container_name: mixarr
image: ghcr.io/aquantumofdonuts/mixarr:v1.1.0
ports:
- 3010:80 # Edit: change 80 to 3000 in order to bypass caddy in the container
- 3443:443
volumes:
- ~/mixarr-data:/data
environment:
- SESSION_SECRET=$(openssl rand -hex 32)
- FRONTEND_URL=https://my-domain:3443/
- BASE_URL=http://my-domain:3010/
restart: unless-stopped
Edit: Just realized you have it using caddy, always, and it is set to redirect to 443. You should give people the option to run without caddy in the container. I have my own instance of caddy running, I don't need it built in.
That being said, changing it from pointing to port 80 and instead to port 3000 allows me to access it over http but ends up having authenticaton issues when trying to change settings.
Edit 2: Oh there is a much more robust docker-compose file. I was just going based on the readme. Will give it a try a bit later.
Thank you, your comment here helped me sort my issue out.
For anyone if you want to access this without the built-in proxy/caddy server set your ports in your docker compose like so.
- 3010:3000
- 3443:443 (this is the caddy port inside the container)
I haven’t figured out how to use the we hook feature to connect to Pushover… maybe it can’t?
This sounds great. I will have to check it out when I'm back home. I have been missing a music discovery tool as I am trying to avoid using any of the corporate overlord algorithm machines.
Awesome! I hope you like it. I've successfully converted my household from Spotify to Plexamp using this. Setup a few subscriptions, let the new artists and recommendations roll in, and you have a constant stream of new music.
Nice. Couple of things:
- The link in your post is broken 😉
- Consider doing with Jellyfin anything you've done with Plex. Plex is on it's way out, especially with Fediverse users.
I think the link is fixed now?
I will definitely take the Jellyfin suggestion to heart. Mixarr is Plex-centric because that's what I use, but I see that Jellyfin has a large share as well. Thanks for the suggestion!
Edit: Added Jellyfin support. Four new subscription types in the "My Library" subscription preset group. You can pull and rebuild docker (or pull the latest image) to get the changes.
Bloody hell. From request to implementation in less than 10 hours?! Amazing.
Might also consider looking into Navidrome support. Not sure if it's even possible but in my experience Jellyfin's music experience is kinda crappy.
Yup, link is golden now.
GitHub link is funky, need to remove the ()
Thank you. Link is fixed.
Omg you are a saint. I was missing a tool like this. Will check it out ASAP.
load more comments
(1 replies)
Is it possible to set this up with navidrome instead of lidarr?
Navidrome can scrobble to Listenbrainz which this supports.
First off thank you so much this is exactly what I've been waiting for.
I looked at the compose file and it doesnt seem to have the base image in there, just the DB and web setup.
I'm not super experienced with docker but would love to deploy this through my dockstarter setup - am I missing something here, is there a way to get it up and running through compose now?
I released a Docker image. You can get it here: https://github.com/aquantumofdonuts/mixarr/releases/tag/latest
Let me know if you have any issues!
load more comments
(4 replies)
view more: next ›