Closed iMonZ closed 7 months ago
Likely due to the backup having specific settings for a Macos installed as it's having issues binding to IP's that aren't there.
Likely due to the backup having specific settings for a Macos installed as it's having issues binding to IP's that aren't there.
Thanks! Solved the issue with using OrbStack instead of Docker. Works now!
Likely due to the backup having specific settings for a Macos installed as it's having issues binding to IP's that aren't there.
Just a small question. Ony my Unifi AP Device it stuck at adopting and set-inform command doesnt exist. Do you know how I can fix that?
Likely due to the backup having specific settings for a Macos installed as it's having issues binding to IP's that aren't there.
Just a small question. Ony my Unifi AP Device it stuck at adopting and set-inform command doesnt exist. Do you know how I can fix that?
U6-Enterprise-BZ.6.6.54# set-inform /bin/ash: set-inform: not found
You need to set the inform URL within the controler. No idea why your device doesn't have set-inform. You'll need to check unifi documentation.
Also note, we don't test/support orbstack, so any issues, we're unable to troubleshoot with that.
These are my logs
:1023 Permanent error code on channel bind request: 400 - Empty port number in channel bind request :1023 Permanent error code on channel bind request: 403 - Forbidden IP :484 All TURN channel bindings failed :948 Unable to read data from SCTP socket. Permanent error: (104) Connection reset by peer :366 SCTP ingest failed :220 SCTP ingest failed :221 Unable to do SSL I/O :906 webRtcId 1 terminated with code: (-2147090409) WebRTC connection interrupted from far side :1023 Permanent error code on channel bind request: 403 - Forbidden IP :1023 Permanent error code on channel bind request: 400 - Empty port number in channel bind request :1023 Permanent error code on channel bind request: 400 - Empty port number in channel bind request :484 All TURN channel bindings failed :948 Unable to read data from SCTP socket. Permanent error: (104) Connection reset by peer :366 SCTP ingest failed :220 SCTP ingest failed :221 Unable to do SSL I/O :906 webRtcId 3 terminated with code: (-2147090409) WebRTC connection interrupted from far side :585 STUN id: 4; fd: 195 192.168.228.3:39267 -> 213.55.243.56:26400 (eth0) DTLS id: 0 () (PEER) timed out :585 STUN id: 5; fd: 195 192.168.228.3:39267 -> 18.156.18.159:18577 (eth0) DTLS id: 0 () (PEER) timed out :585 STUN id: 6; fd: 195 192.168.228.3:39267 -> 192.168.1.9:62097 (eth0) DTLS id: 0 () (PEER) timed out
Also note, we don't test/support orbstack, so any issues, we're unable to troubleshoot with that.
This is my engine config:
{ "experimental" : true, "ipv6" : true }
Is this fine or should I remove something from here?
I have no idea, like I said, we don't test in that platform. https://docs.linuxserver.io/misc/support-policy/
I have no idea, like I said, we don't test in that platform. https://docs.linuxserver.io/misc/support-policy/
Okay thanks I switched now to docker desktop and get the exact same error. I have the latest docker desktop version.
@j0nnymoe Thats my docker compose file:
version: "2.1"
services:
unifi-network-application:
image: lscr.io/linuxserver/unifi-network-application:latest
container_name: unifi-network-application
environment:
- PUID=1000
- PGID=1000
- TZ=Europe/Zurich
- MONGO_USER=MONGO_USER
- MONGO_PASS=MONGO_PASS
- MONGO_HOST=unifi-mongo
- MONGO_PORT=27017
- MONGO_DBNAME=MONGO_DBNAME
- MEM_LIMIT=1024 #optional
- MEM_STARTUP=1024 #optional
- MONGO_TLS= #optional
- MONGO_AUTHSOURCE= #optional
volumes:
- ../Docker-Files:/config
ports:
- 8443:8443
- 3478:3478/udp
- 10001:10001/udp
- 8080:8080
- 1900:1900/udp #optional
- 8843:8843 #optional
- 8880:8880 #optional
- 6789:6789 #optional
- 5514:5514/udp #optional
restart: always
networks:
- unifi-network
networks:
unifi-network:
external: true
@j0nnymoe Thats my docker compose file:
version: "2.1" services: unifi-network-application: image: lscr.io/linuxserver/unifi-network-application:latest container_name: unifi-network-application environment: - PUID=1000 - PGID=1000 - TZ=Europe/Zurich - MONGO_USER=MONGO_USER - MONGO_PASS=MONGO_PASS - MONGO_HOST=unifi-mongo - MONGO_PORT=27017 - MONGO_DBNAME=MONGO_DBNAME - MEM_LIMIT=1024 #optional - MEM_STARTUP=1024 #optional - MONGO_TLS= #optional - MONGO_AUTHSOURCE= #optional volumes: - ../Docker-Files:/config ports: - 8443:8443 - 3478:3478/udp - 10001:10001/udp - 8080:8080 - 1900:1900/udp #optional - 8843:8843 #optional - 8880:8880 #optional - 6789:6789 #optional - 5514:5514/udp #optional restart: always networks: - unifi-network networks: unifi-network: external: true
So that the mongodb database should only be accesible from the Unifi Container I have created a new network where I have put both container inside.
Is there an existing issue for this?
Current Behavior
Unifi page shows after importing the config a 404
Expected Behavior
No response
Steps To Reproduce
Environment
CPU architecture
arm64
Docker creation
Container logs