Open jinjianming opened 1 year ago
I experienced the same problem.
Check if the plugin list is present on configuration
plugins:
- api-breaker
- authz-keycloak
- basic-auth
- batch-requests
- consumer-restriction
- cors
# - dubbo-proxy
- echo
# - error-log-logger
# - example-plugin
- fault-injection
- grpc-transcode
- hmac-auth
- http-logger
- ip-restriction
- jwt-auth
- kafka-logger
- key-auth
- limit-conn
- limit-count
- limit-req
# - log-rotate
# - node-status
- openid-connect
- prometheus
- proxy-cache
- proxy-mirror
- proxy-rewrite
- redirect
- referer-restriction
- request-id
- request-validation
- response-rewrite
- serverless-post-function
- serverless-pre-function
# - skywalking
- sls-logger
- syslog
- tcp-logger
- udp-logger
- uri-blocker
- wolf-rbac
- zipkin
- server-info
- traffic-split
After adding, it cannot be fixed,
plugins: # plugin list
- api-breaker
- authz-casbin
- authz-casdoor
- authz-keycloak
- aws-lambda
- azure-functions
- basic-auth
- clickhouse-logger
- client-control
- consumer-restriction
- cors
- csrf
- datadog
- echo
- error-log-logger
- ext-plugin-post-req
- ext-plugin-post-resp
- ext-plugin-pre-req
- fault-injection
- file-logger
- forward-auth
- google-cloud-logging
- grpc-transcode
- grpc-web
- gzip
- hmac-auth
- http-logger
- ip-restriction
- jwt-auth
- kafka-logger
- kafka-proxy
- key-auth
- ldap-auth
- limit-conn
- limit-count
- limit-req
- loggly
- mocking
- opa
- openid-connect
- opentelemetry
- openwhisk
- prometheus
- proxy-cache
- proxy-control
- proxy-mirror
- proxy-rewrite
- public-api
- real-ip
- redirect
- referer-restriction
- request-id
- request-validation
- response-rewrite
- rocketmq-logger
- server-info
- serverless-post-function
- serverless-pre-function
- skywalking
- skywalking-logger
- sls-logger
- splunk-hec-logging
- syslog
- tcp-logger
- traffic-split
- ua-restriction
- udp-logger
- uri-blocker
- wolf-rbac
- zipkin
- elasticsearch-logge
- openfunction
- tencent-cloud-cls
- ai
- cas-auth
plugin_attr:
log-rotate:
enable_compression: false
max_kept: 3
max_size: 10240
prometheus:
export_addr:
ip: 0.0.0.0
I experienced the same problem.
I experienced the same problem. I found that when requesting the interface "http://locathost:port/apisix/admin/plugins?all=true", the returned response data was null, so the page reported an error and displayed a blank page. Why was the interface response data empty?
ps: Chart.yaml apiVersion: v2 appVersion: 3.0.0 description: A Helm chart for Apache APISIX Dashboard name: apisix-dashboard type: application version: 0.8.1
Experienced the same issue, downgrade to 3.0.0 image resolved the issue and APISIX 3.7.0
Issue description
Console error
Is it not compatible with Apisix 3.2.1
Expected behavior
x
How to Reproduce
http://ip:80/plugin/list
Screenshots
Environment
apisix version
): 3.2.1uname -a
):nginx -V
oropenresty -V
):etcd --version
):Additional context
No response