Repository navigation
remote extension host terminated unexpectedly 3 times within the last 5 minutes. #7907
Description
Activity
- addedbugSomething isn't workingSomething isn't workingtriageThis issue needs to be triaged by a maintainerThis issue needs to be triaged by a maintainer
on Jul 24, 2026 - addedneeds-investigationThis issue needs to be further investigatedThis issue needs to be further investigated
on Jul 24, 2026 So I was desperate to get some work done. I went in and downloaded the
codeCLI and set up a tunnel throughvscode.dev. I'm experiencing the exact same issue runningcode tunnelon my remote machine. It's an LXC container if that matters.If you get the same issues with
codeit is probably a problem with core VS Code or VS Code web and you might get better support at the upstream repo: https://github.com/microsoft/vscode (code-server just wraps VS Code after doing a bit of patching).That said, it looks like a certificate issue with your remote machine. Does disabling telemetry help at all? It looks like an extension is trying to hit telemetry endpoints. If you want to keep it enabled, do you have certificates installed on the machine? On Ubuntu I think this would look something like (untested):
sudo apt install ca-certificates sudo update-ca-certificates # not sure if this is requiredBut the altname errors could be unrelated to the JSON error, so this might not help.
Hello @code-asher
I am facing the same issue with the same error while building Code Server as a Docker image inside a Linux container.
I am currently using version 4.126.0. Do I need to upgrade to the latest version (4.130.0)? Is there a fix for this issue?
Thanks,
You get the same certificate errors? Did you try disabling telemetry?
If you are able to provide the Dockerfile I can run it and see if I get the same error.
Its not about the certificate, i have the same refresh and reconnection with the same error message [08:49:08] [127.0.0.6][76447ada][ExtensionHostConnection] <306> Extension Host Process exited with code: , signal: null.
and yes, the telemetry is disabled :
/app/code-server/bin/code-server
--user-data-dir /home/project/code-server/data
--extensions-dir /home/project/code-server/extensions
--disable-telemetry \Full log:
[07:21:59] [127.0.0.6][76447ada][ExtensionHostConnection] <306> Launched Extension Host Process.
[07:21:59] [127.0.0.6][76447ada][ExtensionHostConnection] <306> [reconnection-grace-time] Extension host: read VSCODE_RECONNECTION_GRACE_TIME=10800000ms (10800s)
[07:32:05] [127.0.0.6][56c4d7bb][ManagementConnection] New connection established.
[07:32:06] [127.0.0.6][b65eb7d1][ExtensionHostConnection] New connection established.
[07:32:06] [127.0.0.6][b65eb7d1][ExtensionHostConnection] Starting extension host process...
[07:32:06] [127.0.0.6][b65eb7d1][ExtensionHostConnection] <4160> Launched Extension Host Process.
[07:32:06] [127.0.0.6][b65eb7d1][ExtensionHostConnection] <4160> [reconnection-grace-time] Extension host: read VSCODE_RECONNECTION_GRACE_TIME=10800000ms (10800s)
[07:32:08] RequestStore#acceptReply was called without receiving a matching request 37
[07:32:08] RequestStore#acceptReply was called without receiving a matching request 38
[07:32:08] RequestStore#acceptReply was called without receiving a matching request 39
[07:32:08] RequestStore#acceptReply was called without receiving a matching request 40
[07:32:08] RequestStore#acceptReply was called without receiving a matching request 41
[07:32:08] RequestStore#acceptReply was called without receiving a matching request 42
[07:32:08] RequestStore#acceptReply was called without receiving a matching request 43
[07:32:08] RequestStore#acceptReply was called without receiving a matching request 44
[07:32:08] RequestStore#acceptReply was called without receiving a matching request 45
[07:32:08] RequestStore#acceptReply was called without receiving a matching request 46
[07:32:08] RequestStore#acceptReply was called without receiving a matching request 47
[07:32:08] RequestStore#acceptReply was called without receiving a matching request 48
[07:32:08] RequestStore#acceptReply was called without receiving a matching request 49
[07:32:08] RequestStore#acceptReply was called without receiving a matching request 50
[07:32:08] RequestStore#acceptReply was called without receiving a matching request 51
[07:32:08] RequestStore#acceptReply was called without receiving a matching request 52
[07:32:08] RequestStore#acceptReply was called without receiving a matching request 53
[07:32:08] RequestStore#acceptReply was called without receiving a matching request 54
[07:32:08] RequestStore#acceptReply was called without receiving a matching request 55
[07:32:08] RequestStore#acceptReply was called without receiving a matching request 56
[07:32:08] RequestStore#acceptReply was called without receiving a matching request 57
[07:32:08] RequestStore#acceptReply was called without receiving a matching request 58
[07:32:08] RequestStore#acceptReply was called without receiving a matching request 59
[07:32:08] RequestStore#acceptReply was called without receiving a matching request 60
[07:32:11] [127.0.0.6][bf58ad1d][ManagementConnection] The client has disconnected gracefully, so the connection will be disposed.
[08:44:06] [127.0.0.6][56c4d7bb][ManagementConnection] The client has reconnected.
[08:44:06] [127.0.0.6][b65eb7d1][ExtensionHostConnection] The client has reconnected.
[08:49:08] [127.0.0.6][76447ada][ExtensionHostConnection] <306> Extension Host Process exited with code: , signal: null.Hmm I am not sure, might be a different bug. I think it is probably a core VS Code issue rather than something in code-server, although it is not impossible our patches messed something up.
Does it happen without any extensions installed?
If you add
--log-level debug(or maybe evenverbose) then we might get more logs about what is going on.
Is there an existing issue for this?
OS/Web Information
code-server --version: 4.130.0 197ef3e with Code 1.130.0Steps to Reproduce
Expected
Extensions should initialize without issue.
Actual
The failure happens all on its own.
Logs
Screenshot/Video
Does this bug reproduce in native VS Code?
I did not test native VS Code
Does this bug reproduce in VS Code web?
I did not test VS Code web
Does this bug reproduce in GitHub Codespaces?
I did not test GitHub Codespaces
Are you accessing code-server over a secure context?
Notes
I looked up this specific issue and found this but the underlying issue seemed different and their solution didn't work for me.
I had a number of third party extensions installed including Intelephense. In diagnosing this issue I disabled all third party extensions and the problem still exists.
I've also tried with other workspaces and project directories.