SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-07-27 16:32:34 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

netbird up fails with device auth failure #670

New Issue
Open
opened 2025-11-20 05:15:43 -05:00 by saavagebueno · 17 comments
saavagebueno commented 2025-11-20 05:15:43 -05:00
Owner
Copy Link

Originally created by @synfinatic on GitHub (Mar 1, 2024).

Describe the problem

Just did a netbird down followed by a netbird up on a device which was bootstrapped onto the netbird network via a setup key and it will not connect.

To Reproduce

netbird down && netbird up

Expected behavior

Connect to netbird. Don't error out with the following error:

2024-03-02T01:47:37Z WARN client/cmd/root.go:195: retrying Login to the Management service in 1.359509522s due to error rpc error: code = Unknown desc = getting device authorization flow info failed with error: context deadline exceeded
2024-03-02T01:47:49Z WARN client/cmd/root.go:195: retrying Login to the Management service in 2.133556171s due to error rpc error: code = Unknown desc = getting device authorization flow info failed with error: context deadline exceeded
Error: login backoff cycle failed: rpc error: code = Unknown desc = getting device authorization flow info failed with error: context deadline exceeded

Are you using NetBird Cloud?

Yes, using cloud.

NetBird version

0.25.7

NetBird status -d output:

netbird status -d
Daemon status: LoginFailed

Run UP command to log in with SSO (interactive login):

 netbird up

If you are running a self-hosted version and no SSO provider has been configured in your Management Server,
you can use a setup-key:

 netbird up --management-url <YOUR_MANAGEMENT_URL> --setup-key <YOUR_SETUP_KEY>

More info: https://docs.netbird.io/how-to/register-machines-using-setup-keys

Screenshots

If applicable, add screenshots to help explain your problem.

Additional context

Add any other context about the problem here.

Originally created by @synfinatic on GitHub (Mar 1, 2024). **Describe the problem** Just did a `netbird down` followed by a `netbird up` on a device which was bootstrapped onto the netbird network via a setup key and it will not connect. **To Reproduce** `netbird down && netbird up` **Expected behavior** Connect to netbird. Don't error out with the following error: ``` 2024-03-02T01:47:37Z WARN client/cmd/root.go:195: retrying Login to the Management service in 1.359509522s due to error rpc error: code = Unknown desc = getting device authorization flow info failed with error: context deadline exceeded 2024-03-02T01:47:49Z WARN client/cmd/root.go:195: retrying Login to the Management service in 2.133556171s due to error rpc error: code = Unknown desc = getting device authorization flow info failed with error: context deadline exceeded Error: login backoff cycle failed: rpc error: code = Unknown desc = getting device authorization flow info failed with error: context deadline exceeded ``` **Are you using NetBird Cloud?** Yes, using cloud. **NetBird version** 0.25.7 **NetBird status -d output:** ``` netbird status -d Daemon status: LoginFailed Run UP command to log in with SSO (interactive login): netbird up If you are running a self-hosted version and no SSO provider has been configured in your Management Server, you can use a setup-key: netbird up --management-url <YOUR_MANAGEMENT_URL> --setup-key <YOUR_SETUP_KEY> More info: https://docs.netbird.io/how-to/register-machines-using-setup-keys ``` **Screenshots** If applicable, add screenshots to help explain your problem. **Additional context** Add any other context about the problem here.
saavagebueno added the waiting-feedbacktriage-needed labels 2025-11-20 05:15:43 -05:00
saavagebueno commented 2025-11-20 05:15:44 -05:00
Author
Owner
Copy Link

@synfinatic commented on GitHub (Mar 1, 2024):

updated to 0.26.2 and same problem:

$ netbird status
Daemon version: 0.26.2
CLI version: 0.26.2
Management: Disconnected, reason: rpc error: code = FailedPrecondition desc = failed connecting to Management Service : context deadline exceeded
Signal: Disconnected
Relays: 0/0 Available
FQDN:
NetBird IP: N/A
Interface type: N/A
Quantum resistance: false
Peers count: 0/0 Connected

