Skip to content

Latest commit

Β 

History

History
63 lines (43 loc) Β· 2.46 KB

File metadata and controls

63 lines (43 loc) Β· 2.46 KB

ProxyT

A lightweight, preconfigured proxy for the Tailscale control plane that enables Tailscale access in the event the Tailscale control plane is being blocked.

Deploy on Railway

Overview

Tailscale connections between peers are incredible resiliant. If you are authenticated to Tailscale, it will endeavour to use all mechanisms at its disposal to forge connections it needs between clients.

However, some networks block the Tailscale control plane (ie, the tailscale.com domain) either via DNS blackholing or SNI interception.

Proxyt allows you to host a proxy to the Tailscale control plane which can be used by clients. You can host Proxyt anywhere, register your own domain or even expose it via Funnel giving you a reliable way of accessing the Tailscale control plane to authenticate clients.

πŸš€ Quick Start

Docker

docker run -d -p 80:80 -p 443:443 -v proxyt-certs:/certs \
  ghcr.io/jaxxstorm/proxyt:latest \
  serve --domain proxy.example.com --email admin@example.com --cert-dir /certs

Kubernetes (Helm)

helm install proxyt oci://ghcr.io/jaxxstorm/charts/proxyt \
  --set proxyt.domain=proxy.example.com \
  --set proxyt.email=admin@example.com

Configure Tailscale Client

tailscale login --login-server https://proxy.example.com

πŸ“– Documentation

Full documentation: proxyt.io

Quick Links

  • πŸ“¦ Installation - Install ProxyT on your platform
  • βš™οΈ Configuration - Configure ProxyT with flags or environment variables
  • πŸš€ Deployment - Deploy to Railway, Docker, or your own server
  • πŸ”§ Tailscale Setup - Configure Tailscale clients to use ProxyT
  • πŸ› οΈ Troubleshooting - Common issues and solutions
  • πŸ”’ Security - Security considerations and best practices
  • πŸ—οΈ Architecture - How ProxyT works under the hood

πŸ’‘ Browsing on GitHub? The documentation source files are in the docs/ directory

Contributing

  1. Fork the repository
  2. Create a feature branch
  3. Make your changes
  4. Add tests if applicable
  5. Submit a pull request

License

See LICENSE for details.