SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-08-04 19:55:09 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

Error on Debian 12 new install (0.28.6) #1085

New Issue
Closed
opened 2025-11-20 05:23:45 -05:00 by saavagebueno · 17 comments
saavagebueno commented 2025-11-20 05:23:45 -05:00
Owner
Copy Link

Originally created by @tylerbean on GitHub (Jul 24, 2024).

Describe the problem

Fresh install on Debian 12 (Proxmox, specifically; all packages up-to-date) fails to connect with unclear error:

Error: waiting sso login failed with: rpc error: code = Unknown desc = string field contains invalid UTF-8

To Reproduce

  • Install Netbird, using script or manual steps for Debian
  • run netbird up
  • Click login link
  • Confirm in browser
  • Throw keyboard

Note: Same outcome using setup-key

Are you using NetBird Cloud?

Yes

NetBird version

0.28.6

NetBird status -d output:

If applicable, add the `netbird status -d' command output.

Screenshots

image
image

Additional context

I have a second Proxmox host, running the same OS and kernel versions, where this worked flawlessly. I have gutted it from the system, started from scratch, and seen the exact same result.

Originally created by @tylerbean on GitHub (Jul 24, 2024). **Describe the problem** Fresh install on Debian 12 (Proxmox, specifically; all packages up-to-date) fails to connect with unclear error: Error: waiting sso login failed with: rpc error: code = Unknown desc = string field contains invalid UTF-8 **To Reproduce** - Install Netbird, using script or manual steps for Debian - run `netbird up` - Click login link - Confirm in browser - Throw keyboard Note: Same outcome using setup-key **Are you using NetBird Cloud?** Yes **NetBird version** 0.28.6 **NetBird status -d output:** If applicable, add the `netbird status -d' command output. **Screenshots** ![image](https://github.com/user-attachments/assets/709e3cbf-8229-4790-a5ff-85557e3cde4f) ![image](https://github.com/user-attachments/assets/485dd7d9-c33d-464e-a175-049929e08c83) **Additional context** I have a second Proxmox host, running the same OS and kernel versions, where this worked flawlessly. I have gutted it from the system, started from scratch, and seen the exact same result.
saavagebueno added the clientwaiting-feedbackagent labels 2025-11-20 05:23:45 -05:00
saavagebueno commented 2025-11-20 05:23:45 -05:00
Author
Owner
Copy Link

@tylerbean commented on GitHub (Jul 24, 2024):

client.log

