I use Lidarr to watch for new releases and try to get some bootleg albums, while main way of getting things is trough some websites or just pulling stuff from qobuz directly.
All the music is FLAC with a small percentage in mp3 320. also, man sometimes wants to get that 300GB discography pack with 6 different releases of the same album 😁
Do you have sample of what kind of errors you’re getting? are they docker related or service related? as in jackett can’t connect/reach sonarr for example?
🥶 is this it? Do I have rizz now?
I got a used mini pc to run as a media center, running the arr stack and torrent client that’s bound to the VPN interface. For usenet stuff I don’t care is it on VPN or not. Its running headless.
If you make sure that the torrent client is set to be bound on the VPN interface, you are fine, if VPN is not up, it should not start, since the interface is not up. For VPN I use wireguard and set the VPN to be brought up by via wg-quick command and use systemd to start it during boot.
You’ll be fine using it for personal stuff along with pulling stuff from high seas.
looks like the guy from History channel or something
how come you didn’t warn me last time?
Definately great using on the go, ease of use 10/10
I’m using usenet.farm, works well
I was running most of them and added Sync - looked fine, but Connect / Voyager work fine for my personal taste, I’m just waiting for Infinity to come out with a full featured stable release. if dev wants to charge for no ads version or ultimate version, it is up to them, and up to the users if they are willing to pay them this. So, it all depends. I wouldn’t go ahead and attack them just because.
Check netmaker for wireguard vpn if you want a ui, but its straightforward to set it up manually.
I’d say, what kind of security are you talking about? Apart from standard HTTPS to keep things encrypted, there are other layers if you want to keep your service exposed to the internet.
Also how things are installed and if they are correct, proper file permissions. nothing different than having it on the server somewhere. You just need to keep thing up to date and you’ll be fine.
I like it here on Lemmy as there are quality talks from people and not too much circlejerking same concepts around. I actually like going trough here.
About 6 year uptime on one machine before we shut it down and relocated.
Yes, thats exactly it.
Make sure your HAProxy is listening on the wireguard interface as well.
Once you have the wireguard tunnel working, do a quick test, like curl -H "Host: domain.tld" https://router_wireguard_ip/ and if that works, add in the iptables roules and you should be all set.
Thanks for the reply, flux is pretty good, I’m using ArgoCD, but both are basically following gitops priciples.
I might give k3s a look and see how ot all work together.
What would be a benefit to run k8s at home, apart from bit dealing with it, compared to docker-compose on a single or two nodes? or docker swarm? Unless there is a big load of services that are selfhosted, which I get, and the autohealing from k8s as the orchestrator.
Just courious, not taking a swing. Thanks!
Yes, that would be possible with this setup. Port on which HAProxy listens just needs to be publicly accessible, and just DNAT traffic from the VPS to your $IP:$PORT .
Technically everything is possible, I just don’t have context if you have a static IP with your ISP or it changes every so often (daily, weekly, every n months). If it’s not, you might consider using a VPN connection between VPS and your router to keep the connection open at all times, and also not exposing HAProxy directly to the live internet.
did it before my smoke break