VS Code Extension Not Working Anymore

[mschmitt61]

Type: Bug

Hi, as of the latest VS Code extension update, I cannot get access to my clusters anymore. The extension logs in ok, but fails when trying to load a cluster.
Only error I can see is Response returned an error code.

Extension version: 0.23.3
VS Code version: Code 1.96.3 (Universal) (91fbdddc47bc9c09064bf7acf133d22631cbf083, 2025-01-09T18:14:09.060Z)
OS version: Darwin arm64 24.2.0
Modes:

Confluent Extension + Sidecar Data

Key	Value
extensionVersion	"0.23.3"
extensionActivated	true
sidecarVersion	"0.134.1"
sidecarStartCount	3
ccloudAuthCompleted	true
ccloudAuthExpiration	"2025-01-15T22:00:56.416Z"
ccloudAuthLastSeenStatus	"VALID_TOKEN"
ccloudSignInCount	6
ccloudSignOutCount	4

System Info

Item	Value
CPUs	Apple M1 Pro (8 x 2400)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: enabled video_encode: enabled webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off
Load (avg)	15, 10, 9
Memory (System)	16.00GB (0.08GB free)
Process Argv	--crash-reporter-id 5c367b04-7eb5-4843-a54c-b4f4c675d719
Screen Reader	no
VM	0%

A/B Experiments

vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
vscod805cf:30301675
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythonnoceb:30805159
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
dvdeprecation:31068756
dwnewjupyter:31046869
newcmakeconfigv2:31071590
nativerepl2:31139839
pythonrstrctxt:31112756
nativeloc1:31192215
cf971741:31144450
iacca1:31171482
notype1:31157159
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530
3d9ag387:31215808
6074i472:31201624
dwoutputs:31217127

[mschmitt61]

Sidecar logs

2025-01-15T13:55:41.823Z [debug] [authn.ccloudProvider] handleSessionSecretChange() 
2025-01-15T13:55:41.823Z [debug] [viewProviders.resources] ccloudConnected event fired {"connected":true}
2025-01-15T13:55:41.824Z [debug] [authn.ccloudProvider] handleSessionCreated() {"updateSecret":false}
2025-01-15T13:55:45.376Z [debug] [quickpicks.kafkaClusters] generating Kafka cluster quickpick {"local":0,"ccloud":9,"direct":0}
2025-01-15T13:55:46.883Z [debug] [storage.ccloudResourceLoader] Deep loading schemas for CCloud Schema Registry lsrc-o257yx 
2025-01-15T13:55:47.032Z [error] [sidecar.middlewares] received error response from sidecar {"request":"{\"url\":\"http://127.0.0.1:26636/schemas\",\"method\":\"GET\",\"headers\":{\"Accept\":\"application/json\",\"Content-Type\":\"application/json\",\"Authorization\":\"Bearer Mq...CB\",\"x-cluster-id\":\"lsrc-o257yx\",\"x-connection-id\":\"vscode-confluent-cloud-connection\"}}","response":"{\"status\":500,\"statusText\":\"Internal Server Error\",\"headers\":{},\"body\":\"{\\\"status\\\":\\\"500\\\",\\\"code\\\":\\\"proxy_error\\\",\\\"title\\\":\\\"Something went wrong while proxying request\\\",\\\"id\\\":\\\"ec8d0f2a-9b5d-426f-91af-f1dd6f413660\\\",\\\"errors\\\":[{\\\"code\\\":\\\"proxy_error\\\",\\\"title\\\":\\\"Failed to create SSL connection\\\",\\\"detail\\\":\\\"Failed to create SSL connection\\\"}]}\"}"}
2025-01-15T13:55:47.033Z [error] [storage.ccloudResourceLoader] Error while preloading CCloud schemas {"error":{"response":{},"name":"ResponseError"}}
2025-01-15T13:55:47.109Z [error] [sidecar.middlewares] received error response from sidecar {"request":"{\"url\":\"http://127.0.0.1:26636/kafka/v3/clusters/lkc-0j8519/topics?includeAuthorizedOperations=true\",\"method\":\"GET\",\"headers\":{\"Accept\":\"application/json\",\"Content-Type\":\"application/json\",\"Authorization\":\"Bearer Mq...CB\",\"x-cluster-id\":\"lkc-0j8519\",\"x-connection-id\":\"vscode-confluent-cloud-connection\"}}","response":"{\"status\":500,\"statusText\":\"Internal Server Error\",\"headers\":{},\"body\":\"{\\\"status\\\":\\\"500\\\",\\\"code\\\":\\\"proxy_error\\\",\\\"title\\\":\\\"Something went wrong while proxying request\\\",\\\"id\\\":\\\"eb027976-b3fd-4f1a-b085-0de8c79d2fc7\\\",\\\"errors\\\":[{\\\"code\\\":\\\"proxy_error\\\",\\\"title\\\":\\\"Failed to create SSL connection\\\",\\\"detail\\\":\\\"Failed to create SSL connection\\\"}]}\"}"}
2025-01-15T13:55:51.835Z [debug] [authn.ccloudPolling] checking auth status for CCloud connection {"status":"VALID_TOKEN","expiration":"2025-01-15T21:55:40.816Z"}
2025-01-15T13:55:51.836Z [trace] [utils.timing] pollCCloudConnectionAuth: using slow frequency polling interval {"fastFrequency":"5000ms","slowFrequency":"10000ms"}
2025-01-15T13:55:56.611Z [debug] [docker.configs] failed to load Docker credentials: {"status":1,"signal":null,"output":[null,"credentials not found in native keychain\n",""],"pid":86852,"stdout":"credentials not found in native keychain\n","stderr":""}
2025-01-15T13:55:56.611Z [trace] [docker.configs] using docker socket path: {"socketPath":"/var/run/docker.sock"}
2025-01-15T13:55:56.615Z [debug] [docker.configs] docker ping error: {"cause":{},"name":"FetchError"}
2025-01-15T13:55:56.615Z [debug] [docker.eventListener] dockerAvailable: false
2025-01-15T13:55:56.615Z [trace] [utils.timing] pollDockerEvents: using slow frequency polling interval {"fastFrequency":"1000ms","slowFrequency":"15000ms"}
2025-01-15T13:56:01.840Z [debug] [authn.ccloudPolling] checking auth status for CCloud connection {"status":"VALID_TOKEN","expiration":"2025-01-15T21:55:40.816Z"}
2025-01-15T13:56:01.859Z [trace] [utils.timing] pollCCloudConnectionAuth: using slow frequency polling interval {"fastFrequency":"5000ms","slowFrequency":"10000ms"}
2025-01-15T13:56:11.605Z [debug] [docker.configs] failed to load Docker credentials: {"status":1,"signal":null,"output":[null,"credentials not found in native keychain\n",""],"pid":87825,"stdout":"credentials not found in native keychain\n","stderr":""}
2025-01-15T13:56:11.605Z [trace] [docker.configs] using docker socket path: {"socketPath":"/var/run/docker.sock"}
2025-01-15T13:56:11.607Z [debug] [docker.eventListener] dockerAvailable: false
2025-01-15T13:56:11.607Z [trace] [utils.timing] pollDockerEvents: using slow frequency polling interval {"fastFrequency":"1000ms","slowFrequency":"15000ms"}
2025-01-15T13:56:11.607Z [debug] [docker.configs] docker ping error: {"cause":{},"name":"FetchError"}
2025-01-15T13:56:11.841Z [debug] [authn.ccloudPolling] checking auth status for CCloud connection {"status":"VALID_TOKEN","expiration":"2025-01-15T21:55:40.816Z"}
2025-01-15T13:56:11.842Z [trace] [utils.timing] pollCCloudConnectionAuth: using slow frequency polling interval {"fastFrequency":"5000ms","slowFrequency":"10000ms"}

