What kind of problems do you catch with beszel?

Check out gatus. Super easy to get up and running depending on what type of monitoring you want to do.

You misspelled spyos.

Nothing requires kubetnetes. Can you scale with kubetnetes easier? Maybe, but then you’d have to learn kubetnetes. Even super scalers like Netflix ran for decades without kubetnetes and then for other reasons they moved. Self hosters only need kubetnetes if they want to learn it.

By your parents a computer and put it on their network and back up locally and remotely on their system. Bonus run immich for them also.

I get all my back up redundancy but helping others host.

Why not just straight wireguard?

Look at dmesg?

Look at the last two boots:

journalctl -o short-precise -k -b -2

I run it in a container without problems. All you have you do is bind it to port 80 and 443. I prefer the container to running it directly within the host OS for ease of portability.

Also strongly recommend building it with support for DNS based validation. Using DNS validation you can have multiple instances running across the different servers you have to easily switch to or provide better local routing. For example please. I run one caddy frontend on a VPS that routes my traffic most of the time, but when I’m at home my DNS points me at a caddy instance that is running on my server on my home network avoiding the path of out to the internet and back home. Using http based validation would require me to sync certs around.

This is even the recommended way. If. You are rolling your own docker images for all the supporting containers you are going to have a bad time. OP I guarantee if you see this and shrug it off you’ll be back here. Many migrated to this from their custom docker set ups.

Renovate? Hrmmmm

Are you routing DNS over wireguard the whole time or do the DNS servers change when you go from public internet to your home network?

If you are using the same DNS servers i.e. always using DNS over wireguard then there isn’t really a lot you can do.

The way I do this is when I am on my home network I use the DNS on that network, i.e. the adguard instance I set up and also override DNS names with, when I am on some public internet i.e. via cellular, I use whatever DNS server they have. So on home network jellyfin.bob.com returns 192.168.8.3 (for example) and on the public internet jellyfin.bob.com will return 68.32.23.11 (i.e. my public IP address).

However that requires multiple DNS servers.

What is an example server where you’d like to do this (it may give us more options) and how is your DNS set up?

Your home router knows nothing about your wireguard VPN unless it is also configured to be a peer in it. So in short no it will not recognize and route your connection locally unfortunately.

Are you using TLS here at all? Can you give me an example of how you access this on your phone when remote vs when local.

e. g. From my phone on cellular I go to Firefox and type in jelly.bob.com which resolves to my wireguard ip hitting the VM in the cloud that then using nginx as a reverse proxy to reach jellyfin over my network.

Remote network: jellyfin.bob.com Phone - > VM - > Home Server where Jellyfin is running

Is each hop is over wireguard i.e from phone to VM from VM to Home Server?

On the local network: jellyfin.bob.com Currently looks the same as the above and what youx like it to do with the same name is go: Phone->Home server

Even when wireguard is on, correct?

DNS server you use from your home network retuns 192.168.1.20 for your service hosted at jellyfin.Bob.org

The DNS server you hit when publically looks up jellyfin.Bob.org and gets the IP from the nameserver you have set with your domain registrar often just theirs and you set this to your home WAN ip.

You have to configure both. I use opentofu / terraform to configure both all from the CLI. Any software like DNS that has a bunch of implementations that doesn’t have Open-Tofu support gets skipped and an alternative is found at this stage. You just can’t beat config as code for this type of set up.

You can also use NAT reflection which will effectively reroute the connection from within your network to your external IP to work on your local network.

I started with reflection and ended up going to the multiple DNS servers as it felt cleaner and I already was running Adguard so why not.

Both adguard and pihlle have opentofu modules.

Rereading your post (heh): In your case I’d just always serve over the wireguard ip local or not. Why do you want to use the local IP vs wireguard? The overhead of wireguard is pretty low

I was using conversations and from what I understood the server handles syncing of history from clients that have all the history so of one disappears your history disappears. That is what played out in my tests.

Yep. I tried xmmp over matrix and while the setup was relatively solid and straightforward to configure the clients and lack of central history were too much of a step back so I went back to matrix.

Are all these long form posts written with the help of AI? The length of posts here seem abnormally long for this type of forum. I’m not saying I don’t like it but I’m immediately skeptical when I see a giant post nowadays.

Ampache ftw! Thank you for all the development work!

So this is like a bridge from sources of music (local files, subsonic, YouTube, etc) to players of music that also stores its own metadata?

Wow lots of people who can’t handle hosting. Ignore the nay sayers. Run your VPS just you know keep it up to date, back it up and use a long stable release.

It seems like the same crowd that can’t figure out email also can’t figure out running a server in general on the internet. Go figure.

This is exactly what I came here to find. Thank you for posting it. If I can be so bold selfhosters should really be leaning this way searxng is great but it still uses big tech.

The other thing we need is a way to identify good crawling agents or *smol agents over corporate bots that just steal content.

If selfhosters can unite and build a good index perhaps searching can go back to the way it was vs a vector to sell you more and collect your data.