Yeah, you and I have very similar use cases with this. Gluetun, VPN, download clients + *arr stack, I get it. I’ll be sure to update with a solution, if I spot one (when I get around to looking)!

I am also currently dealing with this same exact issue, I’m wanting to run multiple instances of Lidarr for MP3 / FLAC libraries with Gluetun. I don’t have an answer (I haven’t put in the time to try and solve it yet), so apologies if I got your hopes up. I’m just here to confirm that others have this issue too!

Edit: Regarding that documentation, it seems like it’s not saying that changing the port breaks it, it’s just that you have to set both sides of the mapping to be the same. The default is 8080, so instead of 8080:8080, change the mapping to 8081:8081. That’s how I’m reading it, anyways.

I should also mention that the closest that I got to fixing this was to boot up my 2nd Lidarr container separately, setting the port in the Lidarr WebUI console to something different (8687, for example), and then attach it to my Gluetun docker compose file. I did a docker compose pull to update my stack, then docker compose up -d for it. You might try this approach, and tinker around with it. I just haven’t had time to really play with this “solution”

Edit 2: Played more with the solution I mentioned, and that LifeBandit666 found. We both gave the same solution, and the solution seems to work. Just don’t be a dumbass, and remember to do application configuration to your container (unlike me, who, after putting the container into my Gluetun docker compose file, forgot that I didn’t do application configuration and just saw a bunch of errors with Lidarr).

Yeah that’s true. Different styles of deployment, in the end all that matters is that your application is up and running

If I already have a docker environment set up, why not use the container? I use containers for most of my stuff, if I can. It makes many aspects of system management so much easier.

Ah, I see. Looks like some other people in this thread gave you some good info, I’ll have to keep this in mind if I ever need to change my approach. Happy to hear you got a good answer!

My solution to this was a radicale docker container, with DAVx5 on f-droid. Very lightweight, just works without much configuration needed. I don’t use my phone for email much, so I just use thunderbird for my email client

Would love to deploy this, but unfortunately I’m running server equipment that apparently doesn’t support MongoDB 5 (Error message MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that!). Tried deploying with both 4.4.18 and 4.4.6 and can’t get it to work. If anybody has some recommendations, I’d appreciate hearing them!

Edit: Changed my proxmox environment processor to host, fixed my issue.