Skip to content

After upgrade to 1.106 I'm unable to connect to MCP server #277297

@srdan-bozovic-msft

Description

@srdan-bozovic-msft

Type: Bug

  1. Try to start MCP server.
  2. Observe error
    "Error sending message to https://xxxxxx/: Error: X509 to PEM conversion"

Notes:

  • The issue doesn't reproduce on every machine but on this one does
  • Rolling back to 1.105 mitigates the issue
  • Maybe a coincidence but with 1.106 you are bumping node.js to 22.20 for which major change is OpenSSL library version

VS Code version: Code 1.106.0 (ac4cbdf, 2025-11-11T16:02:25.943Z)
OS version: Windows_NT x64 10.0.26220
Modes:

System Info
Item Value
CPUs 12th Gen Intel(R) Core(TM) i7-1280P (10 x 1997)
GPU Status 2d_canvas: unavailable_software
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: disabled_software
multiple_raster_threads: enabled_on
opengl: disabled_off
rasterization: disabled_software
raw_draw: disabled_off_ok
skia_graphite: disabled_off
trees_in_viz: disabled_off
video_decode: disabled_software
video_encode: disabled_software
vulkan: disabled_off
webgl: unavailable_software
webgl2: unavailable_software
webgpu: unavailable_software
webnn: unavailable_software
Load (avg) undefined
Memory (System) 20.51GB (3.03GB free)
Process Argv --crash-reporter-id b3a4fc07-71a4-4fc4-900a-6027bd72de74
Screen Reader no
VM 0%
Extensions (37)
Extension Author (truncated) Version
azurite Azu 3.35.0
vscode-eslint dba 3.0.16
docker doc 0.18.0
EditorConfig Edi 0.17.4
prettier-vscode esb 11.0.0
copilot Git 1.388.0
copilot-chat Git 0.33.1
go gol 0.50.0
vscode-pr-pinger jri 0.0.6
rustler Mic 0.0.1-preview.37865
vscode-astred ms- 1.2.5
azure-pipelines ms- 1.261.1
azure-dev ms- 0.10.0
vscode-azure-mcp-server ms- 1.0.0
vscode-azurefunctions ms- 1.19.2
vscode-azureresourcegroups ms- 0.11.6
vscode-bicep ms- 0.38.33
vscode-containers ms- 2.3.0
vscode-docker ms- 2.0.0
csdevkit ms- 1.80.2
csharp ms- 2.100.5
vscode-dotnet-runtime ms- 2.3.7
debugpy ms- 2025.16.0
python ms- 2025.18.0
vscode-pylance ms- 2025.9.1
vscode-python-envs ms- 1.12.0
semantic-kernel ms- 0.13.0
remote-containers ms- 0.431.0
remote-wsl ms- 0.104.3
cmake-tools ms- 1.21.36
cpptools ms- 1.28.3
cpptools-extension-pack ms- 1.3.1
extension-test-runner ms- 0.0.12
makefile-tools ms- 0.12.17
vscode-github-issue-notebooks ms- 0.0.134
rust-analyzer rus 0.3.2675
cmake twx 0.0.17

(1 theme extensions excluded)

A/B Experiments
vsliv368:30146709
binariesv615:30325510
nativeloc1:31344060
dwcopilot:31170013
dwoutputs:31242946
copilot_t_ci:31333650
e5gg6876:31282496
pythonrdcb7:31342333
aj953862:31281341
nes-set-on:31351930
onetestforazureexpcf:31335614
6abeh943:31336334
envsactivate1:31353494
c12345:31413568
0574c672:31404437
f1c06875:31397863
cloudbuttont:31379625
todos-1:31405332
v66_all_req:31402695
control_gpt5applypatchexclusively:31412085
3efgi100_wstrepl:31403338
trigger-command-fix:31379601
auto_model_enabled:31396818
use-responses-api:31390855
sonnet_45_3e700918:31415506
je187915:31401257
v2prompt_9f72f763:31415580
d5i5i512:31405346
agentic_ask_h7d75428:31408710
ec5jj548:31418076
copilot-nes-oct-t:31418199
ff8f5884:31411053
defaulttokens:31418011

Metadata

Metadata

Labels

bugIssue identified by VS Code Team member as probable buginsiders-releasedPatch has been released in VS Code InsidersnetworkNetwork related issuesunder-discussionIssue is under discussion for relevance, priority, approachverifiedVerification succeeded

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions