Nacos 3.2.1-2026.03.30 与 Higress v2.1.11 兼容性问题 || Nacos 3.2.1-2026.03.30 and Higress v2.1.11 compatibility issues

[Fly-fly-bibiQ]

Nacos 版本 Nacos 3.2.1-2026.03.30
Higress 版本 v2.1.11

在Higress 控制台配置
类型：Nacos 3.x
名称：nacos-registry
注册中心地址: nacos ip
注册中心访问端口: 8848 （默认）
是否开启自定义服务端口：否
是否开启认证：是
Nacos用户名：nacos
Nacos密码：nacos
Nacos命名空间ID： public
Nacos服务分组列表：DEFAULT_GROUP
是否启用MCP Server 功能： 是
Mcp Server路由路径前缀：/mcp

在配置完毕后,Nacos 控制台报出接口404 异常
2026-04-08 15:03:03,435 WARN No mapping for GET /nacos/v1/cs/configs
2026-04-08 15:03:03,435 WARN No endpoint GET /nacos/v1/cs/configs.

经我调查，nacos 在3.2.1-2026.03.30 这个版本的时候，路径由v1升级为v3

我现在不知道是否我调查有问题，还有Higress 与 Nacos 的兼容版本是怎么匹配的

以下是我的 docker-compose.yaml

version: '3.8'

services:
nacos:
image: nacos-registry.cn-hangzhou.cr.aliyuncs.com/nacos/nacos-server:latest
container_name: nacos
environment:
MODE: standalone
NACOS_AUTH_TOKEN: ${NACOS_AUTH_TOKEN}
NACOS_AUTH_IDENTITY_KEY: ${NACOS_AUTH_IDENTITY_KEY}
NACOS_AUTH_IDENTITY_VALUE: ${NACOS_AUTH_IDENTITY_VALUE}
ports:
- "8002:8080"
- "8848:8848"
- "9848:9848"
networks:
- mcp-net
restart: unless-stopped

higress-ai:
image: higress-registry.cn-hangzhou.cr.aliyuncs.com/higress/all-in-one:latest
container_name: higress-ai
volumes:
- ./higress/data:/data
environment:
O11Y: "on"
ports:
- "8001:8001"
- "8080:8080"
- "8443:8443"
networks:
- mcp-net
restart: unless-stopped

higress-redis:
image: higress-registry.cn-hangzhou.cr.aliyuncs.com/higress/redis-stack-server:7.4.0-v3
container_name: higress-redis
ports:
- "6380:6379"
networks:
- mcp-net
restart: unless-stopped

networks:
mcp-net:
name: mcp-net
driver: bridge

---

Nacos version Nacos 3.2.1-2026.03.30
Higress version v2.1.11

Configure in Higress console
Type: Nacos 3.x
Name: nacos-registry
Registration center address: nacos ip
Registration center access port: 8848 (default)
Whether to open a custom service port: No
Whether to enable authentication: Yes
Nacos username: nacos
Nacos password: nacos
Nacos namespace ID: public
Nacos service group list: DEFAULT_GROUP
Whether to enable the MCP Server function: Yes
Mcp Server routing path prefix: /mcp

After the configuration is completed, the Nacos console reports an interface 404 exception.
2026-04-08 15:03:03,435 WARN No mapping for GET /nacos/v1/cs/configs
2026-04-08 15:03:03,435 WARN No endpoint GET /nacos/v1/cs/configs.

After my investigation, when nacos was in version 3.2.1-2026.03.30, the path was upgraded from v1 to v3.

I don’t know now if there is something wrong with my investigation, and how the compatible versions of Higress and Nacos are matched.

The following is my docker-compose.yaml

version: '3.8'

services:
nacos:
image: nacos-registry.cn-hangzhou.cr.aliyuncs.com/nacos/nacos-server:latest
container_name: nacos
environment:
MODE: standalone
NACOS_AUTH_TOKEN: ${NACOS_AUTH_TOKEN}
NACOS_AUTH_IDENTITY_KEY: ${NACOS_AUTH_IDENTITY_KEY}
NACOS_AUTH_IDENTITY_VALUE: ${NACOS_AUTH_IDENTITY_VALUE}
ports:
- "8002:8080"
- "8848:8848"
- "9848:9848"
networks:
-mcp-net
restart: unless-stopped

higress-ai:
image: higress-registry.cn-hangzhou.cr.aliyuncs.com/higress/all-in-one:latest
container_name: higress-ai
volumes:
- ./higress/data:/data
environment:
O11Y: "on"
ports:
- "8001:8001"
- "8080:8080"
- "8443:8443"
networks:
-mcp-net
restart: unless-stopped

higress-redis:
image: higress-registry.cn-hangzhou.cr.aliyuncs.com/higress/redis-stack-server:7.4.0-v3
container_name: higress-redis
ports:
- "6380:6379"
networks:
-mcp-net
restart: unless-stopped

