Hello I am currently trying to start a dubbo-provider springboot service on *http* protocol on port 20880. However, the startup logs indicate that this service is not actually being started on the http protocol, but instead on the dubbo protocol.
For reference, I am following the instructions provided by this guide by Alibaba <https://www.alibabacloud.com/blog/high-performance-and-user-friendly-http-access-with-dubbo3_601460> under the section *Access Methods for Different RPC Protocols -> Dubbo Protocol Access Method -> Support for Both HTTP and Dubbo Protocols* Listed below are the steps that I am following: 1. *Clone the dubbo samples <https://github.com/apache/dubbo-samples> repo and use the project 1-basic/dubbo-samples-springboot <https://github.com/apache/dubbo-samples/tree/master/1-basic/dubbo-samples-spring-boot>. *Add the below section to the *application.yml* file. *dubbo: application: name: dubbo-springboot-demo-provider qos-enable: false protocol: name: dubbo port: 20880 ext-protocol: tri registry: address: nacos://<nacos-uuid>.nacos.<nacos-domain>:8848?username=nacos&password=nacos* *2. Build the jar and then the docker image, and deploy to the kubernetes cluster.* *Observations in **Startup Logs* In the startup logs (i*n italics below) *the url *dubbo://172.22.0.18:20880/org <http://172.22.0.18:20880/org>* indicates that the service has still started on the dubbo protocol and NOT the http protocol. *[DUBBO] Register dubbo service org.apache.dubbo.springboot.demo.DemoService url dubbo://172.22.0.18:20880/org <http://172.22.0.18:20880/org>.apache.dubbo.springboot.demo.DemoService?anyhost=true&application=dubbo-springboot-demo-provider&background=false&bind.ip=172.22.0.18&bind.port=20880&deprecated=false&dubbo=2.0.2&dynamic=true&executor-management-mode=isolation&ext.protocol=tri&file-cache=true&generic=false&interface=org.apache.dubbo.springboot.demo.DemoService&ispuserver=true&methods=sayHello&pid=1&prefer.serialization=hessian2,fastjson2&qos.enable=false&release=3.3.1&revision=1.0-SNAPSHOT&service-name-mapping=true&side=provider×tamp=1730177244898 to registry <nacos-registry-uid>.nacos.<rest-of-domain>:8848, dubbo version: 3.3.1, current host: 172.22.0.18* Per my understanding, setting *ext-protocol *and *qos-enable *should be enough to start the service on http. Is there any additional configuration or code change that is needed ? -- Best Tanmay
