Anejey

joined 1 year ago
[–] [email protected] 1 points 11 months ago

Just 6 days now. It was going for 31 days before, but I did a reboot just to make sure everything works properly.

[–] [email protected] 1 points 11 months ago (1 children)

I use all three.

  • CF tunnels to access generic apps I want public.

  • Tailscale to have remote access to my home network.

  • Wireguard tunnel going to a VPS for apps that I don't feel comfortable running through CF due to the bandwidth (Jellyfin, AzuraCast).

I totally could move everything that's on CF tunnels over to Wireguard, but I see no need to do it. Cloudflare is trustworthy enough and I like the additional protection it offers.

[–] [email protected] 1 points 11 months ago

Other than Navidrome (which is probably your best option right now), I also use AzuraCast. It's essentially an internet radio playing my playlists 24/7 that I (or anyone, but I obviously don't just share it with strangers) can listen to from anywhere.

[–] [email protected] 0 points 11 months ago (1 children)

I've had great success with this script. It's a script that makes a Wireguard tunnel between your local network and the VPS, so no opening of ports at home needed. It's made for Oracle VPS though, but it'd probably work elsewhere too.

My current setup is this:

Cloudflare DNS -> Caddy (VPS) -> Wireguard tunnel -> NginxPM (Home) -> services

You can just have the Wireguard tunnel go straight to docker though.

 

I still barely believe it honestly. I'm a student "freshly" outta school with no experience, and I've been struggling finding a job for a while.

I had an (first) job interview recently and while I didn't have much to offer, I seemed to somewhat impress them with my home labbing. I run Proxmox at home for my self-hosted things and got a decent amount of experience with it, and it's what they use a lot as well. It's not that common in my age group to be interested in stuff like this, apparently.

Anyway, this is barely worthy of a post, but I'm really excited. I don't really know how it'll work out as I still got plenty to learn, but it's a big step forwards for me.

[–] [email protected] 1 points 11 months ago

Tailscale, and a Cloudflare Tunnel going to Nginx Proxy Manager. So all three, in a way.

[–] [email protected] 1 points 1 year ago

Can't really go wrong with ext4 for filesystem.

Make a partition with fdisk, format it with mkfs. As for fstab make sure to mount it via either disk ID or UUID.

If you need details just Google it. There's a shitton of guides out there.

[–] [email protected] 1 points 1 year ago

Yeah, that's the problem when something like that is free. It's better to always have backups.

I use my Oracle VPS just for Wireguard to bypass CGNAT. I wouldn't host anything important there.

 

Hello.

My Jellyseerr instance in a Proxmox LXC crashes for some reason, nearly everyday at 3am. I'm not sure how to fix it. It doesn't max out RAM nor CPU.

I have Jellyseerr behind NginxPM and use Pi-hole for DNS. Everything (Radarr, Sonarr, Jellyfin) is also referenced by the domain, not ip:port.

https://preview.redd.it/tj5gv05u2srb1.png?width=1337&format=png&auto=webp&s=c0ae628c0f877e4ea1727f61844848bad45b027f

https://preview.redd.it/8ct3zuf44srb1.png?width=1112&format=png&auto=webp&s=951b27297d128b6fc76731355766c34d90ba0e7c

The last thing on logs is always Jellyfin Sync, but sometimes it crashes early, and other times it crashes at like 3:50, so I'm not sure if that's the actual cause.

Pi-hole activity also goes up quite a bit, but it doesn't report anything going wrong in diagnosis.

https://preview.redd.it/sbgyl6y63srb1.png?width=638&format=png&auto=webp&s=069fc061b063ddac580c55ac8aeef3bc4bef1bb6

Once I start Jellyseerr again, the scans finish and everything works as supposed to. I'm suspecting it's Pi-hole that's the issue, but like I said, it reports nothing going wrong.

I can provide more info if needed. I'm not really sure where to start looking.

Any help is appreciated.

[–] [email protected] 1 points 1 year ago

Also one thing to consider is that running 3 Proxmox machines will allow you to use HA (High Availability). Meaning if one of your hosts go down, others can pick up the slack.

Just one node means everything depends on it.