2024-07-24T13:25:37-05:00 INFO client/cmd/service_controller.go:24: starting Netbird service
2024-07-24T13:25:37-05:00 INFO client/internal/config.go:147: generating new config /etc/netbird/config.json
2024-07-24T13:25:37-05:00 INFO client/internal/config.go:209: using default Management URL https://api.netbird.io:443
2024-07-24T13:25:37-05:00 INFO client/internal/config.go:233: using default Admin URL https://api.netbird.io:443
2024-07-24T13:25:37-05:00 INFO client/internal/config.go:251: generated new Wireguard key
2024-07-24T13:25:37-05:00 INFO client/internal/config.go:257: generated new SSH key
2024-07-24T13:25:37-05:00 INFO client/internal/config.go:273: using default Wireguard port 51820
2024-07-24T13:25:37-05:00 INFO client/internal/config.go:284: using default Wireguard interface wt0
2024-07-24T13:25:37-05:00 INFO client/internal/config.go:337: filling in interface blacklist with defaults: [ wt0 wt utun tun0 zt ZeroTier wg ts Tailscale tailscale docker veth br- lo ]
2024-07-24T13:25:37-05:00 INFO client/internal/config.go:383: using default DNS route interval 1m0s
2024-07-24T13:25:37-05:00 INFO client/cmd/service_controller.go:64: started daemon server: /var/run/netbird.sock
2024-07-24T13:25:47-05:00 ERRO encryption/message.go:13: failed marshalling message string field contains invalid UTF-8
2024-07-24T13:25:47-05:00 ERRO management/client/grpc.go:322: failed to encrypt message: string field contains invalid UTF-8
2024-07-24T13:25:47-05:00 ERRO client/server/server.go:262: failed login: string field contains invalid UTF-8
2024-07-24T13:25:58-05:00 ERRO encryption/message.go:13: failed marshalling message string field contains invalid UTF-8
2024-07-24T13:25:58-05:00 ERRO management/client/grpc.go:322: failed to encrypt message: string field contains invalid UTF-8
2024-07-24T13:25:58-05:00 ERRO client/server/server.go:262: failed login: string field contains invalid UTF-8
2024-07-24T13:41:28-05:00 ERRO encryption/message.go:13: failed marshalling message string field contains invalid UTF-8
2024-07-24T13:41:28-05:00 ERRO management/client/grpc.go:322: failed to encrypt message: string field contains invalid UTF-8
2024-07-24T13:41:28-05:00 ERRO client/server/server.go:262: failed login: string field contains invalid UTF-8
2024-07-24T13:41:28-05:00 WARN client/server/server.go:419: canceling previous waiting execution
2024-07-24T13:41:40-05:00 ERRO encryption/message.go:13: failed marshalling message string field contains invalid UTF-8
2024-07-24T13:41:40-05:00 ERRO management/client/grpc.go:322: failed to encrypt message: string field contains invalid UTF-8
2024-07-24T13:41:40-05:00 ERRO client/server/server.go:262: failed login: string field contains invalid UTF-8
2024-07-24T13:42:05-05:00 ERRO encryption/message.go:13: failed marshalling message string field contains invalid UTF-8
2024-07-24T13:42:05-05:00 ERRO management/client/grpc.go:322: failed to encrypt message: string field contains invalid UTF-8
2024-07-24T13:42:05-05:00 ERRO client/server/server.go:262: failed login: string field contains invalid UTF-8
2024-07-24T13:42:06-05:00 WARN client/server/server.go:419: canceling previous waiting execution
2024-07-24T13:42:27-05:00 ERRO encryption/message.go:13: failed marshalling message string field contains invalid UTF-8
2024-07-24T13:42:27-05:00 ERRO management/client/grpc.go:322: failed to encrypt message: string field contains invalid UTF-8
2024-07-24T13:42:27-05:00 ERRO client/server/server.go:262: failed login: string field contains invalid UTF-8
@tylerbean commented on GitHub (Jul 24, 2024): client.log ``` 2024-07-24T13:25:37-05:00 INFO client/cmd/service_controller.go:24: starting Netbird service 2024-07-24T13:25:37-05:00 INFO client/internal/config.go:147: generating new config /etc/netbird/config.json 2024-07-24T13:25:37-05:00 INFO client/internal/config.go:209: using default Management URL https://api.netbird.io:443 2024-07-24T13:25:37-05:00 INFO client/internal/config.go:233: using default Admin URL https://api.netbird.io:443 2024-07-24T13:25:37-05:00 INFO client/internal/config.go:251: generated new Wireguard key 2024-07-24T13:25:37-05:00 INFO client/internal/config.go:257: generated new SSH key 2024-07-24T13:25:37-05:00 INFO client/internal/config.go:273: using default Wireguard port 51820 2024-07-24T13:25:37-05:00 INFO client/internal/config.go:284: using default Wireguard interface wt0 2024-07-24T13:25:37-05:00 INFO client/internal/config.go:337: filling in interface blacklist with defaults: [ wt0 wt utun tun0 zt ZeroTier wg ts Tailscale tailscale docker veth br- lo ] 2024-07-24T13:25:37-05:00 INFO client/internal/config.go:383: using default DNS route interval 1m0s 2024-07-24T13:25:37-05:00 INFO client/cmd/service_controller.go:64: started daemon server: /var/run/netbird.sock 2024-07-24T13:25:47-05:00 ERRO encryption/message.go:13: failed marshalling message string field contains invalid UTF-8 2024-07-24T13:25:47-05:00 ERRO management/client/grpc.go:322: failed to encrypt message: string field contains invalid UTF-8 2024-07-24T13:25:47-05:00 ERRO client/server/server.go:262: failed login: string field contains invalid UTF-8 2024-07-24T13:25:58-05:00 ERRO encryption/message.go:13: failed marshalling message string field contains invalid UTF-8 2024-07-24T13:25:58-05:00 ERRO management/client/grpc.go:322: failed to encrypt message: string field contains invalid UTF-8 2024-07-24T13:25:58-05:00 ERRO client/server/server.go:262: failed login: string field contains invalid UTF-8 2024-07-24T13:41:28-05:00 ERRO encryption/message.go:13: failed marshalling message string field contains invalid UTF-8 2024-07-24T13:41:28-05:00 ERRO management/client/grpc.go:322: failed to encrypt message: string field contains invalid UTF-8 2024-07-24T13:41:28-05:00 ERRO client/server/server.go:262: failed login: string field contains invalid UTF-8 2024-07-24T13:41:28-05:00 WARN client/server/server.go:419: canceling previous waiting execution 2024-07-24T13:41:40-05:00 ERRO encryption/message.go:13: failed marshalling message string field contains invalid UTF-8 2024-07-24T13:41:40-05:00 ERRO management/client/grpc.go:322: failed to encrypt message: string field contains invalid UTF-8 2024-07-24T13:41:40-05:00 ERRO client/server/server.go:262: failed login: string field contains invalid UTF-8 2024-07-24T13:42:05-05:00 ERRO encryption/message.go:13: failed marshalling message string field contains invalid UTF-8 2024-07-24T13:42:05-05:00 ERRO management/client/grpc.go:322: failed to encrypt message: string field contains invalid UTF-8 2024-07-24T13:42:05-05:00 ERRO client/server/server.go:262: failed login: string field contains invalid UTF-8 2024-07-24T13:42:06-05:00 WARN client/server/server.go:419: canceling previous waiting execution 2024-07-24T13:42:27-05:00 ERRO encryption/message.go:13: failed marshalling message string field contains invalid UTF-8 2024-07-24T13:42:27-05:00 ERRO management/client/grpc.go:322: failed to encrypt message: string field contains invalid UTF-8 2024-07-24T13:42:27-05:00 ERRO client/server/server.go:262: failed login: string field contains invalid UTF-8 ```
saavagebueno commented 2025-11-20 05:23:46 -05:00
Author
Owner
Copy Link

