Ha, same here. HAProxy plugin running on my opnSense. I should probably try caddy because HAProxy is complete overkill for my requirements.

This is the perfect opportunity to set up a pihole. Its primary purpose is to block ads network wide but since it is essentially a DNS with a block list you can also set custom dns-entries.

There seems to be a bit of a misunderstanding of what a reverse proxy does.

The proxy should accept requests on port 80 and 443 and on the basis of the requested website route you to the correct adress:

1. Request for jellyfin.mydomain.com comes in
2. Reverse proxy checks where it should reroute it -> host.of.jellyfin:8443

So your client thinks its talking to your jellyfin-instance over port 443 but in actuality your proxy reroutes the traffic to wherever your jellyfin needs it to arrive…

/Edit: Ah just saw that it redirects 443 requests to your router. Can you configure a DNS override on its config somewhere?

Try running this command on your target system:

cat $HOME/.ssh/authorized_keys

Does the private key part of your key pair show up in the list?

AMD EPYC 7B12 / 256GB RAM / Supermicro H12SSL-i / 4x2TB Samsung 980 Pro in ZFS RAIDZ-10

Total overkill for what is currently running on it. But who knows what the future brings.

Current:

• Docker-based – Portainer – SabNZBD – Radarr – Sonarr – Prowlarr – Gotify – Jellyfin – Bitwarden – Paperless NGX – Watchtower

• As a VM in Proxmox VE – KASM workspaces because it’s really cool – Random Windows 11 VM attached to KASM for some remote work – Random Windows Server 2022 to play around with

• AS an LXC in Proxmox VE – Ubuntu-based SSH jump-host – Ubuntu-based Unifi-controller – Ubuntu-based crowdsec concentrator