Hi,
The crash happens because the container runs headscale without the serve subcommand — it prints the help text and exits immediately, causing the restart loop.
To fix this, go to your Headscale service Settings and set the Custom Start Command to:
headscale serve
Then restart the service. It should start normally after that.
Since this template was created by another user, we're unable to fix it on the template side. If you plan to use Headscale long-term, you can create your own template with the correct start command configured, so future deployments work out of the box.
If you have any other questions, please create a new post. Thanks!