starred/headscale
1
0
Fork 0
mirror of https://github.com/juanfont/headscale.git synced 2026-01-11 20:00:28 +01:00
Code Issues 98 Packages Projects Releases 10 Wiki Activity

[Bug] 0.23.0 There seems to be some issues with the configuration #849

New Issue
Closed
opened 2025-12-29 02:24:48 +01:00 by adam · 0 comments
adam commented 2025-12-29 02:24:48 +01:00
Owner
Copy Link

Originally created by @wszgrcy on GitHub (Nov 4, 2024).

Is this a support request?

  • This is not a support request

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

version error

I install 0.23.0 bug version displayv0.23.0-alpha1

ubuntu@VM-24-12-ubuntu:~$ sudo dpkg -i ./headscale_0.23.0_linux_amd64.deb 
Selecting previously unselected package headscale.
(Reading database ... 125304 files and directories currently installed.)
Preparing to unpack .../headscale_0.23.0_linux_amd64.deb ...
Unpacking headscale (0.23.0) ...
Setting up headscale (0.23.0) ...
Sudo permissions detected
Found headscale /usr/bin/headscale
PostInstall: Adding headscale user headscale
useradd: user 'headscale' already exists
PostInstall: Adding headscale group headscale
groupadd: group 'headscale' already exists
PostInstall: Adding headscale user headscale to group headscale
PostInstall: Creating headscale run directory 
PostInstall: Modifying group ownership of headscale run directory 
----------------------------------------------------------------------
 headscale package has been successfully installed.

 Please follow the next steps to start the software:

    sudo systemctl enable headscale
    sudo systemctl start headscale

 Configuration settings can be adjusted here:
    /etc/headscale/config.yaml

----------------------------------------------------------------------
ubuntu@VM-24-12-ubuntu:~$ sudo headscale version
v0.23.0-alpha1

config db type error

I use 0.23.0 pkg with default config ,but throw error
Error initializing error="unsupported DB"
But miraculously, using my previous (0.22) configuration was normal

config ip prefix

  • 0.23.0 use prefixes(default config) but throw warning as follow
    WRN 'ip_prefixes' not configured, falling back to default: [100.64.0.0/10]

Expected Behavior

I want to know if it's a packaging issue, if I have installation problems or if some of the code hasn't been modified?

Steps To Reproduce

  1. sudo dpkg -i ./headscale_0.23.0_linux_amd64.deb
  2. sudo systemctl enable headscale
    sudo systemctl start headscale
  3. sudo journalctl -u headscale --reverse

Environment

- OS: Linux VM-24-12-ubuntu 5.15.0-88-generic #98-Ubuntu SMP Mon Oct 2 15:18:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
- Headscale version: 0.23.0
- Tailscale version: none

Runtime environment

  • Headscale is behind a (reverse) proxy
  • Headscale runs in a container

Anything else?

No response

Originally created by @wszgrcy on GitHub (Nov 4, 2024). ### Is this a support request? - [X] This is not a support request ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current Behavior ## version error I install 0.23.0 bug version display`v0.23.0-alpha1` ``` ubuntu@VM-24-12-ubuntu:~$ sudo dpkg -i ./headscale_0.23.0_linux_amd64.deb Selecting previously unselected package headscale. (Reading database ... 125304 files and directories currently installed.) Preparing to unpack .../headscale_0.23.0_linux_amd64.deb ... Unpacking headscale (0.23.0) ... Setting up headscale (0.23.0) ... Sudo permissions detected Found headscale /usr/bin/headscale PostInstall: Adding headscale user headscale useradd: user 'headscale' already exists PostInstall: Adding headscale group headscale groupadd: group 'headscale' already exists PostInstall: Adding headscale user headscale to group headscale PostInstall: Creating headscale run directory PostInstall: Modifying group ownership of headscale run directory ---------------------------------------------------------------------- headscale package has been successfully installed. Please follow the next steps to start the software: sudo systemctl enable headscale sudo systemctl start headscale Configuration settings can be adjusted here: /etc/headscale/config.yaml ---------------------------------------------------------------------- ubuntu@VM-24-12-ubuntu:~$ sudo headscale version v0.23.0-alpha1 ``` ### config db type error I use `0.23.0` pkg with default config ,but throw error `Error initializing error="unsupported DB"` But miraculously, using my previous (0.22) configuration was normal ### config ip prefix - `0.23.0` use `prefixes`(default config) but throw warning as follow `WRN 'ip_prefixes' not configured, falling back to default: [100.64.0.0/10]` ### Expected Behavior I want to know if it's a packaging issue, if I have installation problems or if some of the code hasn't been modified? ### Steps To Reproduce 1. sudo dpkg -i ./headscale_0.23.0_linux_amd64.deb 2. sudo systemctl enable headscale sudo systemctl start headscale 3. sudo journalctl -u headscale --reverse ### Environment ```markdown - OS: Linux VM-24-12-ubuntu 5.15.0-88-generic #98-Ubuntu SMP Mon Oct 2 15:18:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux - Headscale version: 0.23.0 - Tailscale version: none ``` ### Runtime environment - [ ] Headscale is behind a (reverse) proxy - [ ] Headscale runs in a container ### Anything else? _No response_
adam added the bug label 2025-12-29 02:24:48 +01:00
adam closed this issue 2025-12-29 02:24:48 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
CLI
DERP
DNS
Nix
OIDC
SSH
bug
database
documentation
duplicate
enhancement
faq
good first issue
grants
help wanted
might-come
needs design doc
needs investigation
no-stale-bot
out of scope
performance
policy 📝
pull-request
Mirrored from GitHub Pull Request
 question
regression
routes
stale
tags
tailscale-feature-gap
well described ❤️
wontfix
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#849
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?