shancw opened a new issue, #15281: URL: https://github.com/apache/dubbo/issues/15281
### Pre-check - [x] I am sure that all the content I provide is in English. ### Search before asking - [x] I had searched in the [issues](https://github.com/apache/dubbo/issues?q=is%3Aissue) and found no similar issues. ### Apache Dubbo Component Java SDK (apache/dubbo) ### Dubbo Version 使用JDK17，Dubbo3.3.0，Nacos2.5.0 ` <dependency> <groupId>org.apache.dubbo</groupId> <artifactId>dubbo-spring-boot-starter</artifactId> <version>3.3.0</version> </dependency> <dependency> <groupId>org.apache.dubbo</groupId> <artifactId>dubbo-nacos-spring-boot-starter</artifactId> <version>3.3.0</version> </dependency> <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-openfeign</artifactId> <version>4.1.3</version> </dependency> ` ### Steps to reproduce this issue 在官网《微服务最佳实践，零改造实现 Spring Cloud & Apache Dubbo 互通》一文中，实操时报错，Dubbo调用Feign接口出现 No provider available from registry RegistryDirectory(registry: 127.0.0.1:8848)-Directory(invokers: 0[], validInvokers: 0[], invokersToReconnect: 0[]) for service com.dubbo.nacos.consumer.client.EchoService on consumer 192.168.0.6 use dubbo version 3.3.0, please check status of providers(disabled, not registered or in blocklist).，无论是自己搭建的还是直接使用**文中案例项目**都无法请求成功 ### What you expected to happen Nacos注册也是成功的，Feign相互调用也是好的 ### Anything else _No response_ ### Are you willing to submit a pull request to fix on your own? - [x] Yes I am willing to submit a pull request on my own! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
