Since the last update (skipped v3.10) I lost the access to my remote server (CentOS7 + Nodejs16).
Is this a feature that Cursor no longer supports old Node?
If so, that will be sad, and I have to stay at v3.9.
Hey, thanks for the request. This isn’t about Node 16 on the host. The remote cursor-server ships with its own Node runtime, so the Node version on the server doesn’t matter here.
The real reason is that starting in 3.10 the remote server requires glibc >= 2.28. CentOS 7 comes with glibc 2.17, which is below that, so the server install fails. Upstream VS Code made the same change for their server. In 3.9 the remote server used an older Node/base where CentOS 7 still met the requirements, so it works there.
Your options right now:
- Stay on the working version 3.9 and disable auto-update: Settings →
update.mode=none. - Or upgrade the OS on the remote host to glibc 2.28+ (RHEL 8 / Ubuntu 20.04+ / Amazon Linux 2023). That’s the most reliable path.
One more thing: make sure you’re using the Anysphere Remote-SSH extension, not the Microsoft one.
About older systems like CentOS 7, we’re looking at compatibility, but I can’t share an ETA right now. If upgrading the host isn’t an option, reply and we can dig into the details. Related discussion here: Cursor3.9 works fine but 3.10 not works on ssh to ubuntu18.04