$ netbird up
2024-03-02T02:00:13Z WARN client/cmd/root.go:204: retrying Login to the Management service in 920.398536ms due to error rpc error: code = Unknown desc = getting device authorization flow info failed with error: context deadline exceeded
2024-03-02T02:00:24Z WARN client/cmd/root.go:204: retrying Login to the Management service in 889.796141ms due to error rpc error: code = Unknown desc = getting device authorization flow info failed with error: context deadline exceeded
Error: login backoff cycle failed: rpc error: code = Unknown desc = getting device authorization flow info failed with error: context deadline exceeded
@synfinatic commented on GitHub (Mar 1, 2024): updated to 0.26.2 and same problem: ``` $ netbird status Daemon version: 0.26.2 CLI version: 0.26.2 Management: Disconnected, reason: rpc error: code = FailedPrecondition desc = failed connecting to Management Service : context deadline exceeded Signal: Disconnected Relays: 0/0 Available FQDN: NetBird IP: N/A Interface type: N/A Quantum resistance: false Peers count: 0/0 Connected $ netbird up 2024-03-02T02:00:13Z WARN client/cmd/root.go:204: retrying Login to the Management service in 920.398536ms due to error rpc error: code = Unknown desc = getting device authorization flow info failed with error: context deadline exceeded 2024-03-02T02:00:24Z WARN client/cmd/root.go:204: retrying Login to the Management service in 889.796141ms due to error rpc error: code = Unknown desc = getting device authorization flow info failed with error: context deadline exceeded Error: login backoff cycle failed: rpc error: code = Unknown desc = getting device authorization flow info failed with error: context deadline exceeded ```
saavagebueno commented 2025-11-20 05:15:44 -05:00
Author
Owner
Copy Link

@synfinatic commented on GitHub (Mar 2, 2024):

Looks like this was a service issue with netbird.io cloud service as it is working now? Was there a status page I should have looked for system/health status?

$ netbird status
Daemon version: 0.26.2
CLI version: 0.26.2
Management: Connected
Signal: Connected
Relays: 2/2 Available
FQDN: raspi-blue.netbird.cloud
NetBird IP: 100.93.254.165/16
Interface type: Kernel
Quantum resistance: false
Peers count: 1/4 Connected
@synfinatic commented on GitHub (Mar 2, 2024): Looks like this was a service issue with netbird.io cloud service as it is working now? Was there a status page I should have looked for system/health status? ``` $ netbird status Daemon version: 0.26.2 CLI version: 0.26.2 Management: Connected Signal: Connected Relays: 2/2 Available FQDN: raspi-blue.netbird.cloud NetBird IP: 100.93.254.165/16 Interface type: Kernel Quantum resistance: false Peers count: 1/4 Connected ```
saavagebueno commented 2025-11-20 05:15:44 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Mar 2, 2024):

@synfinatic can you check the logs, especially the /var/log/netbird/netbird.err?

@mlsmaycon commented on GitHub (Mar 2, 2024): @synfinatic can you check the logs, especially the /var/log/netbird/netbird.err?
saavagebueno commented 2025-11-20 05:15:44 -05:00
Author
Owner
Copy Link

@synfinatic commented on GitHub (Mar 2, 2024):

Sadly, there are no logs anymore since this device is running DietPi and /var/log is on a ramdisk volume which is purged on a regular basis.

@synfinatic commented on GitHub (Mar 2, 2024): Sadly, there are no logs anymore since this device is running DietPi and /var/log is on a ramdisk volume which is purged on a regular basis.
saavagebueno commented 2025-11-20 05:15:44 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Mar 2, 2024):

Please run the agent in the foreground:

sudo netbird service stop
sudo netbird up -F -l debug -m https://your-server-url:port
@mlsmaycon commented on GitHub (Mar 2, 2024): Please run the agent in the foreground: ```shell sudo netbird service stop sudo netbird up -F -l debug -m https://your-server-url:port ```
saavagebueno commented 2025-11-20 05:15:45 -05:00
Author
Owner
Copy Link

@synfinatic commented on GitHub (Mar 2, 2024):

As I stated earlier this morning, the problem seems to have resolved itself. I'm no longer able to reproduce this issue. Should it happen again, I'll be happy to provide the logs... unfortunately the ticket template didn't ask for them and I forgot about the log purging.

However, the limited output seems to indicate an issue with the netbird.io service? Can you confirm there a service issue at that time? I opened the ticket while the problem was occurring.

@synfinatic commented on GitHub (Mar 2, 2024): As I stated earlier this morning, the problem seems to have resolved itself. I'm no longer able to reproduce this issue. Should it happen again, I'll be happy to provide the logs... unfortunately the ticket template didn't ask for them and I forgot about the log purging. However, the limited output seems to indicate an issue with the netbird.io service? Can you confirm there a service issue at that time? I opened the ticket while the problem was occurring.
saavagebueno commented 2025-11-20 05:15:45 -05:00
Author
Owner
Copy Link

@WGandy commented on GitHub (Mar 3, 2024):

