Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Click "Device View"-"New Device" fastly would occationally end up with adding same machine multi-times and led some error in headscale backend #175

Open
KSroido opened this issue Nov 1, 2024 · 2 comments

Comments

@KSroido
Copy link

KSroido commented Nov 1, 2024

I cannot reproduce again, and I have delete the duplicated server in the website

I thought it will be all fine if I delete them in front end. But actually not

image

image

Nov 01 05:39:01 example.com headscale[697]: 2024-11-01T05:39:01-04:00 ERR Failed to fetch machine from the database with node key: nodekey:5e03

server info

Linux example.com 6.1.0-26-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.112-1 (2024-09-30) x86_64 GNU/Linux

headscale version:

 https://github.com/juanfont/headscale/releases/download/v0.22.3/headscale_0.22.3_linux_amd64.deb

UI version :

https://github.com/gurucomputing/headscale-ui/releases/download/2023.01.30-beta-1/headscale-ui.zip

if any futher info needed, I would be willing to attach

@KSroido KSroido changed the title Click "Device View"-"New Device" fastly would occationally end up with add same machine multi-times and led some error in headscale [BUG] Click "Device View"-"New Device" fastly would occationally end up with add same machine multi-times and led some error in headscale Nov 1, 2024
@KSroido KSroido changed the title [BUG] Click "Device View"-"New Device" fastly would occationally end up with add same machine multi-times and led some error in headscale [BUG] Click "Device View"-"New Device" fastly would occationally end up with adding same machine multi-times and led some error in headscale backend Nov 1, 2024
@routerino
Copy link
Contributor

The UI just utilises the API that headscale exposes. If multiple UI calls are causing unintended behavior in the main application, that needs to be raised in headscale, not here.

There is nothing in headscale ui that shouldn't be able to fixed with a browser refresh.

@KSroido
Copy link
Author

KSroido commented Nov 6, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants