panta82
(Ivan Pantic)
December 4, 2025, 6:53am
1
Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
I’ve tried many times to complete Cursor Cloud VM setup according to this guide: Cloud Agents | Cursor Docs
But it always gets stuck on the “Validate Setup” step.
Output:
[Status] Creating testing environment... (Snapshot ID: snapshot-20251130-fdfb986c-1374-43a0-XXX-XXX, Request ID: 69306564-d409-4c05-8b0f-7a8d6a5abf24)
[Warning] Failed to create testing environment: [unavailable] HTTP 502
[Retry] Retrying in 2 seconds (Attempt 2/3)...
[Status] Creating testing environment... (Attempt 2/3) (Snapshot ID: snapshot-20251130-fdfb986c-1374-43a0-XXX-XXX, Request ID: bb311c9c-fa6f-4c10-8364-ae5dae2e1ddf)
[Warning] Failed to create testing environment: [unavailable] HTTP 504
[Retry] Retrying in 2 seconds (Attempt 3/3)...
[Status] Creating testing environment... (Attempt 3/3) (Snapshot ID: snapshot-20251130-fdfb986c-1374-43a0-XXX-XXX, Request ID: 4abd8a56-113a-4f91-95d7-e3603d4faae0)
[STATUS UPDATE] failed
[Error] Failed to create testing environment after 3 attempts: [unavailable] HTTP 504
(I selected “Cursor is unusable” to mean the cloud product is unusable)
Steps to Reproduce
Setup the ubuntu environment with config files and postgresql DB, then proceed down the next steps in the wizard
Operating System
Linux
Current Cursor Version (Menu → About Cursor → Copy)
Version: 2.1.44
VSCode Version: 1.105.1
Commit: f6a8593b2b7c61c2063c79d5a8fcd248c9db4580
Date: 2025-12-01T22:52:09.315Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Linux x64 6.14.0-33-generic
Does this stop you from using Cursor
Yes - Cursor is unusable
deanrie
(Dean Rie)
December 4, 2025, 10:53am
2
Hey, thanks for the report. I see 502/504 on the “Validate Setup” step during “Creating testing environment…”. Can we gather more data?
Please attach:
.cursor/environment.json
Exact install/start/terminals commands (and how long they usually take locally)
Do you use Secrets in Settings → Cloud Agents → Secrets
Full output from the “Validate Setup” step, new Request IDs (from lines “Request ID: …”), and the attempt time
Settings → Network → Run Diagnostics (screenshot/results), any VPN/proxy/corp network; try enabling Settings → search “HTTP/2” → “Disable HTTP/2”
Quick checks:
Send updated Request IDs (besides the ones you provided) - I’ll pass them to the engineers if the issue persists.
panta82
(Ivan Pantic)
December 4, 2025, 9:39pm
4
The entire log (wasn’t sure if the UUID-s were secrets):
[Status] Creating testing environment... (Snapshot ID: snapshot-20251130-fdfb986c-1374-43a0-a615-90cc3dd62c14, Request ID: 69306564-d409-4c05-8b0f-7a8d6a5abf24)
[Warning] Failed to create testing environment: [unavailable] HTTP 502
[Retry] Retrying in 2 seconds (Attempt 2/3)...
[Status] Creating testing environment... (Attempt 2/3) (Snapshot ID: snapshot-20251130-fdfb986c-1374-43a0-a615-90cc3dd62c14, Request ID: bb311c9c-fa6f-4c10-8364-ae5dae2e1ddf)
[Warning] Failed to create testing environment: [unavailable] HTTP 504
[Retry] Retrying in 2 seconds (Attempt 3/3)...
[Status] Creating testing environment... (Attempt 3/3) (Snapshot ID: snapshot-20251130-fdfb986c-1374-43a0-a615-90cc3dd62c14, Request ID: 4abd8a56-113a-4f91-95d7-e3603d4faae0)
[STATUS UPDATE] failed
[Error] Failed to create testing environment after 3 attempts: [unavailable] HTTP 504
When I went back to the remote env tab, there was also this:
[Status] Found existing default environment: pod-nxc45fozjffmddlwkp35vlcqdu
[Status] Connecting to environment...
[Status] Connected to environment: pod-nxc45fozjffmddlwkp35vlcqdu
[STATUS UPDATE] failed
[Error] Failed to attach logs to environment (Pod ID: pod-nxc45fozjffmddlwkp35vlcqdu): [not_found] Object not found: pod [("tenant_id", "690ed51143ec6ea5268c"), ("pod_id", "pod-nxc45fozjffmddlwkp35vlcqdu")]
I don’t have .cursor/environment.json file anywhere that I can see.
No secrets in use
During the setup, ./support/setup.sh was ran, it took about a minute or two. It basically does:
setup 3 git submodules
setup remotes to an alternative gitlab server
npm install
generate settings files
This is also the “run on install” command for the env. No “run on start“, no terminals.
Ran diagnostics: all checks. No firewall/corporate net.
Retried, after switching to http1.1, same results
[Status] Creating testing environment... (Snapshot ID: snapshot-20251204-9e1e4ed4-2faf-4e4b-83dc-20fe7c744bd0, Request ID: c6e8524c-da11-42d1-b09e-06d6a11d2087)
[Warning] Failed to create testing environment: [invalid_argument] Error
[Retry] Retrying in 2 seconds (Attempt 2/3)...
[Status] Creating testing environment... (Attempt 2/3) (Snapshot ID: snapshot-20251204-9e1e4ed4-2faf-4e4b-83dc-20fe7c744bd0, Request ID: 6da57837-f947-4ba1-ad9b-91d4210a8113)
[Warning] Failed to create testing environment: [invalid_argument] Error
[Retry] Retrying in 2 seconds (Attempt 3/3)...
[Status] Creating testing environment... (Attempt 3/3) (Snapshot ID: snapshot-20251204-9e1e4ed4-2faf-4e4b-83dc-20fe7c744bd0, Request ID: 8d70091e-a7a1-4f5b-a512-02704fc566b8)
[Error] Failed to create testing environment after 3 attempts: [invalid_argument] Error
No timestamps, but it takes about 1-2 minutes for each of these to fail. Feels like time out. Doesn’t seem like network, because the remote VM connection worked earlier.
The one interesting thing about this setup is, there are git submodules, and I add an additional remote to them. Not sure if it matters.
httpiga
(Nicola)
December 5, 2025, 4:17pm
5
I don’t know if it may help you, but I’ve had the same issue when defining a start and install scripts (in the “Configured Runtime Settings” step) - I’ve been able to successfully get a working “Validate Setup” only after removing the start/setup scripts.
panta82
(Ivan Pantic)
December 5, 2025, 10:38pm
6
You were right, when I removed setup script, it worked. I guess I’ll try to set it up after the fact. Thanks!
1 Like
andrewh
(Andrew Milich)
December 6, 2025, 6:37am
7
Taking a look at how we can improve setup from this - thank you!
2 Likes
Where does the bug appear (feature/product)?
Background Agent (GitHub, Slack, Web, Linear)
Describe the Bug
Hi,
I’m unable to start a Cloud Agent because Cursor fails to create the default environment.
Here is the full error loop I get:
[Status] Creating default environment… (Request ID: 6e57b81d-7abd-4534-a602-679034e033d8)
[Warning] Failed to create default environment: [invalid_argument] Error
[Retry] Retrying in 2 seconds (Attempt 2/3)…
[Status] Creating default environment… (Attempt 2/3) (Request ID: 6b872e1d-1204-4418-b1e8-0b55987a6fe5)
[Warning] Failed to create default environment: [invalid_argument] Error
[Retry] Retrying in 2 seconds (Attempt 3/3)…
[Status] Creating default environment… (Attempt 3/3) (Request ID: f151cfc1-0504-438a-8573-1792264cd825)
[Error] Failed to create default environment after 3 attempts: [invalid_argument] Error
[STATUS UPDATE] failed
Git provider: GitLab self-hosted , correctly configured
In the Setup Background Agent, step 1 confirms that the repository connection is successful
The error happens immediately when creating the default Cloud Agent environment.
Could you help me identify what is causing this invalid_argument failure?
Thanks,
Hugo
Steps to Reproduce
First try on the Cloud Agent setup on a simple project with Gitlab Self-Hosted repository and Team Plan.
Expected Behavior
The Cloud Agent environment should start so that I can configure a snapshot.
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Cursor 2.1.50 (Universal)
VSCode & environment details:
VSCode Version: 1.105.1
Commit: 56f0a83df8e9eb48585fcc4858a9440db4cc7770
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.1.0
Does this stop you from using Cursor
No - Cursor works, but with this issue
system
(system)
Closed
December 31, 2025, 7:23pm
9
This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.