I just had what appears to the the same error with a client. "context deadline exceeded". This is with a selfhosted netbird. AND I see now that my management seems to be messed up. No peers appear when I log in. Errors from docker show:
http: TLS handshake error from xxx.xxx.xxx.xxx:63817: remote error: tls: unknown certificate

The certs for the management server seems to be intact as I can log in. (those are handled by caddy) but I think there are certs for another part of this?

@WGandy commented on GitHub (Mar 3, 2024): I just had what appears to the the same error with a client. "context deadline exceeded". This is with a selfhosted netbird. AND I see now that my management seems to be messed up. No peers appear when I log in. Errors from docker show: ` http: TLS handshake error from xxx.xxx.xxx.xxx:63817: remote error: tls: unknown certificate` The certs for the management server seems to be intact as I can log in. (those are handled by caddy) but I think there are certs for another part of this?
saavagebueno commented 2025-11-20 05:15:45 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Mar 3, 2024):

@WGandy is that a custom docker build?

@mlsmaycon commented on GitHub (Mar 3, 2024): @WGandy is that a custom docker build?
saavagebueno commented 2025-11-20 05:15:45 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Mar 4, 2024):

As I stated earlier this morning, the problem seems to have resolved itself. I'm no longer able to reproduce this issue. Should it happen again, I'll be happy to provide the logs... unfortunately the ticket template didn't ask for them and I forgot about the log purging.

However, the limited output seems to indicate an issue with the netbird.io service? Can you confirm there a service issue at that time? I opened the ticket while the problem was occurring.

@synfinatic, we didn't have any issues within the timeframe from your logs.
The issue could be linked to a latency between the client and management service. I've shared with you some steps in https://github.com/netbirdio/netbird/issues/1618#issuecomment-1975941729 that might help us understand the issue in detail.

@mlsmaycon commented on GitHub (Mar 4, 2024): > As I stated earlier this morning, the problem seems to have resolved itself. I'm no longer able to reproduce this issue. Should it happen again, I'll be happy to provide the logs... unfortunately the ticket template didn't ask for them and I forgot about the log purging. > > However, the limited output seems to indicate an issue with the netbird.io service? Can you confirm there a service issue at that time? I opened the ticket while the problem was occurring. @synfinatic, we didn't have any issues within the timeframe from your logs. The issue could be linked to a latency between the client and management service. I've shared with you some steps in https://github.com/netbirdio/netbird/issues/1618#issuecomment-1975941729 that might help us understand the issue in detail.
saavagebueno commented 2025-11-20 05:15:45 -05:00
Author
Owner
Copy Link

@WGandy commented on GitHub (Mar 4, 2024):

Yes, you helped me get it setup quite a while ago. It seems that the Coturn is not finding the certs. And it's probably since the Caddy container recently re-upped them. I'm wondering if perhaps we manually copied the certs to get it going when we set it up??
I'm hoping to find the time to sort through it later today. Hopefully it's just a volume mapping issue.

@WGandy commented on GitHub (Mar 4, 2024): Yes, you helped me get it setup quite a while ago. It seems that the Coturn is not finding the certs. And it's probably since the Caddy container recently re-upped them. I'm wondering if perhaps we manually copied the certs to get it going when we set it up?? I'm hoping to find the time to sort through it later today. Hopefully it's just a volume mapping issue.
saavagebueno commented 2025-11-20 05:15:45 -05:00
Author
Owner
Copy Link

@WGandy commented on GitHub (Mar 7, 2024):

Just a follow up, my failure was on account of Caddy renewing certs with a different CA than it used previously. This resulted in having the cert files located at a different path. The dashboard container was able to use the new certs but the management container did not. I manually changed the cert file names and paths in the docker compose for the management and in the management.json file. If it renews again with the opposite provider then I'll need to manually change it again. But, I think that this will be automated in a future version of Netbird.

@WGandy commented on GitHub (Mar 7, 2024): Just a follow up, my failure was on account of Caddy renewing certs with a different CA than it used previously. This resulted in having the cert files located at a different path. The dashboard container was able to use the new certs but the management container did not. I manually changed the cert file names and paths in the docker compose for the management and in the management.json file. If it renews again with the opposite provider then I'll need to manually change it again. But, I think that this will be automated in a future version of Netbird.
saavagebueno commented 2025-11-20 05:15:45 -05:00
Author
Owner
Copy Link

@juniormarangao commented on GitHub (Sep 16, 2024):

Hi!

I am facing this issue, I can't connect any client.
I've installed using Advanced guide, with Authentik and Nginx Proxy Manager.
I can login, shows peers page, I can create management Keys, but I cannot connect.