@dd0ke commented on GitHub (Jul 30, 2024):

Same here. Using:
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
Exact same workflow.

@dd0ke commented on GitHub (Jul 30, 2024): Same here. Using: PRETTY_NAME="Debian GNU/Linux 12 (bookworm)" Exact same workflow.
saavagebueno commented 2025-11-20 05:23:46 -05:00
Author
Owner
Copy Link

@dd0ke commented on GitHub (Jul 30, 2024):

With a --setup-key:
2024-07-30T13:24:24-04:00 WARN client/cmd/root.go:234: retrying Login to the Management service in 1.015879675s due to error rpc error: code = Unknown desc = string field contains invalid UTF-8
2024-07-30T13:24:26-04:00 WARN client/cmd/root.go:234: retrying Login to the Management service in 811.919366ms due to error rpc error: code = Unknown desc = string field contains invalid UTF-8
2024-07-30T13:24:29-04:00 WARN client/cmd/root.go:234: retrying Login to the Management service in 1.149214279s due to error rpc error: code = Unknown desc = string field contains invalid UTF-8
2024-07-30T13:24:31-04:00 WARN client/cmd/root.go:234: retrying Login to the Management service in 4.251581099s due to error rpc error: code = Unknown desc = string field contains invalid UTF-8
2024-07-30T13:24:37-04:00 WARN client/cmd/root.go:234: retrying Login to the Management service in 4.782064415s due to error rpc error: code = Unknown desc = string field contains invalid UTF-8
Error: login backoff cycle failed: rpc error: code = Unknown desc = string field contains invalid UTF-8

