Comment

Comment on New(ish) to self-hosting. Question about reverse proxy setup

You don’t need a reverse proxy if your using tailscale. Make the server you exit node and you can access jellyfin and everything else from outside the network.

source

Sort:hotnew top

kn0wmad1c@programming.dev ⁨2⁩ ⁨days⁩ ago
Alright, I’ve configured tailscale as an exit node, but I’m getting an error that might be related to cloudflare? I’m not sure.

Tailscale logs show Received error: fetch control key: 403 Forbidden

Is there a guide for configuring cloudflare for this?

source
- ragingHungryPanda@piefed.keyboardvagabond.com ⁨2⁩ ⁨days⁩ ago
  tailscale is a vpn. you don’t need cloudflare for it. you do need to set up the tail scale container with your credentials from tail scale, which they have guides for. after that, log in on your machine and click the connect toggle and you’re in.
  
  the exit node is if you want to look like you’re at your host computer.
  
  source
  - kn0wmad1c@programming.dev ⁨2⁩ ⁨days⁩ ago
    If you look at the docker compose for the stack I’m using, cloudflare is definitely a part of it:
    
    github.com/geekau/…/docker-compose.yaml
    
    Headscale requires cloudflare, and tailscale requires Headscale.
    
    The documentation for how all of this ties together is really sparse.
    
    source
    ragingHungryPanda@piefed.keyboardvagabond.com ⁨2⁩ ⁨days⁩ ago
    that’s quite a long compose file.
    
    the way that I use cloud flare is with tunnels since my ISP blocks my ports. I have cloudflared running that connects to the cloudflare tunnel, which has a map of domain name to a service name, which is how services are accessed externally.
    
    tailscale connects to tail scales main service and that’s how I access internal systems. at least that’s how I’m running it.
    
    source