• 0 Posts
  • 9 Comments
Joined 2 years ago
cake
Cake day: February 29th, 2024

help-circle


  • Your existing Apache setup can be used as a reverse proxy. The idea is, you setup those other services (eg, next cloud or radicale) on other systems, or on the same system with different ports. Then when you access some URL, eg https://yourhomenetwork.com/radicale, Apache acts as an intermediary and returns the service at http://127.0.0.1:8080/radicale. No additional open ports needed. No additional certificates needed.

    Apache can even be configured to respond to requests differently if they’re coming from the internet or from wireguard. Say if you wanted to deny all traffic from the internet and only access it from your VPN, or if you wanted to conditionally apply a password.

    You can also use Apache to host multiple domain names, or sub domains, from the same IP address and ports (the feature is called “vhost”). That may require multiple SSL certificates though. (EDIT: If youre using a wildcard certificate, you can host multiple sub domains from that one certificate)

    You’ve got options though, and you don’t need to break what you’ve already got :)






  • Shit, ask4? I think they were the isp when I was at uni about a decade ago. I’m sorry to hear they’re still kicking.

    If it’s still the same as back then, all the dorms are essentially on the same lan and they’re using Mac filtering at the gateway. Since this was before Https became ubiquitous this meant you could sniff other people’s http requests.

    What you do (what we did) was sign up with one device and setup a proxy on it. I think we used squid-cache. But anything that will masquerade the traffic as coming from that one device should do the trick.