Ssh access to centos 7 without internet connection still fails with version 3.19

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I am using cursor 3.19
currently if I connect to a legacy centos 7 server with internet connection through ssh, it works fine.
But some of my servers (centos7) does not have an internet connection. It seems the cursor server copied over to offline server through ssh does not have the same legacy support.

version 3.09 still works fine with offline legacy servers.

Steps to Reproduce

using cusor 3.19 to connect through ssh to a centos 7 without internet connection, other than the ssh.

Expected Behavior

Fail to connect to target legacy system

Operating System

Windows 10/11

Version Information

Version: 3.19.13 (user setup)
VS Code Extension API: 1.128.0
Commit: dd066f332fcea7382764400fde902f61920648d0
Date: 2026-09-04T17:41:16.065Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 42.10.0
Chromium: 148.0.7778.280
Node.js: 24.18.1
V8: 14.8.178.38-electron.0
xterm.js: 6.1.0-beta.291
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

Yes - Cursor is unusable

5

Hey @S_Wang, thanks for the report,.

You’re right about what’s happening. Cursor 3.10 and later ships a separate “legacy” remote server for older Linux hosts (glibc 2.17 to 2.27, which includes CentOS 7). The install script decides whether to use it by checking for that legacy package from the remote host itself. On a server with no internet access, the check can’t succeed, so it falls back to the regular server package, and the regular package needs glibc 2.28 or newer.

Can you try this?

  1. In Cursor, open Help → About and note the Version (yours is 3.19.13) and the Commit (yours is dd066f332fcea7382764400fde902f61920648d0).

  2. On your Windows PC (which has internet), download this file:
    https://cursor.blob.core.windows.net/remote-releases/3.19.13-dd066f332fcea7382764400fde902f61920648d0/vscode-reh-linux-legacy-x64.tar.gz
    (For future versions, replace the version and commit in the URL with the values from step 1.)

  3. Copy it to the offline server, for example:
    scp vscode-reh-linux-legacy-x64.tar.gz zoo:/tmp/

  4. SSH into the server and run these commands (replace the commit if yours differs):

    D=~/.cursor-server/bin/linux-x64/dd066f332fcea7382764400fde902f61920648d0
rm -rf "$D" && mkdir -p "$D"
tar -xzf /tmp/vscode-reh-linux-legacy-x64.tar.gz -C "$D" --strip-components=1
"$D/node" --version

The last command should print v20.18.2. If it does, the legacy server is in place.

Does the connection come up after this? Let me know, and I’ll share this with the team (it should be easier than this).

7

yes, this works, thanks.
so future upgrade I just need to unzip the legacy files into the commit of new version?

8

Hoping we can make this overall easier, but yes this would be repeatable until it’s addressed.

18

It also happens when the network bandwidth of remote server is low.