Dev containers extension > 1.0.15 and remote ssh extension > 1.0.21 do not allow me to connect to a running container

Bug Reports
1

Describe the Bug

When connecting to a dev container using a remote Docker installation with versions of the dev containers extension newer than 1.0.15 and the remote ssh extension newer than 1.0.21 results in:

2025-07-19 14:55:14.830 [error] Failed to connect to Cursor server from the client, attempt 3 of 3 This operation was aborted
2025-07-19 14:55:14.830 [error] Error resolving dev container authority Failed to connect to Cursor server from the client
2025-07-19 14:55:14.839 [info] [tunnel-forwarding] stdout: forwarder: handleClient subprocess exited with code null and signal SIGTERM
forwarder: handleClient subprocess closed

2025-07-19 14:55:15.831 [info] [tunnel-forwarding] stdout: forwarder: handleClient subprocess exited with code null and signal SIGTERM
forwarder: handleClient subprocess closed

2025-07-19 14:55:18.845 [info] [tunnel-forwarding] stdout: forwarder: handleClient subprocess exited with code null and signal SIGTERM
forwarder: handleClient subprocess closed

Steps to Reproduce

  • Start a container on a remote machine
  • Create a docker context targeting that machine and enable it
  • Install versions 1.0.17 of the dev containers extension by Anysphere and version 1.0.22 of the remote ssh extension by Anisphere
  • Attempt to connect to the container you created in the first step from Cursor

Expected Behavior

Connection is successful.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.2.4 (user setup)
VSCode Version: 1.99.3
Commit: a8e95743c5268be73767c46944a71f4465d05c90
Date: 2025-07-10T17:09:01.383Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100

Does this stop you from using Cursor

Yes - Cursor is unusable

3

Downgraded to 1.0.15 and 1.0.21 of the extensions to be able to continue using Cursor for now.

5

Hi @Julien_Debache, thank you for this bug report. We added a connection check in version 1.0.16 of the Remote Containers extension that inadvertently caused a timeout and connection failures. We have removed this check in version 1.0.18 of the extension. Could you try upgrading and share whether that fixes it? Apologies for this regression.

6

Hello @ravirahman , thanks for the follow up. I will test it in the coming days.

Might I suggest having a test covering that flow? :wink:. It is very costly in terms of time and frustration to encounter an issue such as this one.

8

@ravirahman I’ve tried dev containers 1.0.20 and remote - ssh 1.0.23 and this is still happening.

10

Hi @MirkoA, could you share your logs from the “Remote - SSH” and “Remote - Dev Containers” output windows so we can take a closer look?

11

Sorry, I’ve already downgraded to earlier versions. The error I was getting was very similar to the one in this Bug Report (Anysphere Devcontainer extension: Error resolving dev container authority [devcontainer up]) - “error resolving dev container authority”, but I’m not using docker compose.

13

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.