When I debbug shows this below

2024-09-16T12:33:03-03:00 ERRO client/internal/login.go:105: failed while getting Management Service public key: failed while getting Management Service public key
2024-09-16T12:33:03-03:00 WARN client/cmd/root.go:234: retrying Login to the Management service in 1.259689188s due to error failed while getting Management Service public key
2024-09-16T12:33:05-03:00 DEBG client/internal/login.go:93: connecting to the Management service https://vpn.example.com:443
2024-09-16T12:33:05-03:00 DEBG client/internal/login.go:63: connected to the Management service https://vpn.example.com:443
2024-09-16T12:33:05-03:00 ERRO management/client/grpc.go:287: failed while getting Management Service public key: rpc error: code = Unavailable desc = unexpected HTTP status code received from server: 502 (Bad Gateway); transport: received unexpected content-type "text/html"

The setup is 3 VMs:

  1. Nginx Proxy Manager
  2. Authentik
  3. Netbird

All behind one Public IP, but same internal network, all reachable between each.
In NPM with host pointing to netbird vm, is the ports 80, 443, and 33073 in configuration, with gRPC, etc...

The other ports required, is forwarding directly to the netbird VM.

There are something that I missed?

@juniormarangao commented on GitHub (Sep 16, 2024): Hi! I am facing this issue, I can't connect any client. I've installed using Advanced guide, with Authentik and Nginx Proxy Manager. I can login, shows peers page, I can create management Keys, but I cannot connect. When I debbug shows this below ``` 2024-09-16T12:33:03-03:00 ERRO client/internal/login.go:105: failed while getting Management Service public key: failed while getting Management Service public key 2024-09-16T12:33:03-03:00 WARN client/cmd/root.go:234: retrying Login to the Management service in 1.259689188s due to error failed while getting Management Service public key 2024-09-16T12:33:05-03:00 DEBG client/internal/login.go:93: connecting to the Management service https://vpn.example.com:443 2024-09-16T12:33:05-03:00 DEBG client/internal/login.go:63: connected to the Management service https://vpn.example.com:443 2024-09-16T12:33:05-03:00 ERRO management/client/grpc.go:287: failed while getting Management Service public key: rpc error: code = Unavailable desc = unexpected HTTP status code received from server: 502 (Bad Gateway); transport: received unexpected content-type "text/html" ``` The setup is 3 VMs: 1. Nginx Proxy Manager 2. Authentik 3. Netbird All behind one Public IP, but same internal network, all reachable between each. In NPM with host pointing to netbird vm, is the ports `80`, `443`, and `33073` in configuration, with gRPC, etc... The other ports required, is forwarding directly to the netbird VM. There are something that I missed?
saavagebueno commented 2025-11-20 05:15:46 -05:00
Author
Owner
Copy Link

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

Hello @synfinatic,

We're currently reviewing our open issues and would like to verify if this problem still exists in the latest NetBird version.

Could you please confirm if the issue is still there?

We may close this issue temporarily if we don't hear back from you within 2 weeks, but feel free to reopen it with updated information.

Thanks for your contribution to improving the project!

@nazarewk commented on GitHub (Apr 28, 2025): Hello @synfinatic, We're currently reviewing our open issues and would like to verify if this problem still exists in the [latest NetBird version](https://github.com/netbirdio/netbird/releases). Could you please confirm if the issue is still there? We may close this issue temporarily if we don't hear back from you within **2 weeks**, but feel free to reopen it with updated information. Thanks for your contribution to improving the project!
saavagebueno commented 2025-11-20 05:15:46 -05:00
Author
Owner
Copy Link

@jjqtony commented on GitHub (May 1, 2025):