networks:
mcp-net:
name:mcp-net
driver: bridge

[Fly-fly-bibiQ]

==> var/log/higress/gateway.log <==
2026-04-08T08:38:41.544149Z info wasm fetching image mcp-server/all-in-one from registry higress-registry.cn-hangzhou.cr.aliyuncs.com with tag 1.0.0

==> var/log/higress/pilot.log <==
2026-04-08T08:38:41.440742Z info adsc Received type=security.istio.io/v1beta1/AuthorizationPolicy count=0 nonce=8b68c535-65fb-4742-a461-4ba54227ec67
2026-04-08T08:38:41.440915Z info adsc Received type=networking.istio.io/v1alpha3/EnvoyFilter count=3 nonce=536b2e11-65d8-4bf2-a47e-4a4933d6308d
2026-04-08T08:38:41.441094Z info adsc Received type=networking.istio.io/v1beta1/ProxyConfig count=0 nonce=7ea9811d-fffb-45e7-b795-4f4df3413cb3
2026-04-08T08:38:41.441110Z info adsc Received type=telemetry.istio.io/v1alpha1/Telemetry count=0 nonce=58b6c624-9c40-4abf-a95f-442022667497
2026-04-08T08:38:41.441152Z info adsc Received type=security.istio.io/v1beta1/PeerAuthentication count=0 nonce=b032f44f-db89-453e-ba80-61e82f61275e
2026-04-08T08:38:41.441194Z info adsc Received type=networking.istio.io/v1alpha3/VirtualService count=2 nonce=fee25b35-ddca-42f4-956b-067efbf4d682
2026-04-08T08:38:41.441246Z info adsc Received type=extensions.istio.io/v1alpha1/WasmPlugin count=1 nonce=399279b7-3da2-467a-bedd-18cf3adc6ef0
2026-04-08T08:38:41.441303Z info adsc Received type=networking.istio.io/v1alpha3/DestinationRule count=1 nonce=8d194305-1991-4757-a9ab-da544f45d6f4
2026-04-08T08:38:41.441325Z info adsc Received type=networking.istio.io/v1alpha3/Sidecar count=0 nonce=0401475c-b429-4398-ba5c-a777541c0022
2026-04-08T08:38:41.441339Z info adsc Received type=networking.istio.io/v1alpha3/WorkloadEntry count=0 nonce=e6437156-cac2-4b31-9432-7ea9c9bd894a
2026-04-08T08:38:41.441351Z info adsc Received type=networking.istio.io/v1alpha3/WorkloadGroup count=0 nonce=7b7d3714-1c06-4716-9183-b8ea37e4800a
2026-04-08T08:38:41.441426Z info PushRequest generated in configHandler: &model.PushRequest{Full:true, ConfigsUpdated:sets.Set[istio.io/istio/pilot/pkg/model.ConfigKey]{model.ConfigKey{Kind:0x26, Name:"istio-autogenerated-mcp-wasmplugin", Namespace:"higress-system"}:struct {}{}}, Push:(*model.PushContext)(nil), Start:time.Date(1, time.January, 1, 0, 0, 0, 0, time.UTC), Reason:model.ReasonStats{"config":1}, Delta:model.ResourceDelta{Subscribed:sets.Setstring, Unsubscribed:sets.Setstring}}
2026-04-08T08:38:41.441442Z info ads full push happen, reason:map[config:1]
2026-04-08T08:38:41.441913Z info adsc Received type=networking.istio.io/v1alpha3/Gateway count=1 nonce=facabc07-30e3-427d-8133-2974f378ff5f
2026-04-08T08:38:41.441957Z info adsc Received type=security.istio.io/v1beta1/RequestAuthentication count=0 nonce=a4722206-aa9a-41a0-99f8-50d7bb1355e8
2026-04-08T08:38:41.441967Z info adsc Received type=networking.istio.io/v1alpha3/ServiceEntry count=2 nonce=cf5ff6ef-e598-4534-86d9-6338d514becb
2026-04-08T08:38:41.442029Z info serviceentry PushRequest generated in Controller::serviceEntryHandler: &model.PushRequest{Full:true, ConfigsUpdated:sets.Set[istio.io/istio/pilot/pkg/model.ConfigKey]{model.ConfigKey{Kind:0x1e, Name:"nacos-chatbot::1.0.0.mcp-endpoints.public.nacos", Namespace:"mcp"}:struct {}{}}, Push:(model.PushContext)(nil), Start:time.Date(1, time.January, 1, 0, 0, 0, 0, time.UTC), Reason:model.ReasonStats{"service":1}, Delta:model.ResourceDelta{Subscribed:sets.Setstring, Unsubscribed:sets.Setstring}}
2026-04-08T08:38:41.442039Z info ads full push happen, reason:map[service:1]
2026-04-08T08:38:41.442079Z info serviceentry PushRequest generated in Controller::serviceEntryHandler: &model.PushRequest{Full:true, ConfigsUpdated:sets.Set[istio.io/istio/pilot/pkg/model.ConfigKey]{model.ConfigKey{Kind:0x1e, Name:"higress-console.static", Namespace:"mcp"}:struct {}{}}, Push:(model.PushContext)(nil), Start:time.Date(1, time.January, 1, 0, 0, 0, 0, time.UTC), Reason:model.ReasonStats{"service":1}, Delta:model.ResourceDelta{Subscribed:sets.Setstring, Unsubscribed:sets.Setstring}}
2026-04-08T08:38:41.442084Z info ads full push happen, reason:map[service:1]
2026-04-08T08:38:41.542650Z info ads Push debounce stable[87] 3 for config WasmPlugin/higress-system/istio-autogenerated-mcp-wasmplugin and 2 more configs: 100.548513ms since last change, 101.158466ms since last push, full=true
2026-04-08T08:38:41.543266Z info ads XDS: Pushing Services:3 ConnectedEndpoints:1 Version:2026-04-08T08:38:41Z/47
2026-04-08T08:38:41.543461Z info ads CDS: PUSH for node:higress-gateway.higress-system resources:3 size:1.1kB cached:0/2
2026-04-08T08:38:41.543486Z info ads EDS: PUSH INC for node:higress-gateway.higress-system resources:1 size:114B empty:0 cached:0/1
2026-04-08T08:38:41.543740Z info ads LDS: PUSH for node:higress-gateway.higress-system resources:2 size:11.3kB cached:0/0
2026-04-08T08:38:41.543757Z info ads SRDS: PUSH for node:higress-gateway.higress-system resources:2 size:86B
2026-04-08T08:38:41.543766Z warn route cache is disabled for RDS:higress-rds-8443.
2026-04-08T08:38:41.543823Z warn route cache is disabled for RDS:higress-rds-8080.
2026-04-08T08:38:41.543854Z info ads RDS: PUSH for node:higress-gateway.higress-system resources:2 size:4.0kB cached:0/2
2026-04-08T08:38:41.543888Z info ads ECDS: PUSH for node:higress-gateway.higress-system resources:2 size:1.7kB

