ysfnsrv opened a new issue, #3129:
URL: https://github.com/apache/apisix-dashboard/issues/3129

   ### Issue description
   
   When visiting http://127.0.0.1:9000/plugin/list, the Dashboard displays a 
blank page.
   No error message is shown, but the plugin list fails to render.
   
   The Admin API /apisix/admin/plugins?all=true returns a valid schema 
(verified), but the UI does not display anything.
   
   This happens when APISIX is running with a valid plugin list in config.yaml, 
and the plugin schema is large or contains nested definitions.
   
   ### Expected behavior
   
   Dashboard should render the plugin list UI correctly based on the response 
from /apisix/admin/plugins?all=true, or at least show a clear error if 
something goes wrong.
   
   ### How to Reproduce
   
   ```
   PRETTY_NAME="Ubuntu 24.04.1 LTS"
   NAME="Ubuntu"
   VERSION_ID="24.04"
   VERSION="24.04.1 LTS (Noble Numbat)"
   VERSION_CODENAME=noble
   ID=ubuntu
   ID_LIKE=debian
   HOME_URL="https://www.ubuntu.com/";
   SUPPORT_URL="https://help.ubuntu.com/";
   BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
   
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
   UBUNTU_CODENAME=noble
   LOGO=ubuntu-logo
   ```
   
   `Docker Compose version v2.35.1`
   
   my docker compose file 
   `services:
     apisix:
       image: apache/apisix:${APISIX_IMAGE_TAG:-3.12.0-debian}
       restart: always
       volumes:
         - ./apisix_conf/config.yaml:/usr/local/apisix/conf/config.yaml:ro
       depends_on:
         - etcd
       ##network_mode: host
       ports:
         - "9180:9180/tcp"
         - "9080:9080/tcp"
         - "9091:9091/tcp"
         - "9443:9443/tcp"
         - "9092:9092/tcp"
       networks:
         apisix:
   
     etcd:
       image: bitnami/etcd:3.5.11
       restart: always
       volumes:
         - etcd_data:/bitnami/etcd
       environment:
         ETCD_ENABLE_V2: "true"
         ALLOW_NONE_AUTHENTICATION: "yes"
         ETCD_ADVERTISE_CLIENT_URLS: "http://etcd:2379";
         ETCD_LISTEN_CLIENT_URLS: "http://0.0.0.0:2379";
       ports:
         - "2379:2379/tcp"
       networks:
         apisix:
   
     web1:
       image: nginx:1.19.0-alpine
       restart: always
       volumes:
         - ./upstream/web1.conf:/etc/nginx/nginx.conf
       ports:
         - "9081:80/tcp"
       environment:
         - NGINX_PORT=80
       networks:
         apisix:
   
     web2:
       image: nginx:1.19.0-alpine
       restart: always
       volumes:
         - ./upstream/web2.conf:/etc/nginx/nginx.conf
       ports:
         - "9082:80/tcp"
       environment:
         - NGINX_PORT=80
       networks:
         apisix:
   
   
     dashboard:
       image: apache/apisix-dashboard:latest
       container_name: apisix-dashboard
       ports:
        - "9000:9000"
       volumes:
         - ./dashboard/conf.yaml:/usr/local/apisix-dashboard/conf/conf.yaml:ro
       networks:
         - apisix
   
   
   networks:
     apisix:
       driver: bridge
   
   volumes:
     etcd_data:
       driver: local
   `
   
   my conf file 
   
   `cat dashboard/conf.yaml 
   conf:
     listen:
       host: 0.0.0.0
       port: 9000
   
     etcd:
       endpoints:
         - http://etcd:2379
   
   authentication:
     secret: secret-key
     expire_time: 3600
     users:
       - username: admin
         password: admin
   `
   
   
   ### Screenshots
   
   _No response_
   
   ### Environment
   
   - apisix version (cmd: `apisix version`):
   - OS (cmd: `uname -a`):
   - OpenResty / Nginx version (cmd: `nginx -V` or `openresty -V`):
   - etcd version, if have (cmd: run `etcd --version`):
   - apisix-dashboard version, if have:
   - Browser version, if have:
   
   
   ### Additional context
   
   
![Image](https://github.com/user-attachments/assets/5661c9b1-3f35-4ed6-a940-3f1148faa4f1)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to