I’m not getting any specific error message. However, I’m unable to use Cursor at all

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

           As mentioned, I’m not getting any specific error message. However, I’m unable to use Cursor at all — when I type in the editor, nothing happens and no actions are performed.

I’ve already tried logging out and logging back in, as well as using different devices, but the issue persists. The application opens, but it is completely unresponsive and I cannot do any work.
Please let me know what further information or screenshots you need from my side to help resolve this issue.

Please review this video: Nginx app loading issue - 18 December 2025 | Loom

Steps to Reproduce

when I type in the editor, nothing happens and no actions are performed.

Expected Behavior

Noting happen and it will return noting.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Cursor

Version: 2.2.36 (user setup)
VSCode Version: 1.105.1
Commit: 55c9bc11e99cedd1fb93fbb7996abf779c583150
Date: 2025-12-18T06:25:21.733Z (3 hrs ago)
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26100

For AI issues: which model did you use?

all

Does this stop you from using Cursor

Yes - Cursor is unusable

Hi @Vinayak_Pandya,

Thanks for reporting this!

As a first step, could you run Network Diagnostics (docs) and let me know if everything passes?

If it does, please also grab a Request ID so we can check whether the request is reaching our servers.

Finally, if you’re able to try a specific model instead of Auto, that would help us narrow things down.

1 Like

In the network diagnostics all thinks are pass, i can not find the
can not pass request so how i find the request, and now i am using the sonnet 4.5

Thanks.

a514a68d-2418-492b-a49c-b3f241e23e8c

this is the request id. @Colin

Hey @Vinayak_Pandya,

On my end, I can see that the connection was ended prematurely by the client (your side). This likely wasn’t intentional, it’s probably something related to your environment.

A couple of things to try:

  • Check your upload speed. We sometimes see this error when upload speeds are very slow.
  • Switch to HTTP/1.1 compatibility mode. Even though your network diagnostics show HTTP/2 working, it’s worth trying this to rule it out.

@Colin I have check in HTTP/1.1 and it is working fine also i check my upload speeds and it is more than enough also in my company all people use this same network and they have not face this issue kindly give another suggestion or look in to this matter.

same problem

Hey @Vinayak_Pandya and @Ada_Will

Can you let me know if you’re still experiencing this issue with the latest version of Cursor? Please also make sure that all outstanding invoices are paid in your dashboard.