@dd0ke commented on GitHub (Jul 30, 2024): With a --setup-key: 2024-07-30T13:24:24-04:00 WARN client/cmd/root.go:234: retrying Login to the Management service in 1.015879675s due to error rpc error: code = Unknown desc = string field contains invalid UTF-8 2024-07-30T13:24:26-04:00 WARN client/cmd/root.go:234: retrying Login to the Management service in 811.919366ms due to error rpc error: code = Unknown desc = string field contains invalid UTF-8 2024-07-30T13:24:29-04:00 WARN client/cmd/root.go:234: retrying Login to the Management service in 1.149214279s due to error rpc error: code = Unknown desc = string field contains invalid UTF-8 2024-07-30T13:24:31-04:00 WARN client/cmd/root.go:234: retrying Login to the Management service in 4.251581099s due to error rpc error: code = Unknown desc = string field contains invalid UTF-8 2024-07-30T13:24:37-04:00 WARN client/cmd/root.go:234: retrying Login to the Management service in 4.782064415s due to error rpc error: code = Unknown desc = string field contains invalid UTF-8 Error: login backoff cycle failed: rpc error: code = Unknown desc = string field contains invalid UTF-8
saavagebueno commented 2025-11-20 05:23:46 -05:00
Author
Owner
Copy Link

@pappz commented on GitHub (Jul 31, 2024):

Could you send to me the output of the dmidecode -t system command?

@pappz commented on GitHub (Jul 31, 2024): Could you send to me the output of the `dmidecode -t system` command?
saavagebueno commented 2025-11-20 05:23:46 -05:00
Author
Owner
Copy Link

@dd0ke commented on GitHub (Jul 31, 2024):

I imagine you meant posting it here? Otherwise let me know.
Here it goes:

dmidecode 3.4

Getting SMBIOS data from sysfs.
SMBIOS 2.7 present.

Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: PC Engines
Product Name: PC Engines apu4
Version: 1.0
Serial Number: ..........
UUID: Not Settable
Wake-up Type: Reserved
SKU Number: 4 GB
Family: Not Specified

Handle 0x0005, DMI type 32, 11 bytes
System Boot Information
Status: No errors detected

On Jul 31, 2024, at 10:58 AM, Zoltan Papp @.***> wrote:

Could you send to me the output of the dmidecode -t system command?

—
Reply to this email directly, view it on GitHub https://github.com/netbirdio/netbird/issues/2319#issuecomment-2260005609, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF7LKBMLK4ACWG7FYSIEP7DZPCRK3AVCNFSM6AAAAABLNB3UACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRQGAYDKNRQHE.
You are receiving this because you commented.

@dd0ke commented on GitHub (Jul 31, 2024): I imagine you meant posting it here? Otherwise let me know. Here it goes: # dmidecode 3.4 Getting SMBIOS data from sysfs. SMBIOS 2.7 present. Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: PC Engines Product Name: PC Engines apu4 Version: 1.0 Serial Number: .......... UUID: Not Settable Wake-up Type: Reserved SKU Number: 4 GB Family: Not Specified Handle 0x0005, DMI type 32, 11 bytes System Boot Information Status: No errors detected > On Jul 31, 2024, at 10:58 AM, Zoltan Papp ***@***.***> wrote: > > > Could you send to me the output of the dmidecode -t system command? > > — > Reply to this email directly, view it on GitHub <https://github.com/netbirdio/netbird/issues/2319#issuecomment-2260005609>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AF7LKBMLK4ACWG7FYSIEP7DZPCRK3AVCNFSM6AAAAABLNB3UACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRQGAYDKNRQHE>. > You are receiving this because you commented. >
saavagebueno commented 2025-11-20 05:23:46 -05:00
Author
Owner
Copy Link

@pappz commented on GitHub (Jul 31, 2024):

Yes, thank you. I was not sure that it has any data that is sensitive for you.
I am curious about the dmidecode -t baseboard too. Maybe the board.serial contains invalid characters.

@pappz commented on GitHub (Jul 31, 2024): Yes, thank you. I was not sure that it has any data that is sensitive for you. I am curious about the `dmidecode -t baseboard` too. Maybe the board.serial contains invalid characters.
saavagebueno commented 2025-11-20 05:23:46 -05:00
Author
Owner
Copy Link

@dd0ke commented on GitHub (Jul 31, 2024):

Hi there, and thanks!

Here is the output.

dmidecode 3.4

Getting SMBIOS data from sysfs.
SMBIOS 2.7 present.

Handle 0x0002, DMI type 2, 8 bytes
Base Board Information
Manufacturer: PC Engines
Product Name: PC Engines apu4
Version: 1.0
Serial Number: ..........

No special characters detected here.
Others here could try on other Debian 12 based systems to see if it is generalized.

