[BUG] STUN/TURN failing - unable to connect through unifi.ui.com

[crimist]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Attempting to open my site in unifi.ui.com causes it to hang infinitely (loading bar stuck).

Expected Behavior

Opening my site in unifi.ui.com should load without issue.

Steps To Reproduce

1. open unifi.ui.com
2. choose the self hosted site

Environment

- OS: Debian 12.10
- Linux: 6.1.0-28-amd64
- How docker service was installed: debian mirror `https://download.docker.com/linux/debian bookworm stable`


$ docker version
Client: Docker Engine - Community
 Version:           28.1.1
 API version:       1.49
 Go version:        go1.23.8
 Git commit:        4eba377
 Built:             Fri Apr 18 09:52:57 2025
 OS/Arch:           linux/amd64
 Context:           default

Server: Docker Engine - Community
 Engine:
  Version:          28.1.1
  API version:      1.49 (minimum version 1.24)
  Go version:       go1.23.8
  Git commit:       01f442b
  Built:            Fri Apr 18 09:52:57 2025
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.7.27
  GitCommit:        05044ec0a9a75232cad458027ca83437aae3f4da
 runc:
  Version:          1.2.5
  GitCommit:        v1.2.5-0-g59923ef
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

CPU architecture

x86-64

Docker creation

services:
  unifi-db:
    image: docker.io/mongo:7
    container_name: unifi-db
    environment:
      - MONGO_INITDB_ROOT_USERNAME=<redacted>
      - MONGO_INITDB_ROOT_PASSWORD=<redacted>
      - MONGO_USER=<redacted>
      - MONGO_PASS=<redacted>
      - MONGO_DBNAME=<redacted>
      - MONGO_AUTHSOURCE=<redacted>
    volumes:
      - ./mongo/data:/data/db
      - ./mongo/init-mongo.sh:/docker-entrypoint-initdb.d/init-mongo.sh:ro
    restart: unless-stopped

  unifi:
    image: lscr.io/linuxserver/unifi-network-application:latest
    container_name: unifi
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/PST
      - MONGO_USER=<redacted>
      - MONGO_PASS=<redacted>
      - MONGO_HOST=<redacted>
      - MONGO_PORT=<redacted>
      - MONGO_DBNAME=<redacted>
      - MONGO_AUTHSOURCE=<redacted>
    volumes:
      - ./unifi/data:/config
    ports:
      - 8443:8443
      - 3478:3478/udp
      - 10001:10001/udp
      - 8080:8080
    restart: unless-stopped

Container logs

the same errors repeat over and over


