-
## Bug description
I have successfully installed Headscale in a Docker container running on a Proxmox LXC container. I opened ports 80, 443, and 8080 in the Proxmox firewall, forwarding them to por…
-
### What is the issue?
After briefly using `tailscale serve` (but turning it off) I am seeing CPU in excess of 100% on the Linux server (Google GCP virtual machine running Debian)
### Steps to r…
-
### What is the issue?
Recently I started using googlefi. When hot-spotting, the android phone seems like it does not support dual-stack hotspotting.
So for example when I'm on a ipv4 carrier, the…
-
This issue tracks the status of the Tailscale control server.
-
**Is your feature request related to a problem? Please describe.**
We have multiple users who might run ansible configuration playbooks against a given system. Since the state for the playbook is sto…
-
### What is the issue?
tl:dr; disable use as exit node to get dns working..
tailscale as road warrior setup.. just connecting back to the residence when on mobile data..
iOS, 17.4.1 messing w…
-
### What is the issue?
Tested on both fedora 40 and macos sonoma, that when proxying through socks5 using the https_proxy variable, DERP servers are not reachable and shows "not connected to HOME d…
-
### What is the issue?
Stock Ubuntu 24.04 install with the latest tailscale:
```
$ tailscale version
1.66.4
tailscale commit: 067defc641850791142cc83a44dadae29709344a
other commit: 49481b7…
-
I get an error as shown in the screenshot, even though I have opened an external network connection via Keenetic, everything I have done is correct.
![Ekran Görüntüsü (10)](https://github.com/getum…
-
I am currently using the built-in DERP in Headscale and I noticed that the --verify-clients parameter is not configurable. This situation implies that the DERP I am using could be publicly accessible,…