They’re pretty decent. Really depends on the temperature.

If the room is cool you hear the hard drives over the chassis fans. Power is totally dependent on the CPU. I put a 4790k in the R220 and it would sit around 45-55w average with two 3.5” drives.

I have a Dell R220 and a R240 which I’m looking to offload, free. They’re both specifically for short racks if you happen to be near central NC.

Same as the other reply here, if you’re on your local network most likely be a 192. address. You can find this on the host server by the “ip a” command.

Personally immich is pretty advanced for someone new to homelab, you might find starting with homeassistant or something might be easier to get started. Also immich is super beta right now and prone to drastic breaking changes with each update.

From the little bit I can see in the screenshot I see a 5 starting the IP, assuming that’s a public IP.

Need to know, are you trying to access at home on the same WiFi network or outside your house on cellular?

Have you set up a reverse proxy or done any port forwarding?

Your reverse proxy should have a cert with HTTPS.

https://github.com/jmshrv/finamp

Jellyfin equivalent which doesn’t require a subscription for your own media library.

Use SwiftFin app instead on Apple TV, but better than the Jellyfin app.

This ^

Simple, no ads, and handles HDR super well

I’m sure google will fix that in chrome, like killing adblocker functionality.

Less HTTPS = easier government & advertiser data collection

Corporate nets use 802.1X authentication, risk of a DHCP hijack is very low.

As someone who works in large corporate networks, we absolutely don’t assign static IPs outside of core network gear, it’s impossible to manage a fleet of servers in this way with scaling in mind.

Instead of doing a manual action in two different places and having to keep them in sync, just do it once on the DHCP server. Setting a static IP on the server is superfluous.

good general advice until you have to try to explain to your SO the VPN is required on their smart TV to access Jellyfin.

don’t do this, use DHCP reservations instead so you actually have a list of all your servers and most routers register hostnames in DNS for you which is even better.

My personal opinion, as soon as you’re charging and providing SLAs you’ve exceeded what you should be doing on a residential ISP.

I’d really recommend putting your app in a real cloud solution, which can provide actual load balancing via DNS natively for regional failover if you desire.

For what OP is asking DNS has no part in DNAT, they need a load balancer.

Personally, asking about high uptime on a residential ISP is the larger issue here, but alas.

Every “plug and play” NAS I’ve had has been garbage, riddled with adware and had to be firewalled from the internet. After a year they just get insanely slow because they put the worlds’s cheapest ARM SoC in there.

Personally just take your drives out and stick them in an old PC and install truenas, or just straight ZFS on Debian. Then you can run your containers on the same machine like Jellyfin, etc.

fyi you can get a wildcard from letsencrypt for free

There’s nothing bad per se, but obviously not sharing the inner workings of your internet facing server is just another step to protect yourself.

You mention in the OP this is for a business, my opinion you should be working on a professional resource/developer to manage this for you and not random Lemmy users.

On the use of Caddy, your configs here host a lot of sites with many specific configurations, I’m not sure caddy can support all of this. nginx is the tool of choice for a wide majority of the internet for a good reason.

I ran opnsense in a VM for years with no issue, just recently went to dedicated hardware. Every now and then I’d want to replace a drive or swap the GPU in the host for jellyfin and taking the internet out with it sucks a lot.

Being able to snapshot opnsense is cool, but opnsense also has a very robust backup and restore system so idk.