# No response to prompts due to 'Internal Server Error'

**URL:** <https://forum.cursor.com/t/no-response-to-prompts-due-to-internal-server-error/165058>\
**Category:** Help\
**Created:** [July 7, 2026, 5:52pm UTC](https://forum.cursor.com/t/no-response-to-prompts-due-to-internal-server-error/165058 "2026-07-07T17:52:43Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![amrapali.srivastava](https://avatars.discourse-cdn.com/v4/letter/a/6a8cbe/32.png) [@amrapali.srivastava](https://forum.cursor.com/u/amrapali.srivastava)\
**Post date:** [July 7, 2026, 5:52pm UTC](https://forum.cursor.com/t/no-response-to-prompts-due-to-internal-server-error/165058/1 "2026-07-07T17:52:43Z")

</div>

Request ID: f5090626-0ec8-45d5-a72d-08231727c7bb  
[internal] Protocol error  
RetriableError: [internal] Protocol error  
at udf (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9066:9690)  
at Hqi (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9066:8425)  
at Scp (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9067:11962)  
at Object.classify (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9067:16467)  
at pdf (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9067:5856)  
at async fWo.runWithSharedTurnRunner (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9067:15819)  
at async xV.runAgentLoop (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:20459:3067)  
at async aba.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:20487:14009)  
at async aba.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:20487:23432)  
at async jIe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9229:2399)

Version: 3.10.17 (Universal)  
VS Code Extension API: 1.125.0  
Commit: c89f45b831621cdc5e951694db44fecd8fab1150  
Date: 2026-07-05T06:39:45.228Z  
Layout: IDE  
Build Type: Stable  
Release Track: Default  
Electron: 40.10.3  
Chromium: 144.0.7559.236  
Node.js: 24.15.0  
V8: 14.4.258.32-electron.0  
xterm.js: 6.1.0-beta.256  
OS: Darwin arm64 25.5.0

---

<div class="post-metadata">

**Author:** ![amrapali.srivastava](https://avatars.discourse-cdn.com/v4/letter/a/6a8cbe/32.png) [@amrapali.srivastava](https://forum.cursor.com/u/amrapali.srivastava)\
**Post date:** [July 7, 2026, 5:53pm UTC](https://forum.cursor.com/t/no-response-to-prompts-due-to-internal-server-error/165058/4 "2026-07-07T17:53:15Z")

</div>

![Screenshot 2026-07-07 at 11.22.26 PM](https://us1.discourse-cdn.com/cursor1/original/3X/2/c/2c65a7dd2dab737dd5a6d18c4f416f2b9d97a9e3.png)

---

<div class="post-metadata">

**Author:** ![kevinn](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/kevinn/32/101206_2.png) [@kevinn](https://forum.cursor.com/u/kevinn)\
**Post date:** [July 7, 2026, 6:02pm UTC](https://forum.cursor.com/t/no-response-to-prompts-due-to-internal-server-error/165058/7 "2026-07-07T18:02:21Z")

</div>

Hi @amrapali.srivastava Thank you for the forum post. The failure here is a “Protocol error,” meaning the connection carrying your request was interrupted or the response got corrupted in transit. We looked up that request ID and it never registered on our end, which points to the request being dropped on the network path between Cursor and our servers rather than a fault on our side.

Since this is network-level, the best steps to narrow it down:

- Run Cursor Settings \> Network \> Run Diagnostics and review the results.
- Test on a different network (like a personal hotspot) to see if it clears. This pattern often comes from a corporate proxy, VPN, firewall, or TLS-inspection tool interfering with the streaming (HTTP/2) connection.
- Confirm Cursor’s domains are allowed through any proxy or firewall. Our guide covers the common fixes: [Network, proxy, and remote connections | Cursor Docs](https://cursor.com/help/troubleshooting/network)
- If it persists, reply with the diagnostics output and a fresh request ID and we’ll keep digging.

Since it sounds like you’re in a managed enterprise environment, it may also help to loop in your IT/network team, as proxy or firewall rules are a common cause.

---

<div class="post-metadata">

**Author:** ![amrapali.srivastava](https://avatars.discourse-cdn.com/v4/letter/a/6a8cbe/32.png) [@amrapali.srivastava](https://forum.cursor.com/u/amrapali.srivastava)\
**Post date:** [July 7, 2026, 6:13pm UTC](https://forum.cursor.com/t/no-response-to-prompts-due-to-internal-server-error/165058/8 "2026-07-07T18:13:57Z")

</div>

Thanks Kevin. Turns out the latest cursor version is not working with the enterprise firewall. Changing HTTP compatibility from HTTP/2 to HTTP/1.1 worked for me.

---

<div class="post-metadata">

**Author:** ![kevinn](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/kevinn/32/101206_2.png) [@kevinn](https://forum.cursor.com/u/kevinn)\
**Post date:** [July 7, 2026, 6:38pm UTC](https://forum.cursor.com/t/no-response-to-prompts-due-to-internal-server-error/165058/10 "2026-07-07T18:38:53Z")

</div>

Great! Thank you very much for circling back and confirming the fix.

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [September 3, 2026, 8:13pm UTC](https://forum.cursor.com/t/no-response-to-prompts-due-to-internal-server-error/165058/13 "2026-09-03T20:13:15Z")

</div>

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