some problem in websocket proxy

[liujun69]

The config in above. Set the cert and websocket address info in upsteam;then set the proxy path and rewrite https in route.
The actual websocket service id wss://ip:port/ws, when visit by 'ws://127.0.0.1:9080/ws', the request reach apisix service but forward error.
2022/07/28 15:24:58 [info] 44#44: *27028 [lua] init.lua:378: http_access_phase(): matched route: {"clean_handlers":{},"createdIndex":34186,"key":"/apisix/routes/418527933334815422","value":{"uri":"/ws","priority":0,"upstream_id":"418527821128794814","name":"mqtt","enable_websocket":true,"id":"418527933334815422","update_time":1658993052,"create_time":1658991687,"status":1,"methods":["GET","POST","PUT","DELETE","PATCH","HEAD","OPTIONS","CONNECT","TRACE"]},"update_count":0,"orig_modifiedIndex":34200,"modifiedIndex":34200,"has_domain":false}, client: 172.18.0.1, server: _, request: "GET /ws HTTP/1.1", host: "172.16.15.131:9080"
2022/07/28 15:24:58 [error] 44#44: *27028 [lua] upstream.lua:555: get_by_id(): failed to find upstream by id: 418527821128794814, client: 172.18.0.1, server: _, request: "GET /ws HTTP/1.1", host: "172.16.15.131:9080"
2022/07/28 15:24:58 [info] 44#44: *27028 client 172.18.0.1 closed keepalive connection

[liujun69]

create a ws proxy is ok, but wss is error and throw failed to find upstream by id: 418527821128794814,is this means already forward but the targt service no response?

[liujun69]

upstream 418527821128794814 is in the dashboard view

[tokers]

In the dashboard view doesn't represent it can be used by APISIX. Please read my last message carefully.

[tzssangglass]

check 418527821128794814 in ETCD

[liujun69]

check 418527821128794814 in ETCD
/apisix/upstreams/
init_dir
/apisix/upstreams/418527821128794814
{"id":"418527821128794814","create_time":1658991621,"update_time":1659325364,"nodes":{"172.16.1.188:15676":1},"timeout":{"connect":30,"send":30,"read":30},"type":"roundrobin","scheme":"https","pass_host":"pass","name":"rabbit","tls":{"client_cert":"xxxx","client_key":"xxxx"},"keepalive_pool":{"idle_timeout":60,"requests":1000,"size":320}}

[liujun69]

The problem is resoved. It caused by the cert content must be started by '-----BEGIN CERTIFICATE-----' and end by '-----END CERTIFICATE-----'