Skip to main content
Solved

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

  • September 7, 2026
  • 3 replies
  • 23 views
mis_development

I'm getting a "Couldn't load Make. Try checking your network connection or refreshing the page. (M2)" error when trying to load Figma Make.

Opening Network Settings (Cmd/Ctrl + P → "Check network settings") shows:
- Publishing a plugin or widget (POST) — Blocked
- Domain listed: figma-alpha.s3.us-west-2.amazonaws.com
- All other actions (Publishing a library, Adding media to comments, Importing content, Publishing a Make kit, Figma Sites and Make, Figma Make - makeproxy-c, Figma Make - makeproxy-m, Fetching font list) show Available.

I've ruled out a local network issue:
1. Tested on my company network — same error.
2. Tested on mobile data (5G, no VPN) — same error.
3. Opened https://figma-alpha.s3.us-west-2.amazonaws.com directly in a browser on both networks — both return the same S3 AccessDenied XML response (with different RequestId/HostId each time), meaning the domain is reachable and not blocked by any firewall/proxy on my end.

Since the same result happens across two completely different networks, this doesn't look like a local network/firewall problem — it looks like either a false positive in Figma's network check, or a bug on Figma's side related to this specific S3 endpoint.

 

Best answer by Celyn_L

Hi ​@mis_development, Celyn from the Figma Community Support team here.

Thanks for reaching out and for sharing the troubleshooting you’ve already completed, that’s really helpful.

We understand that you’re receiving a “Couldn’t load Make (M2)” error when opening Figma Make, even though the Make-specific network checks show as available, and the issue persists across both your company network and mobile data.

I’ve gone ahead and created a support ticket for you so the team can investigate this further. Your ticket number is #2116799.

To help with the investigation, please reply directly to your ticket with:

If you’re using Figma in a browser, please also try opening Make in a private or incognito window with browser extensions disabled and let us know whether the error persists.

Someone from the team will follow up through your ticket, so please keep an eye on your inbox. Thanks for your patience in the meantime!

    3 replies

    Celyn_L
    Figmate
    • Celyn_L
    • Figmate
    • Answer
    • September 7, 2026

    Hi ​@mis_development, Celyn from the Figma Community Support team here.

    Thanks for reaching out and for sharing the troubleshooting you’ve already completed, that’s really helpful.

    We understand that you’re receiving a “Couldn’t load Make (M2)” error when opening Figma Make, even though the Make-specific network checks show as available, and the issue persists across both your company network and mobile data.

    I’ve gone ahead and created a support ticket for you so the team can investigate this further. Your ticket number is #2116799.

    To help with the investigation, please reply directly to your ticket with:

    If you’re using Figma in a browser, please also try opening Make in a private or incognito window with browser extensions disabled and let us know whether the error persists.

    Someone from the team will follow up through your ticket, so please keep an eye on your inbox. Thanks for your patience in the meantime!

    mis_development
    • mis_development
    • Author
    • New Member
    • September 7, 2026

    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.

     

    Celyn_L
    Figmate
    • Celyn_L
    • Figmate
    • September 7, 2026

    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 🙏

    Terms & ConditionsAccessibility statement