zhonghuafy opened a new issue, #25211: URL: https://github.com/apache/shardingsphere/issues/25211
Sharding-Proxy版本：Version: 5.3.2 jdk版本：Java HotSpot(TM) 64-Bit Server VM 18.9 系统：Windows 10 专业版 mysql版本：8.0.26 navicat版本：15.0.9 - Premium 使用命令行可以正常连接Sharding-Proxy：  使用navicat可以测试连接成功：  但是打开连接报错：  server.yaml唯一的配置： ```authority: users: - user: sharding@% password: sharding privilege: type: DATABASE_PERMITTED props: user-database-mappings: sharding@%=sharding_proxy ``` config-sharding.yaml的全部配置： ```databaseName: sharding_proxy dataSources: ds_0: url: jdbc:mysql://127.0.0.1:3306/dn1?serverTimezone=UTC&useSSL=false username: risk password: riskpassword connectionTimeoutMilliseconds: 30000 idleTimeoutMilliseconds: 60000 maxLifetimeMilliseconds: 1800000 maxPoolSize: 50 minPoolSize: 1 ds_1: url: jdbc:mysql://127.0.0.1:3306/dn2?serverTimezone=UTC&useSSL=false username: risk password: riskpassword connectionTimeoutMilliseconds: 30000 idleTimeoutMilliseconds: 60000 maxLifetimeMilliseconds: 1800000 maxPoolSize: 50 minPoolSize: 1 ds_2: url: jdbc:mysql://127.0.0.1:3306/dn4?serverTimezone=UTC&useSSL=false username: risk password: riskpassword connectionTimeoutMilliseconds: 30000 idleTimeoutMilliseconds: 60000 maxLifetimeMilliseconds: 1800000 maxPoolSize: 50 minPoolSize: 1 ds_com: url: jdbc:mysql://127.0.0.1:3306/comm?serverTimezone=UTC&useSSL=false username: risk password: riskpassword connectionTimeoutMilliseconds: 30000 idleTimeoutMilliseconds: 60000 maxLifetimeMilliseconds: 1800000 maxPoolSize: 50 minPoolSize: 1 rules: - !SHARDING tables: auto_main_order: actualDataNodes: ds_${0..2}.auto_main_order databaseStrategy: standard: shardingColumn: partner_id shardingAlgorithmName: boundary-range tableStrategy: none: shardingAlgorithms: boundary-range: type: BOUNDARY_RANGE props: sharding-ranges: 10, 30, ``` 相似问题：[[windows部署shardingsphere-proxy,启动成功，使用navicat连接报错](https://community.sphere-ex.com/t/topic/1175)](https://community.sphere-ex.com/t/topic/1175) -- 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]