:0 TCP candidates not supported yet
:0 TCP candidates not supported yet
:0 Permanent error code on allocate request: 420 - . This was after receiving a valid nonce
:0 TURN instance failed: TURN id:   3; fd: 228 0.0.0.0:47973 -> 141.101.90.1:3478 (all_interfaces) DTLS id:
:0 STUN id:   4; fd: 255 172.18.0.2:39990 -> <redacted>:51442 (eth0) DTLS id: 0 () (PEER) timed out
:0 STUN id:   5; fd: 255 172.18.0.2:39990 -> 104.30.147.21:30607 (eth0) DTLS id: 0 () (PEER) timed out
:0 STUN id:   6; fd: 255 172.18.0.2:39990 -> 104.30.147.21:39732 (eth0) DTLS id: 0 () (PEER) timed out
:0 STUN id:   7; fd: 255 172.18.0.2:39990 -> 104.30.147.22:39341 (eth0) DTLS id: 0 () (PEER) timed out
:0 STUN id:   8; fd: 255 172.18.0.2:39990 -> 104.30.147.22:38986 (eth0) DTLS id: 0 () (PEER) timed out
:0 STUN id:   9; fd: 255 172.18.0.2:39990 -> 104.30.147.22:39646 (eth0) DTLS id: 0 () (PEER) timed out
:0 STUN id:  10; fd: 255 172.18.0.2:39990 -> 104.30.147.23:17767 (eth0) DTLS id: 0 () (PEER) timed out
:0 STUN id:  11; fd: 255 172.18.0.2:39990 -> 104.30.147.21:39806 (eth0) DTLS id: 0 () (PEER) timed out
:0 STUN id:  12; fd: 255 172.18.0.2:39990 -> 104.30.147.20:51845 (eth0) DTLS id: 0 () (PEER) timed out
:0 STUN id:  13; fd: 255 172.18.0.2:39990 -> 104.30.147.22:64518 (eth0) DTLS id: 0 () (PEER) timed out
:0 STUN id:  14; fd: 255 172.18.0.2:39990 -> 104.30.147.22:38650 (eth0) DTLS id: 0 () (PEER) timed out
:0 TCP candidates not supported yet
:0 TCP candidates not supported yet
:0 Permanent error code on allocate request: 420 - . This was after receiving a valid nonce
:0 TURN instance failed: TURN id:   3; fd: 253 0.0.0.0:60555 -> 141.101.90.1:3478 (all_interfaces) DTLS id:
:0 STUN id:   4; fd: 260 172.18.0.2:47078 -> <redacted>:46610 (eth0) DTLS id: 0 () (PEER) timed out
:0 STUN id:   5; fd: 260 172.18.0.2:47078 -> 104.30.147.22:36391 (eth0) DTLS id: 0 () (PEER) timed out
:0 STUN id:   6; fd: 260 172.18.0.2:47078 -> 104.30.147.22:34723 (eth0) DTLS id: 0 () (PEER) timed out
:0 STUN id:   7; fd: 260 172.18.0.2:47078 -> 104.30.147.22:36483 (eth0) DTLS id: 0 () (PEER) timed out
:0 STUN id:   8; fd: 260 172.18.0.2:47078 -> 104.30.147.22:21683 (eth0) DTLS id: 0 () (PEER) timed out
:0 STUN id:   9; fd: 260 172.18.0.2:47078 -> 104.30.147.22:50525 (eth0) DTLS id: 0 () (PEER) timed out
:0 STUN id:  10; fd: 260 172.18.0.2:47078 -> 104.30.147.22:46474 (eth0) DTLS id: 0 () (PEER) timed out
:0 STUN id:  11; fd: 260 172.18.0.2:47078 -> 104.30.147.22:54847 (eth0) DTLS id: 0 () (PEER) timed out
:0 STUN id:  12; fd: 260 172.18.0.2:47078 -> 104.30.147.21:26631 (eth0) DTLS id: 0 () (PEER) timed out
:0 STUN id:  13; fd: 260 172.18.0.2:47078 -> 104.30.147.21:58585 (eth0) DTLS id: 0 () (PEER) timed out
:0 STUN id:  14; fd: 260 172.18.0.2:47078 -> 104.30.147.22:54838 (eth0) DTLS id: 0 () (PEER) timed out
:0 TCP candidates not supported yet
:0 TCP candidates not supported yet
:0 Permanent error code on allocate request: 420 - . This was after receiving a valid nonce
:0 TURN instance failed: TURN id:   3; fd: 277 0.0.0.0:44028 -> 141.101.90.1:3478 (all_interfaces) DTLS id:
...

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[crimist]

Others users have also reported this issue:

#138 (comment)
#138 (comment)

They appear to have an effectively identical configuration.

[crimist]

Interestingly the unifi application for Android seems to connect to the site without issue and no logs are generated.

[providentitsolutions]

Also having the same problem, tried rolling back the image from 9.0.114-ls87 to 9.0.114-ls77 (the earliest LSIO image matching the Unifi Network version 9.0.114) and the issue persists, end unifi devices show as offline in the network application and my container logs show:

[custom-init] No custom files found, skipping...
[ls.io-init] done.
:0 Permanent error code on allocate request: 420 - . This was after receiving a valid nonce
:0 TURN instance failed: TURN id: 3; fd: 221 0.0.0.0:41413 -> 141.101.90.1:3478 (all_interfaces) DTLS id:
:0 Permanent error code on allocate request: 420 - . This was after receiving a valid nonce
:0 TURN instance failed: TURN id: 3; fd: 222 0.0.0.0:44815 -> 141.101.90.1:3478 (all_interfaces) DTLS id:
:0 STUN id: 4; fd: 217 172.20.128.9:47142 -> 62.232.215.226:64635 (eth0) DTLS id: 14 (165.232.41.194:47142) (PEER) timed out
:0 webRtcId 2 terminated with code: (-2147090409) WebRTC connection interrupted from far side

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[crimist]

I'm guessing this is an upstream issue?

https://community.home-assistant.io/t/ui-com-unifi-network-application-connectivity-problem-stun-or-other-traffic-blocked/840401

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.