mirror of
https://github.com/juanfont/headscale.git
synced 2024-11-29 18:33:05 +00:00
Update answer based on comment
This commit is contained in:
parent
dbe32829a1
commit
bdf54e802e
1 changed files with 1 additions and 1 deletions
|
@ -53,4 +53,4 @@ For convenience, we also build Docker images with `headscale`. But **please be a
|
||||||
We don't know. We don't use reverse proxies with `headscale` ourselves, so we don't have any experience with them. We have [community documentation](https://headscale.net/reverse-proxy/) on how to configure various reverse proxies, and a dedicated [Discord channel](https://discord.com/channels/896711691637780480/1070619818346164324) where you can ask for help to the community.
|
We don't know. We don't use reverse proxies with `headscale` ourselves, so we don't have any experience with them. We have [community documentation](https://headscale.net/reverse-proxy/) on how to configure various reverse proxies, and a dedicated [Discord channel](https://discord.com/channels/896711691637780480/1070619818346164324) where you can ask for help to the community.
|
||||||
|
|
||||||
## Can I use headscale and tailscale on the same machine?
|
## Can I use headscale and tailscale on the same machine?
|
||||||
Yes, this is no problem. Install Headscale and Tailscale according to the instructions and use `tailscale up --login-server localhost`.
|
Running headscale on a machine that is also in the tailnet might cause problems with routing and MagicDNS - at very least. It should be extremely discouraged.
|
Loading…
Reference in a new issue