On Jul 31, 2024, at 12:18 PM, Zoltan Papp @.***> wrote:

Yes, thank you. I was not sure that it has any data that is sensitive for you.
I am curious about the dmidecode -t baseboard too. Maybe the board.serial contains invalid characters.

—
Reply to this email directly, view it on GitHub https://github.com/netbirdio/netbird/issues/2319#issuecomment-2260171905, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF7LKBNXTHTXOKFSQOD77JLZPC2WPAVCNFSM6AAAAABLNB3UACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRQGE3TCOJQGU.
You are receiving this because you commented.

@dd0ke commented on GitHub (Jul 31, 2024): Hi there, and thanks! Here is the output. # dmidecode 3.4 Getting SMBIOS data from sysfs. SMBIOS 2.7 present. Handle 0x0002, DMI type 2, 8 bytes Base Board Information Manufacturer: PC Engines Product Name: PC Engines apu4 Version: 1.0 Serial Number: .......... No special characters detected here. Others here could try on other Debian 12 based systems to see if it is generalized. > On Jul 31, 2024, at 12:18 PM, Zoltan Papp ***@***.***> wrote: > > > Yes, thank you. I was not sure that it has any data that is sensitive for you. > I am curious about the dmidecode -t baseboard too. Maybe the board.serial contains invalid characters. > > — > Reply to this email directly, view it on GitHub <https://github.com/netbirdio/netbird/issues/2319#issuecomment-2260171905>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AF7LKBNXTHTXOKFSQOD77JLZPC2WPAVCNFSM6AAAAABLNB3UACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRQGE3TCOJQGU>. > You are receiving this because you commented. >
saavagebueno commented 2025-11-20 05:23:46 -05:00
Author
Owner
Copy Link

@pappz commented on GitHub (Jul 31, 2024):

I think under the hood the Serial Number: .......... is an invalid character line.
In this PR I tried to fix it.

