Hello. Pretty sure I'm doing something stupid, but I can't find it. I have Caddy and Uptime-kuma installed as Docker containers. They are on the same Docker bridge network. Both work fine (with the below exception). I'm trying to monitor Caddy virtual hosts from Uptime-kuma and getting a timeout. If I exec into the Uptime-kuma container, I can ping the host name I want to monitor (and the DNS is resolving correctly to the Docker hosts external IP). But I can't reach port 80/443 using `telnet` or `openssl`. Any suggestions for what I might be doing wrong? Thanks!

I use HomeAssistant automations for all my home stuff, it has an official easy to add Node Red integration available. I played with it a little in the past but didn’t really see any value for me at the time. Now I’m looking to set up a new automation tool that’s not necessarily hardware/home type stuff, moreso the kind of thing you might use IFTTT for, but I want to self host. so for example scraping a webpage, extracting the content of an article, sending to an AI API for summary, then outputting as RSS. I was thinking about setting up n8n, but I wanted to see if maybe the HA Node Red would be just as good (I think it’s a fork right?). That way I don’t need to set up a new VM or anything plus it’ll be already integrated into my backups and proxy etc as part of HA. So has anyone used both and could compare?

Hi! I used to run Plex and forward a port through my vpn so I could access the service outside my network, like on vacation. This meant I could keep my vpn on and still access my content. I use Cloudflared to access other services in this way. Now that my vpn has stopped allowing port forwarding, how can I again access my content while keeping my network private and secure?

My weekly `zpool scrub` came back with this: ``` pool: blackhole state: DEGRADED status: One or more devices are faulted in response to persistent errors. Sufficient replicas exist for the pool to continue functioning in a degraded state. action: Replace the faulted device, or use 'zpool clear' to mark the device repaired. scan: scrub repaired 0B in 02:01:59 with 0 errors on Tue Jul 11 04:02:09 2023 config: NAME STATE READ WRITE CKSUM blackhole DEGRADED 0 0 0 raidz1-0 DEGRADED 0 0 0 ata-WDC_WD120EDAZ-11F3RA0_5PG8DYKC ONLINE 0 0 0 ata-WDC_WD120EFBX-68B0EN0_5QKJ6M8B ONLINE 0 0 0 ata-WDC_WD120EFBX-68B0EN0_5QKJTT8B FAULTED 51 0 0 too many errors errors: No known data errors ``` I only got the drive 6 months ago, well within WD's 3 year warranty so I opened a support case, but do errors like this basically always mean the drive is its way out or is it possible to have false positives?

I’ve got Jellyfin up and running right now on a DS620Slim NAS and it’s running pretty good so far. I’ve seen a lot of people say they prefer Plex over Jellyfin. What are the main advantages to plex?

I've been trying to figure this out off and on for months without any luck. This is my first homelab setup in a while. I have Proxmox running a few VMs, one is Truenas with some drives in direct passthrough. I also have a Proxmox container running Docker which is running a few things, Traefik being one of them. I've got http/https working and figure out LetsEncypt certs via DNS checks through blood, sweat, and tears, but I cannot -- for the life of me -- figure out how to get Traefik to handle smb for that Truenas server so I don't have to have 2 different DNS entries (1 pointing to Traefik for web and one pointing right at the VM for smb). I found the ports Truenas claims to use for smb (and other services) [here](https://www.truenas.com/docs/references/defaultports/) and how to capture TCP and UDP entrypoints on Traefik [here](https://doc.traefik.io/traefik/routing/entrypoints/), but I can't seem to find the right combo for my Docker compose and Traefik setup. Anybody else figure this out? *edit: My fat thumbs on mobile create a lot of typos. I also added the entrypoints documentation URL*

Hello everyone, first time ever posting on lemmy, feels good 😉 I have a question regarding DHCP in my local network. My current setup is as follows: - DHCP provided by router (Fritz!Box 7490) - DNS provided by pi-hole hosted on a raspberry pi - DHCP pushes the IP of the raspberry via DHCP to all clients My problem is: When the raspberry pi (running pi hole) is down for any reason, none of my devices has internet access anymore. This is due to the fact that the Fritz!Box router (aka DHCP server) has no option to push a secondary DNS as a fallback to its clients. One option would be to buy another router which has the option to push a secondary DNS, which I would prefer to avoid, since otherwise I am happy with the Fritz!Box. So I am looking for alternative configurations with my existing hardware. I could for example use pi holes DHCP. Or I could use the DHCP server package of a synology NAS which is also part of my local network. Or is there another option, maybe using some DHCP service on the raspberry pi or in a docker container or something like that? Does anyone have experience with one of these setups and can tell me if it is possible to provide the clients with two (prioritized) DNS options? What would you recommend? Thanks!

Hello everyone! Mods here 😊 Tell us, what services do you selfhost? Extra points for selfhosted hardware infrastructure. Feel free to take it as a chance to present yourself to the community! 🦎