MQTT Data Bridge configuration error

Hi
When I am trying to configure MQTT Data bridge over EMQX V5.2.1 GUI, its failing during test connectivity with error message “400 TEST Failed: closed”.
I am passing all the correct values like MQTT Broker details, Key and Certificates.
Please provide your help on this.

Note: my EMQX installation through helm over Kubernetes cluster.

Sharing logs for more details

23-10-25T12:49:45.145723+00:00 [error] msg: start_ecpool_error, mfa: emqx_resource_pool:start/3, line: 51, pool_name: <<“bridge:mqtt:device_session:egress”>>, reason: closed
2023-10-25T12:49:45.145924+00:00 [warning] msg: start_resource_failed, mfa: emqx_resource_manager:start_resource/2, line: 494, id: <<“bridge:mqtt:device_session”>>, reason: closed
2023-10-25T12:50:00.674785+00:00 [warning] msg: egress_client_connect_failed, mfa: emqx_bridge_mqtt_egress:connect/2, line: 95, name: <<“bridge:mqtt:device_session:egress”>>, reason: closed
2023-10-25T12:50:00.675073+00:00 [error] Supervisor: {<0.4472.0>,ecpool_worker_sup}. Context: start_error. Reason: closed. Offender: id={worker,1},pid=undefined.
2023-10-25T12:50:00.675175+00:00 [error] crasher: initial call: ecpool_worker:init/1, pid: <0.4473.0>, registered_name: , exit: {closed,[{gen_server,init_it,6,[{file,“gen_server.erl”},{line,835}]},{proc_lib,init_p_do_apply,3,[{file,“proc_lib.erl”},{line,240}]}]}, ancestors: [<0.4472.0>,<0.4470.0>,ecpool_sup,<0.2646.0>], message_queue_len: 1, messages: [{‘EXIT’,<0.4474.0>,{shutdown,closed}}], links: [<0.4472.0>], dictionary: , trap_exit: true, status: running, heap_size: 1598, stack_size: 28, reductions: 3396; neighbours:
2023-10-25T12:50:00.675553+00:00 [error] Supervisor: {<0.4470.0>,ecpool_pool_sup}. Context: start_error. Reason: {shutdown,{failed_to_start_child,{worker,1},closed}}. Offender: id=worker_sup,pid=undefined.
2023-10-25T12:50:00.677426+00:00 [error] msg: start_ecpool_error, mfa: emqx_resource_pool:start/3, line: 51, pool_name: <<“bridge:mqtt:device_session:egress”>>, reason: closed

emqxConfig:
EMQX_BRIDGES__MQTT__DEVICE_SESSION__ENABLE: “true”
EMQX_BRIDGES__MQTT__DEVICE_SESSION__SERVER: “:”
EMQX_BRIDGES__MQTT__DEVICE_SESSION__USERNAME: “”
EMQX_BRIDGES__MQTT__DEVICE_SESSION__PASSWORD: “”
EMQX_BRIDGES__MQTT__DEVICE_SESSION__KEEPALIVE: “400s”
EMQX_BRIDGES__MQTT__DEVICE_SESSION__CLEAN_START: “false”
EMQX_BRIDGES__MQTT__DEVICE_SESSION__EGRESS__REMOTE__TOPIC: “device-session”
EMQX_BRIDGES__MQTT__DEVICE_SESSION__EGRESS__REMOTE__QOS: “1”
EMQX_BRIDGES__MQTT__DEVICE_SESSION__SSL__ENABLE: “true”
EMQX_BRIDGES__MQTT__DEVICE_SESSION__SSL__CACERTFILE: “c/Users/pandeyvi2/cacer.pem”
EMQX_BRIDGES__MQTT__DEVICE_SESSION__SSL__CERTFILE: “c/Users/pandeyvi2/cert.pem”
EMQX_BRIDGES__MQTT__DEVICE_SESSION__SSL__KEYFILE: “c/Users/pandeyvi2/key.pem”
EMQX_RULE_ENGINE__RULES__RULE_SESSION__ENABLE: “true”
EMQX_RULE_ENGINE__RULES__RULE_SESSION__SQL: SELECT * FROM ‘$events/client_connected’, ‘$events/client_disconnected’
EMQX_RULE_ENGINE__RULES__RULE_SESSION__ACTIONS:
- “mqtt:device_session”