Figma Make: "Couldn't load Make" error — figma-alpha.s3.us-west-2.amazonaws.com shown as Blocked, but domain is reachable

Hi Celyn,

Thanks for creating the ticket. I'm not able to record a screen video or attaching any image, reason is im facing an error “Not allowed due to company policy:” 

But a few things I noticed in the logs that might help the investigation:

1. In the Network tab, the request to the per-session preview iframe domain (f996966d-cc69-47d5-baca-24fc500561a8-v3-figmaiframepreview.figma.site) fails with net::ERR_SOCKET_NOT_CONNECTED. Meanwhile, every other *.figma.site request in the same session (check-network-compatibility.figma.site, check-network-compatibility.makeproxy-c.figma.site, status.makeproxy-m.figma.site) returns 200 successfully.

2. In the console, I see repeating [make] preview.iframe_sandbox_error, preview_iframe_failure_state_changed, and iframe_buffer_manager.failure_waiting_for_buffer events, followed by reconnecting_toast_shown — it looks like the preview iframe never successfully connects and keeps retrying in a loop.

3. There's also a 403 Forbidden on GET /api/source/v1/make/environment/...&guid=0%3A6, and a 400 Bad Request on POST /api/cortex/foundry/fs-read-file.

4. Separately (unrelated to the above, just flagging it): browser-intake-datadoghq.com is blocked by net::ERR_BLOCKED_BY_CLIENT in my browser, but this looks like Datadog RUM/analytics rather than a Make-required domain, and it happens even with extensions off, so it may just be built-in browser tracking protection.

To recap the troubleshooting already done:
- Tested on company network: same error
- Tested on mobile data (5G, no VPN): same error
- Tested in private/incognito with extensions disabled: same error
- Network Settings modal shows all Make-specific checks (makeproxy-c, makeproxy-m, Figma Sites and Make) as Available except "Publishing a plugin or widget" pointing to figma-alpha.s3.us-west-2.amazonaws.com — but that endpoint returns a normal S3 AccessDenied response (not a timeout/block) from both networks tested, so it doesn't look like it's actually being blocked.

Given the consistent per-session iframe preview socket failure across three completely different networks/environments, this looks like it could be server-side (the preview session/iframe backend) rather than anything in my setup.

Thanks for following up and taking the time to share such a detailed breakdown, @mis_development.

No worries about the screen recording. The log details and troubleshooting steps you provided are still very helpful, and I’ve passed all of this context along through your support ticket so the team has the full picture.

If you have any additional context to share, feel free to reply directly to your ticket. Thanks again for documenting everything so thoroughly. Someone from the team will follow up with you soon 🙏

It does sound more like a Figma side issue than a problem with your network. Since you reproduced it on both your company network and 5G, I would report the M2 error to Figma Support and include the Network Settings result showing the blocked POST request to the S3 endpoint. The AccessDenied response in the browser also suggests the domain itself is reachable.

We have the same issue here and it has just started in the last few days. ‘Could not load Make’ but also a message that ‘Your network has access to the domains needed to run Figma’. We have whitelisted all of the required domains. Every once in a while a prototype might loads but then on refresh it’s the same error.