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] Modifying prefixes:v4 does not take effect #856

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

Originally created by @lixh00 on GitHub (Nov 21, 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

When I changed prefixes:v4 in the configuration file and restarted headscale, it did not take effect and was still the previous setting。

Expected Behavior

I want to change the value of prefixes:v4 from 100.100.100.0/24 to 100.99.98.0/24

Steps To Reproduce

  1. change config.yaml
  2. restart headscale
  3. restart tailscale

Environment

- OS:alpine latest
- Headscale version: 0.23.0
- Tailscale version: latest

Runtime environment

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

Anything else?

No response

Originally created by @lixh00 on GitHub (Nov 21, 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 When I changed prefixes:v4 in the configuration file and restarted headscale, it did not take effect and was still the previous setting。 ### Expected Behavior I want to change the value of prefixes:v4 from 100.100.100.0/24 to 100.99.98.0/24 ### Steps To Reproduce 1. change config.yaml 2. restart headscale 3. restart tailscale ### Environment ```markdown - OS:alpine latest - Headscale version: 0.23.0 - Tailscale version: latest ``` ### 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:56 +01:00
adam closed this issue 2025-12-29 02:24:56 +01:00
adam commented 2025-12-29 02:24:56 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (Nov 21, 2024):

When you say it does not take effect, do you mean:

New nodes gets addresses from the old prefix?

or

Nodes that is already in the database dont get moved to the new prefix?

@kradalby commented on GitHub (Nov 21, 2024): When you say it does not take effect, do you mean: New nodes gets addresses from the _old_ prefix? or Nodes that is already in the database dont get moved to the _new_ prefix?
adam commented 2025-12-29 02:24:56 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (Dec 5, 2024):

closing due to lack of response

@kradalby commented on GitHub (Dec 5, 2024): closing due to lack of response
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#856
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?