[flippingbits]

Thanks for reaching out, @mschmitt61!

It seems you have troubles listing the schemas of a SR cluster. I have a couple of questions:

• Are you able to list topics of a Kafka cluster?
• Does the cluster use a private network?
• Do you sit behind a firewall that performs SSL inspection?
• Did you recently change your network setup, like introduce a new firewall product?

[mschmitt61]

Hi,

1. No
2. Yes
3. Yes, certs are loaded via the settings
4. Nope

Worked fine in previous releases, I'll double check internally to see if anything change but nothing to my knowledge.

[flippingbits]

Thanks for the swift feedback!

Worked fine in previous releases, I'll double check internally to see if anything change but nothing to my knowledge.

May I trouble you to check if your certs have changed?

[mschmitt61]

No trouble at all, just checked artifactory and redownloaded the certs, same issue.

[mschmitt61]

Note that the cluster names load in, it only fails when the extension tries to load the topics.

[flippingbits]

Thanks for providing the additional information, @mschmitt61.

For listing clusters, the VS Code extension talks to our control plane. For interacting with clusters, e.g., to list topics or schemas, the VS Code extension talks to our data plane. In your case, the data plane is part of a private network.

For debugging purposes, can you check if you can list topics/schemas after disabling cert validation in the extension settings?

Also, what happens when you do a right click on the SR cluster in the VS Code extension, select "Copy URI", and open that URI in your browser?

[mschmitt61]

Thanks for the help and following up on this!

1. Disabling cert validation does not work.
2. Cluster URI https://lkc-0j8519.dom3g3qm0w2.us-east-1.aws.confluent.cloud:443 which gives a 404 not found.
3. Schema Registry URI https://lkc-0j8519.dom3g3qm0w2.us-east-1.aws.confluent.cloud/ this had a login username/password prompt, we use SSO for login to Confluent Cloud, so no idea what to put there.

[flippingbits]

Just to double check, are you still seeing the same error in the logs after disabling cert validation? Also, do you mind sharing the sidecar logs that you can find in the file $TMPDIR/vscode-confluent-sidecar.log with me? Feel free to send them privately via email to ssprenger (at) confluent (dot) io if you don't feel comfortable sharing them publicly.

I'll try to reproduce this on my side in the meantime.

[mschmitt61]

Sure, just sent the logs to your email address, thank you!

[mschmitt61]

And yes, same error in the logs when disabling cert validation.