• 1 post
  • 64 comments
Joined 2 years ago
Cake day: April 11th, 2024
  • Install tailscale on your vps. Install tailscale on your router. Use tailscale option (on your router) to expose subnet to the tailnet, the subnet being whatever you’re trying to reverse proxy.

    Replace tailscale with headscale if you’re paranoid, can run headscale on the vps too if you want to. I had this sort of working, my issue i ran into was manually setting up outbound rules for tailscale traffic in pfsense. Manual because the pfsense tailscale plugin didn’t let you specify a headscale server, it only plays with the official tailacale backplane. Installing tailacale on the pfsense command line works and gets around this and your router will show up on your headscale tailnet, but the outbound rules wont automatically be created… so… twas a rabbit hole I didn’t feeling like exploring at the time.

  • I deal with cgnat on my 2 isps at home. Install tailscale on your vps and your router at home and then on your router you can share subnet devices over your tailscale network. Install a reverse proxy on your vps.

    If set up correctly you can route a human readable web address (jellyfin.example.com) to your vps static ip address and then to, for example, a docker container with local address 192.168.100.1:8096, via reverse proxy.

  • I actually did this instead of tailscale first; installing tailscale on a pfsense router was a challenge, iirc i had to find and install the freebsd tailscale pkg from the command line because the plugin doesn’t give the option to connect to a non-tailscale control plane.

    After I did that and connected to my headscale server (on my vps) I could ping pfsense’s local ip over the tailnet, but couldn’t get any traffic out from pfsense. Turns out I had forgotten the pfsense tailscale plugin automatically sets up outbound rules for you.

    That was a rabbit hole I didn’t feeling like falling down, so I turned off headscale and just used tailscale account and the normal pfsense tailscale plugin. But it’s there and it does work fine if I ever wanted to go figure out the outbound traffic rules.

  • I’m actually behind 3 routers and still hosting stuff to the internet. My house is behind cgnat, I have two isp routers, which both connect to a pfsense router (ip of which is in the dmz of each isp router).

    My pfsense router and a free vps hosted at oracle are both connected via tailscale. Pfsense router advertises specific subnet addresses to the tailnet. VPS uses caddy to reverse proxy to those subnet addresses to expose them to the internet.

  • Here. I’m on docker 3.7. I think it’s correct…

    services: elinorr: image: registry.gitlab.com/mwirth001/elinorr:latest container_name: elinorr environment: - PUID=1000 - PGID=1000 - TZ=America/Chicago - SHOW_LIST="design-squad" volumes: - '/mnt/user/appdata_docker/elinorr:/elinorr/config' - '/mnt/user/media/zz_downloads/elinorr_downloads:/elinorr/downloads' restart: unless-stopped