Cursor Tab not working. Usage of HTTP/2 despite having it disabled.

Bug Report
1

Cursor Tab says “Requires Pro (custom model)”, even though I’m logged in and subscribed to Pro.

I’m behind a corporate proxy, which also blocks HTTP/2. I configured certs and proxies correctly and even use win-ca.

But the console output suggests that Cursor Tab is still trying to use HTTP/2, even though I disabled it - which helped getting other Cursor features to work.

image
image1421×340 40.4 KB

2

Hi @PeterKeffer

Have you tried restarting Cursor?

3

Yes, also reinstalled and logout/login to account.

4

You need access to these URLs. Ask your company to add them to the exceptions list.

image
image1728×572 84.1 KB

5

Thanks, but I’m in a big corporation, they wont do that probably. Secondly we are using ZScaler with blocks HTTP/2. Weird thing is that everything besides Cursor Tab works.

6

Maybe that’s not the issue, check your logs just to be sure.

7

You also mentioned getting a warning that a Pro subscription is required. Make sure you’re signed in with the same email address that you used to purchase the subscription.

image
image1146×504 15.2 KB

8

image
image406×117 3.27 KB

I’m signed in with correct account.

Relevant Logs say this:

2024-10-30 13:43:55.399 [error] Error Checking Connection: [canceled] http/2 stream closed with error code CANCEL (0x8)
2024-10-30 13:44:01.053 [error] Error Checking Connection: [canceled] http/2 stream closed with error code CANCEL (0x8)
2024-10-30 13:44:06.083 [error] Error Checking Connection: [canceled] http/2 stream closed with error code CANCEL (0x8)
2024-10-30 13:44:11.193 [error] Error Checking Connection: [canceled] http/2 stream closed with error code CANCEL (0x8)

and 

2024-10-30 13:37:15.147 [error] Failed to check if git graph is enabled [aborted] socket hang up
2024-10-30 13:42:15.245 [error] Failed to check if git graph is enabled [aborted] socket hang up
9

Can you check if there are any errors in the DevTools?

Cursor> Help>Toggle Developer Tools

10

workbench.desktop.main.js:3012 [Extension Host] (node:44240) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to ‘0’ makes TLS connections and HTTPS requests insecure by disabling certificate verification.
(Use Cursor --trace-warnings ... to show where the warning was created)

workbench.desktop.main.js:3012 Error refreshing default models: ConnectError: [invalid_argument] HTTP 400
at Object.F [as unary] (workbench.desktop.main.js:3821:11898)
at async Object.availableModels (workbench.desktop.main.js:266:139385)
at async Be.refreshDefaultModels (workbench.desktop.main.js:3752:3815)

Oh and I’m on Windows, if this is relevant.

11

It seems that your requests are still being blocked by the corporate proxy.