Cannot connect to Azure Event Hubs with version 3.2.0 #1884
Description
After upgrading Redpanda Console (Windows 11) to v3.2.0 I cannot connect anymore to Azure Event Hubs at all :/
The logs:
{"time":"2025-08-23T16:10:03.337872+02:00","level":"INFO","msg":"started Redpanda Console","version":"3.2.0","built_at":"1755614785"}
{"time":"2025-08-23T16:10:03.3552777+02:00","level":"INFO","msg":"connecting to Kafka seed brokers, trying to fetch cluster metadata","seed_brokers":["pi-ilotto-eh-cat.servicebus.windows.net:9093"]}
{"time":"2025-08-23T16:10:15.355138+02:00","level":"WARN","msg":"failed to test Kafka connection, going to retry in 3s","remaining_retries":1}
{"time":"2025-08-23T16:10:18+02:00","level":"ERROR","msg":"failed to start API","!BADKEY":"start console service: failed to test kafka connectivity: failed to test kafka connection: failed to request metadata: read tcp 192.168.55.30:16141->20.86.89.110:9093: wsarecv: Istniejące połączenie zostało gwałtownie zamknięte przez zdalnego hosta."}Istniejące połączenie zostało gwałtownie zamknięte przez zdalnego hosta is in Polish and means An existing connection has been forcibly closed by the remote host.
My config file is as follows:
kafka:
brokers:
- "pi-ilotto-eh-cat.servicebus.windows.net:9093"
clientId: console-ui
sasl:
enabled: true
username: "$ConnectionString"
password: 'Endpoint=sb://pi-ilotto-eh-cat.servicebus.windows.net/;SharedAccessKeyName=subscribe-only;SharedAccessKey=XXXXXXXXXXXXXXXX'
mechanism: PLAIN
tls:
enabled: true
insecureSkipTlsVerify: true
startup:
maxRetries: 1
retryInterval: 3s
maxRetryInterval: 60s
backoffMultiplier: 2
schemaRegistry:
enabled: false
server:
listenAddress: 0.0.0.0
listenPort: 8181I've verified the connection using kcat and it works fine:
$ kcat -b pi-ilotto-eh-cat.servicebus.windows.net:9093 -L \
-X security.protocol=SASL_SSL \
-X sasl.mechanisms=PLAIN \
-X sasl.username='$ConnectionString' \
-X sasl.password='Endpoint=sb://pi-ilotto-eh-cat.servicebus.windows.net/;SharedAccessKeyName=subscribe-only;SharedAccessKey=XXXXXXXXXXXXXXXX'
Metadata for all topics (from broker 0: sasl_ssl://pi-ilotto-eh-cat.servicebus.windows.net:9093/0):
1 brokers:
broker 0 at pi-ilotto-eh-cat.servicebus.windows.net:9093 (controller)
6 topics:
topic "ewallet" with 1 partitions:
partition 0, leader 0, replicas: , isrs:
topic "financial_transaction" with 1 partitions:
partition 0, leader 0, replicas: , isrs:
topic "game_transaction" with 1 partitions:
partition 0, leader 0, replicas: , isrs:
topic "limit" with 1 partitions:
partition 0, leader 0, replicas: , isrs:
topic "player" with 1 partitions:
partition 0, leader 0, replicas: , isrs:
topic "player_session" with 1 partitions:
partition 0, leader 0, replicas: , isrs:
Furthermore when I downgrade to v3.1.1 it works as well:
{"level":"info","ts":"2025-08-23T16:12:15.928+0200","msg":"started Redpanda Console","version":"3.1.1","built_at":"1747783084"}
{"level":"info","ts":"2025-08-23T16:12:15.949+0200","msg":"connecting to Kafka seed brokers, trying to fetch cluster metadata","seed_brokers":["pi-ilotto-eh-cat.servicebus.windows.net:9093"]}
{"level":"info","ts":"2025-08-23T16:12:16.381+0200","msg":"successfully connected to kafka cluster","advertised_broker_count":1,"topic_count":6,"controller_id":0,"kafka_version":"unknown custom version at least v0.10.2"}
{"level":"info","ts":"2025-08-23T16:12:16.420+0200","msg":"Server listening on address","address":"[::]:8181","port":8181}