@pappz commented on GitHub (Jul 31, 2024): I think under the hood the **Serial Number: ..........** is an invalid character line. In [this](https://github.com/netbirdio/netbird/pull/2360) PR I tried to fix it.
saavagebueno commented 2025-11-20 05:23:47 -05:00
Author
Owner
Copy Link

@pappz commented on GitHub (Jul 31, 2024):

@ekavun
Could you do a test with the fixed version? You can download the NetBird agent binary from this link:
If you stop the daemon you can start the patched version from a console with this command:
sudo ./netbird up -F -l debug

@pappz commented on GitHub (Jul 31, 2024): @ekavun Could you do a test with the fixed version? You can download the NetBird agent binary from [this](https://github.com/netbirdio/netbird/actions/runs/10181214766/artifacts/1760256992 ) link: If you stop the daemon you can start the patched version from a console with this command: `sudo ./netbird up -F -l debug`
saavagebueno commented 2025-11-20 05:23:47 -05:00
Author
Owner
Copy Link

@dd0ke commented on GitHub (Jul 31, 2024):

Thanks!
If I run it in foreground with your debug log, it works. If I run it as a daemon, it gives me the same errors.
In daemon, I am asked to login and the errors continue. In foreground, I’m logged in automatically with netbird up.

This only works with your patch, with the limitations I mentioned.

Sorry for not being more thorough, rushing this to you on spotty connection. Happy to test further later. Thanks for the work!

On Jul 31, 2024, at 3:50 PM, Zoltan Papp @.***> wrote:

@ekavun https://github.com/ekavun
Could you do a test with the fixed version? You can download the NetBird agent binary from this https://github.com/netbirdio/netbird/actions/runs/10181214766/artifacts/1760256992 link:
If you stop the daemon you can start the patched version from a console with this command:
sudo ./netbird up -F -l debug

—
Reply to this email directly, view it on GitHub https://github.com/netbirdio/netbird/issues/2319#issuecomment-2260574479, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF7LKBOINERDUNTENERB33LZPDTQZAVCNFSM6AAAAABLNB3UACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRQGU3TINBXHE.
You are receiving this because you were mentioned.

@dd0ke commented on GitHub (Jul 31, 2024): Thanks! If I run it in foreground with your debug log, it works. If I run it as a daemon, it gives me the same errors. In daemon, I am asked to login and the errors continue. In foreground, I’m logged in automatically with netbird up. This only works with your patch, with the limitations I mentioned. Sorry for not being more thorough, rushing this to you on spotty connection. Happy to test further later. Thanks for the work! > On Jul 31, 2024, at 3:50 PM, Zoltan Papp ***@***.***> wrote: > > > @ekavun <https://github.com/ekavun> > Could you do a test with the fixed version? You can download the NetBird agent binary from this <https://github.com/netbirdio/netbird/actions/runs/10181214766/artifacts/1760256992> link: > If you stop the daemon you can start the patched version from a console with this command: > sudo ./netbird up -F -l debug > > — > Reply to this email directly, view it on GitHub <https://github.com/netbirdio/netbird/issues/2319#issuecomment-2260574479>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AF7LKBOINERDUNTENERB33LZPDTQZAVCNFSM6AAAAABLNB3UACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRQGU3TINBXHE>. > You are receiving this because you were mentioned. >
saavagebueno commented 2025-11-20 05:23:47 -05:00
Author
Owner
Copy Link

@pappz commented on GitHub (Jul 31, 2024):

At the first look should not be different in daemon and foreground mode. Could you double check you run the proper binary in daemon mode?
In this PR I extended the error message with extra information:
failed marshalling message string field contains invalid UTF-8, meta:{hostname:"...

@pappz commented on GitHub (Jul 31, 2024): At the first look should not be different in daemon and foreground mode. Could you double check you run the proper binary in daemon mode? In this PR I extended the error message with extra information: `failed marshalling message string field contains invalid UTF-8, meta:{hostname:"...`
saavagebueno commented 2025-11-20 05:23:47 -05:00
Author
Owner
Copy Link

@dd0ke commented on GitHub (Jul 31, 2024):

I am sure I ran the binary you provided for both modes.
Just tested again to be sure. With a simple ./netbird up, after the login messages, the error is:
Error: waiting sso login failed with: rpc error: code = Unknown desc = string field contains invalid UTF-8

A ./netbird up -F -l debug works fine, without login step.

On Jul 31, 2024, at 4:25 PM, Zoltan Papp @.***> wrote:

At the first look should not be different in daemon and foreground mode. Could you double check you run the proper binary in daemon mode?
In this PR I extended the error message with extra information:
failed marshalling message string field contains invalid UTF-8, meta:{hostname:"...

—
Reply to this email directly, view it on GitHub https://github.com/netbirdio/netbird/issues/2319#issuecomment-2260651025, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF7LKBMATAMRYR7GD6SM2PTZPDXUJAVCNFSM6AAAAABLNB3UACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRQGY2TCMBSGU.
You are receiving this because you were mentioned.

@dd0ke commented on GitHub (Jul 31, 2024): I am sure I ran the binary you provided for both modes. Just tested again to be sure. With a simple ./netbird up, after the login messages, the error is: Error: waiting sso login failed with: rpc error: code = Unknown desc = string field contains invalid UTF-8 A ./netbird up -F -l debug works fine, without login step. > On Jul 31, 2024, at 4:25 PM, Zoltan Papp ***@***.***> wrote: > > > At the first look should not be different in daemon and foreground mode. Could you double check you run the proper binary in daemon mode? > In this PR I extended the error message with extra information: > failed marshalling message string field contains invalid UTF-8, meta:{hostname:"... > > — > Reply to this email directly, view it on GitHub <https://github.com/netbirdio/netbird/issues/2319#issuecomment-2260651025>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AF7LKBMATAMRYR7GD6SM2PTZPDXUJAVCNFSM6AAAAABLNB3UACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRQGY2TCMBSGU>. > You are receiving this because you were mentioned. >
saavagebueno commented 2025-11-20 05:23:47 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Jul 31, 2024):

@ekavun this is because the daemon is running with a different binary.

What you can do to replace it:

sudo netbird service stop
sudo mv ./netbird $(which netbird)
sudo netbird start
netbird up
@mlsmaycon commented on GitHub (Jul 31, 2024): @ekavun this is because the daemon is running with a different binary. What you can do to replace it: ```shell sudo netbird service stop sudo mv ./netbird $(which netbird) sudo netbird start netbird up ```
saavagebueno commented 2025-11-20 05:23:47 -05:00
Author
Owner
Copy Link

@dd0ke commented on GitHub (Jul 31, 2024):

This did, in fact, fix the issue!
You are wonderful! It’s rare to have this level of swift and efficient.
I’m 1 day old with Netbird so do not know yet its components and architecture.

On Jul 31, 2024, at 5:15 PM, Maycon Santos @.***> wrote:

@ekavun https://github.com/ekavun this is because the daemon is running with a different binary.

What you can do to replace it:

sudo netbird service stop
sudo mv ./netbird $(which netbird)
sudo netbird start
netbird up
—
Reply to this email directly, view it on GitHub https://github.com/netbirdio/netbird/issues/2319#issuecomment-2260765898, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF7LKBLJOZUOFFIEM7FMDB3ZPD5PNAVCNFSM6AAAAABLNB3UACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRQG43DKOBZHA.
You are receiving this because you were mentioned.

@dd0ke commented on GitHub (Jul 31, 2024): This did, in fact, fix the issue! You are wonderful! It’s rare to have this level of swift and efficient. I’m 1 day old with Netbird so do not know yet its components and architecture. > On Jul 31, 2024, at 5:15 PM, Maycon Santos ***@***.***> wrote: > > > @ekavun <https://github.com/ekavun> this is because the daemon is running with a different binary. > > What you can do to replace it: > > sudo netbird service stop > sudo mv ./netbird $(which netbird) > sudo netbird start > netbird up > — > Reply to this email directly, view it on GitHub <https://github.com/netbirdio/netbird/issues/2319#issuecomment-2260765898>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AF7LKBLJOZUOFFIEM7FMDB3ZPD5PNAVCNFSM6AAAAABLNB3UACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRQG43DKOBZHA>. > You are receiving this because you were mentioned. >
saavagebueno commented 2025-11-20 05:23:48 -05:00
Author
Owner
Copy Link

@tylerbean commented on GitHub (Jul 31, 2024):

Fixed for me as well, thank you so much

@tylerbean commented on GitHub (Jul 31, 2024): Fixed for me as well, thank you so much
saavagebueno commented 2025-11-20 05:23:48 -05:00
Author
Owner
Copy Link

@nazarewk commented on GitHub (Apr 23, 2025):

@tylerbean @dd0ke is the issue resolved? can we close this?

@nazarewk commented on GitHub (Apr 23, 2025): @tylerbean @dd0ke is the issue resolved? can we close this?
saavagebueno commented 2025-11-20 05:23:48 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Jun 1, 2025):

closing issue due to no recent feedback. Feel free to open a new one if the issue persist or reopen if this was a feature request.

@mlsmaycon commented on GitHub (Jun 1, 2025): closing issue due to no recent feedback. Feel free to open a new one if the issue persist or reopen if this was a feature request.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
2021 Q4
2022 Q1
2022 Q1
accessibility
acl
agent
agent
Android
Android
api
authentik
automation
azure
battery-usage
bug
cache
client
client-ui
cloud
cloud-only
cloudflare
community
compatibility
config-idp
config-issue
connection
contribution
coturn
cross-vpn
dashboard
data-usage
distribution
dns
docker
documentation
duplicate
enhancement
enhancement
event-stream
feature-request
freebsd
getting-started
go
good first issue
gui
help wanted
home-assistant
idp
inconsistency
integration
integrations
ios
ipv6
jwt
k8s
keycloak
linux
login
macos
management-service
missing-docs
mobile
moved-internal
needs-review
netbird-ui
networking
new-platform
nginx
notification
okta
openwrt
packaging
peer-management
peer-management
peer-management
performance
postgres
posture-checks
psk
pull-request
Mirrored from GitHub Pull Request
 question
refactor
relay
release
rfc
routes
security
security-related
self-hosting
server
signal
sleep-issue
ssh
ssl
status
store
synology
system-compatibility-issue
test-suite
third-party-integration
triage
triage-needed
troubleshooting
UX
waiting-feedback
windows
wontfix
zitadel
No Label agent client waiting-feedback
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#1085
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?