==> var/log/higress/gateway.log <==
2026-04-08T08:38:42.313466Z warning envoy wasm external/envoy/source/extensions/common/wasm/context.cc:1485 wasm log: [mcp-server] [] [nil] parse rule config failed for rule {"match_route":["istio-autogenerated-mcp-httproute-55b25619-23f3-4eb9-a1bc-65c1c3c73b05"],"allowTools":["chat"],"server":{"config":{"credentials":{}},"name":"nacos-chatbot"},"tools":[{"args":[{"name":"response_mode","required":true,"type":"string"},{"name":"query","required":true,"type":"string"},{"name":"inputs","properties":{},"required":true,"type":"object"},{"name":"conversation_id","required":true,"type":"string"},{"name":"user","required":true,"type":"string"}],"description":"与【HR测试】聊天助手对话","name":"chat","requestTemplate":{"method":"","url":""},"responseTemplate":{},"security":null}]}: failed to add tool chat: direct response mode must set responseTemplate.body, trying to load from backup thread=244
2026-04-08T08:38:42.313510Z error envoy wasm external/envoy/source/extensions/common/wasm/context.cc:1488 wasm log: [mcp-server] [] [nil] failed to load rule from backup, skipping rule: {"match_route":["istio-autogenerated-mcp-httproute-55b25619-23f3-4eb9-a1bc-65c1c3c73b05"],"allowTools":["chat"],"server":{"config":{"credentials":{}},"name":"nacos-chatbot"},"tools":[{"args":[{"name":"response_mode","required":true,"type":"string"},{"name":"query","required":true,"type":"string"},{"name":"inputs","properties":{},"required":true,"type":"object"},{"name":"conversation_id","required":true,"type":"string"},{"name":"user","required":true,"type":"string"}],"description":"与【HR测试】聊天助手对话","name":"chat","requestTemplate":{"method":"","url":""},"responseTemplate":{},"security":null}]} thread=244
2026-04-08T08:38:42.313515Z warning envoy wasm external/envoy/source/extensions/common/wasm/context.cc:1485 wasm log: [mcp-server] [] [nil] parse rule config failed: all rules failed to parse and no previous successful config available thread=244
2026-04-08T08:38:42.313522Z error envoy wasm external/envoy/source/extensions/common/wasm/context.cc:1488 wasm log: [mcp-server] [] [nil] plugin start failed thread=244
2026-04-08T08:38:42.313524Z error envoy wasm external/envoy/source/extensions/common/wasm/wasm.cc:151 Wasm VM failed Failed to configure base Wasm plugin thread=244
2026-04-08T08:38:42.320975Z warning envoy config external/envoy/source/extensions/config_subscription/grpc/grpc_subscription_impl.cc:143 gRPC config for type.googleapis.com/envoy.config.core.v3.TypedExtensionConfig rejected: Unable to create Wasm HTTP filter higress-system.istio-autogenerated-mcp-wasmplugin thread=244
2026-04-08T08:38:42.320982Z warning envoy config external/envoy/source/extensions/config_subscription/grpc/grpc_subscription_impl.cc:143 gRPC config for type.googleapis.com/envoy.config.core.v3.TypedExtensionConfig rejected: Unable to create Wasm HTTP filter higress-system.istio-autogenerated-mcp-wasmplugin thread=244

