linuxserver / docker-unifi-network-application

GNU General Public License v3.0
721 stars 54 forks source link

Fingerprint change icon doesn't work #87

Closed hutkayl closed 5 months ago

hutkayl commented 6 months ago

Is there an existing issue for this?

Current Behavior

i wanted to set the fingerprint icon for my client (cellphone) in the new frontend, but the popup window (change icon) was empty. I tried in the legacy frontend as well, and I got an error message there; Failed to load Some data requirements failed to load. Please try later. I tried several times, the results are the same.

Expected Behavior

the icon change should be work in both frontends.

Steps To Reproduce

Képernyőfotó 2024-05-14 - 16 20 33 Képernyőfotó 2024-05-14 - 16 22 33 Képernyőfotó 2024-05-14 - 16 23 19

Environment

- Synology NAS DS720+
- Docker container (Synology Conatiner Manager)

CPU architecture

x86-64

Docker creation

services:
  unifi-network-application:
    image: lscr.io/linuxserver/unifi-network-application:latest
    container_name: unifi-network-application
    environment:
      - PUID=1026
      - PGID=101
      - TZ=Europe/Budapest
      - MONGO_USER=XXXXXXXX
      - MONGO_PASS=XXXXXXXX
      - MONGO_HOST=XXXXXXXX
      - MONGO_PORT=27017
      - MONGO_DBNAME=XXXXXXXX
      - MONGO_TLS=enable
      - MONGO_AUTHSOURCE=XXXXXXXX
    volumes:
      - /volume1/docker/unifi-network/config:/config
      - /volume1/docker/unifi-network/backup:/backup
    ports:
      - 8443:8443
      - 3478:3478/udp
      - 10001:10001/udp
      - 8080:8080
    restart: unless-stopped
    networks:
      - unifi-net
    depends_on:
      - unifi-db

  unifi-db:
    image: docker.io/mongo:4
    container_name: unifi-db
    environment:
      - TZ=Europe/Budapest
    ports:
      - 2717:27017
    volumes:
      - /volume1/docker/unifi-db/databases:/data/db
      - /volume1/docker/unifi-db/config/:/config/
      - /volume1/docker/unifi-db/init-mongo.js:/docker-entrypoint-initdb.d/init-mongo.js:ro
    restart: unless-stopped
    networks:
      - unifi-net

networks:
  unifi-net:
    driver: bridge

Container logs

date    stream  content
2024/05/13 22:43:04 stderr  at java.base/java.lang.Thread.run(Thread.java:840)
2024/05/13 22:43:04 stderr  at com.ubnt.ace.Launcher.Ö00000(Unknown Source)
2024/05/13 22:43:04 stderr  at com.ubnt.service.C.Ö00000(Unknown Source)
2024/05/13 22:43:04 stderr  at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1249)
2024/05/13 22:43:04 stderr  at org.springframework.context.support.AbstractRefreshableApplicationContext.getBeanFactory(AbstractRefreshableApplicationContext.java:168)
2024/05/13 22:43:04 stderr  Exception in thread "Thread-10" java.lang.IllegalStateException: BeanFactory not initialized or already closed - call 'refresh' before accessing beans via the ApplicationContext
2024/05/13 22:43:04 stdout  org.tuckey.web.filters.urlrewrite.UrlRewriteFilter INFO: destroy called
2024/05/13 22:38:03 stdout  [ls.io-init] done.
2024/05/13 22:32:45 stdout  [custom-init] No custom files found, skipping...
2024/05/13 22:32:44 stderr  for: CN=unifi
2024/05/13 22:32:44 stderr  Generating 4,096 bit RSA key pair and self-signed certificate (SHA384withRSA) with a validity of 3,650 days
2024/05/13 22:32:38 stdout  *** Waiting for MONGO_HOST unifi-db to be reachable. ***
2024/05/13 22:32:38 stdout  
2024/05/13 22:32:38 stdout  ───────────────────────────────────────
2024/05/13 22:32:38 stdout  User GID:    101
2024/05/13 22:32:38 stdout  User UID:    1026
2024/05/13 22:32:38 stdout  
2024/05/13 22:32:38 stdout  ───────────────────────────────────────
2024/05/13 22:32:38 stdout  GID/UID
2024/05/13 22:32:38 stdout  ───────────────────────────────────────
2024/05/13 22:32:38 stdout  
2024/05/13 22:32:38 stdout  https://www.linuxserver.io/donate/
2024/05/13 22:32:38 stdout  To support LSIO projects visit:
2024/05/13 22:32:38 stdout  
2024/05/13 22:32:38 stdout  ───────────────────────────────────────
2024/05/13 22:32:38 stdout     Brought to you by linuxserver.io
2024/05/13 22:32:38 stdout  
2024/05/13 22:32:38 stdout        ╚══════╝╚══════╝╚═╝ ╚═════╝
2024/05/13 22:32:38 stdout        ███████╗███████║██║╚██████╔╝
2024/05/13 22:32:38 stdout        ██║     ╚════██║██║██║   ██║
2024/05/13 22:32:38 stdout        ██║     ███████╗██║██║   ██║
2024/05/13 22:32:38 stdout        ██║     ██╔════╝██║██╔═══██╗
2024/05/13 22:32:38 stdout        ██╗     ███████╗██╗ ██████╗
2024/05/13 22:32:38 stdout  
2024/05/13 22:32:38 stdout  ───────────────────────────────────────
2024/05/13 22:32:36 stdout  [migrations] no migrations found
2024/05/13 22:32:36 stdout  [migrations] started
github-actions[bot] commented 6 months ago

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

LinuxServer-CI commented 5 months ago

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.

hutkayl commented 5 months ago

Do you have any idea about this issue?

j0nnymoe commented 5 months ago

It's likely a unifi bug than something with the container. We don't do anything more than installing the packages they provide.

ForsakenRei commented 5 months ago

I'm having the same issue after migrating controller to a different machine(if that matter), I'm running 8.2.93 but remembered it works before.

drizuid commented 5 months ago

We support the container, not the application within the container. I do not have this issue, nor do the majority of our users. As stated we simply install ubiquiti's package, you will need to seek help from them on this issue.