5 ms·
author here: I tried port forwarding (because I never did in the past) and couldn't figure how to do it. capture here https://viggy28.dev/article/pain-of-setti
by vira28 5y ago
author here:
I tried port forwarding (because I never did in the past) and couldn't figure how to do it. capture here https://viggy28.dev/article/pain-of-setting-up-port-forwarding-in-xfinity/ https://viggy28.dev/article/pain-of-setting-up-port-forwardi...
I guess Alex's inlets (https://github.com/inlets https://github.com/inlets) might do it too. I would love to hear other alternatives.
- jpillora 5y agoPort forwarding is fairly simple. All routers should support it. Forward port 443 to local-rpi-ip-address:443. Setup caddy/traefik. Create A record to public ip. Enable tls. Enable file hosting. Done: you now have TLS static website without any 3rd parties. That said, cloudflare is super handy for dns, and for proxying specific domains, where you don't want to expose your public ip.
- vira28 5y agoThanks. Xfinity (my ISP) supports only TCP and UDP for Xfi Gateway and not HTTP/HTTPS. The thing which I don't know is how to remove Xfi Gateway and use my own gateway/router.
- Thorrez 5y agoHTTP and HTTPS are layer 7 protocols that both go inside the layer 4 protocol TCP. So port forward TCP and you'll be good. https://en.wikipedia.org/wiki/OSI_model https://en.wikipedia.org/wiki/OSI_model
- vira28 5y agoPerfect. Thanks. That was my doubt. Will try it out.
- WrtCdEvrydy 5y agoYeah, most routers have a predefined list of "Applications" but you can add a custom application with custom port. Back in the day, DynDNS actually allowed the IP to DNS as a free service.
- Thorrez 5y agoOh, I forgot to mention HTTP uses TCP port 80, and HTTPS uses TCP port 443.
- sodality2 5y agoUnfortunately residential networks usually don't have static IP's so the IP changes on reboots. Updating the DNS record every time would probably be a PITA.
- 27100974 5y agoCouple of notes: You can use a DNS updater like this one: https://github.com/timothymiller/cloudflare-ddns https://github.com/timothymiller/cloudflare-ddns The bigger problem would be if your ISP implemented CGNAT.
- ekianjo 5y agoEasily taken care of by duckdns for example
- skeletonjelly 5y agoAnd then you have to hope your ISP doesn't use CGNAT
- sodality2 5y agoThen I can't hook it up to a real domain like google.com, just a subdomain of whatever site is running it.
- anaganisk 5y agoIf you are going to use inlets, which needs a bastion host. I would rather just suggest to jump in and use wireguard VPN instead on a $3.5 vps on linode or lightsail. You get more control over your connection and firewall capabilities than inlets, which locks down premium capabilities. Also Cloudflared tunnel will timeout and turn off your endpoint after a network disconnection. If you notice the systemd default file that comes with it, you will notice it restarts after a day. So you will have significant downtime, if your home network or power goes down.