==> var/log/higress/pilot.log <==
2026-04-08T08:38:42.321317Z warn ads ADS:ECDS: ACK ERROR higress-gateway.higress-system-9 Internal:Unable to create Wasm HTTP filter higress-system.istio-autogenerated-mcp-wasmplugin

==> var/log/higress/apiserver.log <==
I0408 08:38:44.247421 49 file_rest.go:262] [secrets] higress-console got

[CH3CHO]

先解决这个配置问题：

2026-04-08T08:38:42.313466Z warning envoy wasm external/envoy/source/extensions/common/wasm/context.cc:1485 wasm log: [mcp-server] [] [nil] parse rule config failed for rule {"match_route":["istio-autogenerated-mcp-httproute-55b25619-23f3-4eb9-a1bc-65c1c3c73b05"],"allowTools":["chat"],"server":{"config":{"credentials":{}},"name":"nacos-chatbot"},"tools":[{"args":[{"name":"response_mode","required":true,"type":"string"},{"name":"query","required":true,"type":"string"},{"name":"inputs","properties":{},"required":true,"type":"object"},{"name":"conversation_id","required":true,"type":"string"},{"name":"user","required":true,"type":"string"}],"description":"与【HR测试】聊天助手对话","name":"chat","requestTemplate":{"method":"","url":""},"responseTemplate":{},"security":null}]}: failed to add tool chat: direct response mode must set responseTemplate.body, trying to load from backup thread=244

[Fly-fly-bibiQ]

感谢，现在服务能正常从 nacos 获取 对应服务了
但是Nacos端还是会出现以下错误
2026-04-13 09:18:16,424 WARN No mapping for GET /nacos/v1/cs/configs
2026-04-13 09:18:16,424 WARN No endpoint GET /nacos/v1/cs/configs.

我关闭Higress 服务后，该服务的确停止了

[CH3CHO]

两个问题：

1. nacos 地址配的是 8848 端口吧？
2. 看一下 nacos 的 application.properties 文件，nacos.core.api.compatibility.console.enabled=true 这个值对不对

[Fly-fly-bibiQ]

以下是我的 docker compose:

version: '3.8'

services:
nacos:
image: nacos-registry.cn-hangzhou.cr.aliyuncs.com/nacos/nacos-server:latest
container_name: nacos
environment:
MODE: standalone
NACOS_AUTH_TOKEN: ${NACOS_AUTH_TOKEN}
NACOS_AUTH_IDENTITY_KEY: ${NACOS_AUTH_IDENTITY_KEY}
NACOS_AUTH_IDENTITY_VALUE: ${NACOS_AUTH_IDENTITY_VALUE}
ports:
- "8002:8080"
- "8848:8848"
- "9848:9848"
networks:
- mcp-net
restart: unless-stopped

higress-ai:
image: higress-registry.cn-hangzhou.cr.aliyuncs.com/higress/all-in-one:latest
container_name: higress-ai
volumes:
- ./higress/data:/data
environment:
O11Y: "on"
ports:
- "8001:8001"
- "8080:8080"
- "8443:8443"
networks:
- mcp-net
restart: unless-stopped

higress-redis:
image: higress-registry.cn-hangzhou.cr.aliyuncs.com/higress/redis-stack-server:7.4.0-v3
container_name: higress-redis
ports:
- "6380:6379"
networks:
- mcp-net
restart: unless-stopped

networks:
mcp-net:
name: mcp-net
driver: bridge

我需要到哪查看配置文件，从我的compose 来看，我是没有调整过这个参数

[Fly-fly-bibiQ]

我把容器内的参数改变重启后，还是有404的问题

[CH3CHO]

虽然有这个错误，但似乎不影响从 Nacos 里获取 MCP Server 配置这一功能。这个错误请 @rinfx 看一下。CC @EndlessSeeker

---

Although there is this error, it does not seem to affect the function of obtaining MCP Server configuration from Nacos. Please @rinfx take a look at this error. CC @EndlessSeeker