Connection failed 0.43.5 orz

Bug Report
1

When using agent mode, it displays a connection failure, with the request ID being 804bb3f9-e97f-423a-b9d3-7716250b84d1
And in the same network conditions, normal mode operates without any issues

2

Hey,

The agent mode uses HTTP/2 which is a network protocol that many VPNs and firewall do not like.
Can you confirm if you are working behind a VPN or inside the network of a company, as this would be the most likely cause.

4

Thanks for your reply; I tried the following methods later, but the agent mode still doesn’t work

  1. “api2.cursor.sh”,
    “api3.cursor.sh”,
    “repo42.cursor.sh”,
    “api4.cursor.sh”,
    “us-asia.gcpp.cursor.sh”,
    “us-eu.gcpp.cursor.sh”,
    “us-only.gcpp.cursor.sh”
    The status values ​​returned by these addresses using http/2 are all 200

  2. I tried turning off the VPN and firewall and switching the network, but the result is still connection failed …

5

Do you have another Request ID you can send over, like the one in your original post? I can hopefully dig into that to see what’s going on behind the scenes!

6

Sure, thank you
I have two network connections, so I listed both cases

1
b437d41a-b0d1-4a57-85f6-5cdd9309298b

ad9ee402-506a-43ef-85ea-38de42f90a27

2
Request ID: 54c28901-9484-42e6-aa09-f1042ea04b96

ca6fa1eb-a981-45bb-8555-402c53492706

7

This issue continues to happen to me but in every composer mode, not just agent.

I have tried http2 enabled and disabled, reloading the window, restarting the chat.

I have NO vpn, NO proxy, NO corporate anything, just straight at&t fiber to my single default configuration home router. It used to work fine but for weeks it has refused all connections. No changes to my network or local laptop configuration. Very frustrating not to be able to use the product for this monthly price point :frowning:

1 Like
8

How are things progressing? THANKS