• 0 Posts
  • 3 Comments
Joined 28 days ago
cake
Cake day: October 3rd, 2026

help-circle

    • Forgejo for private git repos, coz F GitHub (F as in paying respect obviously… :v)
    • Portainer, though don’t use much as of late as I got used to the CLI
    • qBittorrent for Linux ISOs. No, really, I use it to download Linux ISOs :v
    • WireGuard, several instances, some for accessing specific services, one for accessing GeoIP blocked content when traveling
    • Vaultwarden for managing passwords
    • Home Assistant for managing a couple of sensors
    • Nginx Proxy Manager for managing hosts
    • TeamSpeak 6, just playing around with the beta for now
    • Apache Subversion for private SVN repos
    • A handmade C# service for storing some MQTT data into a database
    • peaNUT a NUT dashboard for the UPS
    • RustDesk for remote management of desktops

    As for the hardware:

    • A Raspberry pi 4 running Docker containers
    • A Dell Wyse 5070 (16GB) running Proxmox with mainly Alpine Linux VMs

  • The way a reverse proxy works is to literally stand in the middle of a connection, so either side only sees them communicating with the proxy, oblivious to the actual endpoint. The only “solution” to this, though it’s more of a hack really, is to somehow send the original IP as additional data in a way that both sides agree on, e.g. the X-Forwarded-For header as others have mentioned, however, as I’ve said, both sides need to support and aggree with that, so you may have to find a setting/config to enable on the services behind the proxy. Think of it this way, if services blindly trusted that header and you weren’t using a reverse proxy, a bad actor could send a request to your service with that header included thereby spoofing their identity in your logs, therefore, this kind of thing is usually opt-in