2025-05-01T13:00:39+08:00 DEBG client/internal/login.go:94: connecting to the Management service https://api.netbird.io:443
2025-05-01T13:00:39+08:00 DEBG util/net/dialer_dial.go:52: Dialing tcp api.netbird.io:443
2025-05-01T13:00:49+08:00 INFO ./caller_not_available:0: 2025/05/01 13:00:49 WARNING: [core] [Channel #1 SubChannel #2]grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: authentication handshake failed: EOF"
2025-05-01T13:00:50+08:00 DEBG util/net/dialer_dial.go:52: Dialing tcp api.netbird.io:443
2025-05-01T13:01:00+08:00 INFO ./caller_not_available:0: 2025/05/01 13:01:00 WARNING: [core] [Channel #1 SubChannel #2]grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: authentication handshake failed: EOF"

@jjqtony commented on GitHub (May 1, 2025): 2025-05-01T13:00:39+08:00 DEBG client/internal/login.go:94: connecting to the Management service https://api.netbird.io:443 2025-05-01T13:00:39+08:00 DEBG util/net/dialer_dial.go:52: Dialing tcp api.netbird.io:443 2025-05-01T13:00:49+08:00 INFO ./caller_not_available:0: 2025/05/01 13:00:49 WARNING: [core] [Channel #1 SubChannel #2]grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: authentication handshake failed: EOF" 2025-05-01T13:00:50+08:00 DEBG util/net/dialer_dial.go:52: Dialing tcp api.netbird.io:443 2025-05-01T13:01:00+08:00 INFO ./caller_not_available:0: 2025/05/01 13:01:00 WARNING: [core] [Channel #1 SubChannel #2]grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: authentication handshake failed: EOF"
saavagebueno commented 2025-11-20 05:15:46 -05:00
Author
Owner
Copy Link

@morandalex commented on GitHub (Aug 22, 2025):

having this from one peer:

Last login: Fri Aug 22 17:08:58 2025 from 10.232.161.204
ale@raspi52:~ $ netbird up
Error: daemon up failed: login backoff cycle failed: rpc error: code = Unknown desc = getting device authorization flow info failed with error: context deadline exceeded
ale@raspi52:~ $ netbird up
Error: daemon up failed: login backoff cycle failed: rpc error: code = Unknown desc = getting device authorization flow info failed with error: context deadline exceeded

@morandalex commented on GitHub (Aug 22, 2025): having this from one peer: Last login: Fri Aug 22 17:08:58 2025 from 10.232.161.204 ale@raspi52:~ $ netbird up Error: daemon up failed: login backoff cycle failed: rpc error: code = Unknown desc = getting device authorization flow info failed with error: context deadline exceeded ale@raspi52:~ $ netbird up Error: daemon up failed: login backoff cycle failed: rpc error: code = Unknown desc = getting device authorization flow info failed with error: context deadline exceeded
saavagebueno commented 2025-11-20 05:15:46 -05:00
Author
Owner
Copy Link

@ghaisasadvait commented on GitHub (Sep 5, 2025):

having this from one peer:

Last login: Fri Aug 22 17:08:58 2025 from 10.232.161.204 ale@raspi52:~ netbird up Error: daemon up failed: login backoff cycle failed: rpc error: code = Unknown desc = getting device authorization flow info failed with error: context deadline exceeded ale@raspi52:~ netbird up Error: daemon up failed: login backoff cycle failed: rpc error: code = Unknown desc = getting device authorization flow info failed with error: context deadline exceeded

Same issue for me

@ghaisasadvait commented on GitHub (Sep 5, 2025): > having this from one peer: > > Last login: Fri Aug 22 17:08:58 2025 from 10.232.161.204 ale@raspi52:~ $ netbird up Error: daemon up failed: login backoff cycle failed: rpc error: code = Unknown desc = getting device authorization flow info failed with error: context deadline exceeded ale@raspi52:~ $ netbird up Error: daemon up failed: login backoff cycle failed: rpc error: code = Unknown desc = getting device authorization flow info failed with error: context deadline exceeded Same issue for me
saavagebueno commented 2025-11-20 05:15:46 -05:00
Author
Owner
Copy Link

@lukababu commented on GitHub (Oct 4, 2025):

I did some upgrades including changing the port for managment and turn server. Nedless to say I encounted the same issue.

Here is how I solved it.

You'll have to go one by one for each peer that has Session Expiration disabled and re-enable them.

then on the target peer do the following:

sudo netbird service stop
sudo netbird up -F -l debug -m https://your-server-url:port

It should prompt for login. Do that then close the session (control + c).

Disable Session Expiration.

Now either run sudo apt update and sudo apt install netbird update to get the latest and re-enable the service or just simply run sudo netbird service start

You should now have this resolved for this peer. Do it for the other ones now :)

@lukababu commented on GitHub (Oct 4, 2025): I did some upgrades including changing the port for managment and turn server. Nedless to say I encounted the same issue. Here is how I solved it. You'll have to go one by one for each peer that has Session Expiration disabled and re-enable them. then on the target peer do the following: `sudo netbird service stop` `sudo netbird up -F -l debug -m https://your-server-url:port` It should prompt for login. Do that then close the session (control + c). Disable Session Expiration. Now either run `sudo apt update` and `sudo apt install netbird `update to get the latest and re-enable the service or just simply run `sudo netbird service start` You should now have this resolved for this peer. Do it for the other ones now :)
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 triage-needed 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#670
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?