mirror of https://github.com/juanfont/headscale.git synced 2024-11-29 18:33:05 +00:00

Update documentation for 0.23 (#2096 )

* docs/acl: fix path to policy file

* docs/exit-node: fixup for 0.23

* Add newlines between commands to improve readability
* Use nodes instead on name
* Remove query parameter from link to Tailscale docs

* docs/remote-cli: fix formatting

* Indent blocks below line numbers to restore numbering
* Fix minor typos

* docs/reverse-proxy: remove version information

* Websocket support is always required now
* s/see detail/see details

* docs/exit-node: add warning to manual documentation

* Replace the warning section with a warning admonition
* Fix TODO link back to the regular linux documentation

* docs/openbsd: fix typos

* the database is created on-the-fly

* docs/sealos: fix typos

* docs/container: various fixes

* Remove a stray sentence
* Remove "headscale" before serve
* Indent line continuation
* Replace hardcoded 0.22 with <VERSION>
* Fix path in debug image to /ko-app/headscale

Fixes: #1822

aa

2024-09-03 11:04:20 +00:00

3.3 KiB

Raw Blame History

Controlling `headscale` with remote CLI

Prerequisite

A workstation to run headscale (could be Linux, macOS, other supported platforms)
A headscale server (version 0.13.0 or newer)
Access to create API keys (local access to the headscale server)
headscale must be served over TLS/HTTPS
- Remote access does not support unencrypted traffic.
Port 50443 must be open in the firewall (or port overridden by grpc_listen_addr option)

Goal

This documentation has the goal of showing a user how-to set control a headscale instance from a remote machine with the headscale command line binary.

Create an API key

We need to create an API key to authenticate our remote headscale when using it from our workstation.

To create a API key, log into your headscale server and generate a key:

headscale apikeys create --expiration 90d

Copy the output of the command and save it for later. Please note that you can not retrieve a key again, if the key is lost, expire the old one, and create a new key.

To list the keys currently assosicated with the server:

headscale apikeys list

and to expire a key:

headscale apikeys expire --prefix "<PREFIX>"

Download and configure `headscale`

Download the latest headscale binary from GitHub's release page:
Put the binary somewhere in your PATH, e.g. /usr/local/bin/headscale
Make headscale executable:
```
chmod +x /usr/local/bin/headscale
```
Configure the CLI through environment variables
```
export HEADSCALE_CLI_ADDRESS="<HEADSCALE ADDRESS>:<PORT>"
export HEADSCALE_CLI_API_KEY="<API KEY FROM PREVIOUS STAGE>"
```
for example:
```
export HEADSCALE_CLI_ADDRESS="headscale.example.com:50443"
export HEADSCALE_CLI_API_KEY="abcde12345"
```
This will tell the headscale binary to connect to a remote instance, instead of looking for a local instance (which is what it does on the server).

The API key is needed to make sure that you are allowed to access the server. The key is not needed when running directly on the server, as the connection is local.
Test the connection

Let us run the headscale command to verify that we can connect by listing our nodes:
```
headscale nodes list
```
You should now be able to see a list of your nodes from your workstation, and you can now control the headscale server from your workstation.

Behind a proxy

It is possible to run the gRPC remote endpoint behind a reverse proxy, like Nginx, and have it run on the same port as headscale.

While this is not a supported feature, an example on how this can be set up on NixOS is shown here.

Troubleshooting

Checklist:

Make sure you have the same headscale version on your server and workstation
Make sure you use version 0.13.0 or newer.
Verify that your TLS certificate is valid and trusted
- If you do not have access to a trusted certificate (e.g. from Let's Encrypt), add your self signed certificate to the trust store of your OS or
- Set HEADSCALE_CLI_INSECURE to 0 in your environment

3.3 KiB Raw Blame History

Controlling headscale with remote CLI