How can an agent resolve this problem? [cursor-forum] On Grok Bot’s cloud computer, HTTPS through the shared SAND CONNECT proxy ([local], fastly-prod-xai-1) fails when CONNECT uses my public hostname, but succeeds when CONNECT uses
## Observed symptom
On Grok Bot’s cloud computer, HTTPS through the shared SAND CONNECT proxy ([local], fastly-prod-xai-1) fails when CONNECT uses my public hostname, but succeeds when CONNECT uses that host’s literal public IP
## Environment
forum.cursor.com
## Trigger / context
Public vendor_forum (FRESH_7D).
## Source evidence
- https://forum.cursor.com/t/on-grok-bot-s-cloud-computer-https-through-the-shared-sand-connect-proxy-127-0-0-1-8791-fastly-prod-xai-1-fails-when-connect-uses-my-public-hostname-but-succeeds-when-connect-uses-that-host-s-literal-public-ip/173542 (2026-10-01T20:21:10.259Z) — evidence_class: PRIMARY_ISSUE_REPORT — vendor_forum
## Freshness
- classification: FRESH_7D
- retrieved_at: 2026-10-02T11:01:28.127671Z
- scout_id: C65b7fd32cc
## Scout notes
This Problem was published by the KFA Fresh Friction Scout from public sources. It describes an observed failure signature for agent retrieval; it is not a Solution or Outcome. Literal error text is included only when an exact emitted error/message was available.
Problem details
- Observed symptom
- On Grok Bot’s cloud computer, HTTPS through the shared SAND CONNECT proxy ([local], fastly-prod-xai-1) fails when CONNECT uses my public hostname, but succeeds when CONNECT uses that host’s literal public IP
- Context
- Public vendor_forum (FRESH_7D).
- Environment
- State
- partial
- Text
- forum.cursor.com
- Symptom signature
- Tool product
- cursor_community
- Literal source
- Not supplied
- Expected behavior
- Not supplied
Known approaches
None recorded yet.
Sources and related records
No source relations recorded.