Skip to main content
Question

Connect a domain button stuck on infinite loading spinner (Figma Sites/Make)

  • June 29, 2026
  • 5 replies
  • 35 views
DesmondLHB2026

Account: Professional plan

File: HolyMomma.co (file ID: 3i3DklvXxH2VM5fi8xtRMk)

URL: https://www.figma.com/make/3i3DklvXxH2VM5fi8xtRMk/HolyMomma.co

 

Issue:

In Settings > Domains > Connected domains, clicking "Connect a domain" opens the field/button but it immediately gets stuck on an infinite loading spinner and never progresses to the form where I'd enter my domain (holymomma.co) or receive the DNS records to add.

 

Steps to reproduce:

1. Open the file above

2. Click the settings gear icon (top right) > Domains

3. Under "Connected domains," click "Connect a domain"

4. The button is replaced by a spinner that never resolves

 

What I've already tried (all failed the same way):

- Multiple full page reloads

- Opening in brand-new browser tabs

- Logging out and back into Figma, then retrying

- Waiting 10+ seconds on the spinner

- Removing a previously-connected domain and re-adding it (also got stuck)

 

Additional notes:

- No errors appear in the browser console during the stuck state

- No related network request is fired when clicking the button (checked via browser dev tools)

- The base domain section (notice-jab-66490202.figma.site) works fine and shows "Published"

- This is blocking me from connecting my own domain (holymomma.co) to my published site

 

Could you please look into why the Connect a domain dialog isn't loading, or let me know if there's a workaround?

 

Thanks,

Desmond

5 replies

Tom Reem
Figmate
  • Tom Reem
  • Figmate
  • June 29, 2026

👋🏻 Hey ​@DesmondLHB2026, welcome to Figma Forum and thanks so much for taking the time to explain this.

I followed the steps to reproduce and things did work as expected with my test file. I want to make sure we're zeroing in on the specific settings where things may be getting stuck, so I'm opening a ticket with our Product Support team for a deeper dive into the file. Your ticket number is: 1989020, and I've sent instructions on sharing the file securely — please check the email inbox that's tied to your Figma account for next steps.

Thanks again for your report and for your patience as we look into this.

DesmondLHB2026

Hi Tom, thanks for looking into this — I'll check my inbox for the file-sharing instructions and get the HolyMomma.co file over to your team shortly. Appreciate the quick turnaround, and I'll keep an eye out for updates on ticket #1989020.

Celine_
Figmate
  • Celine_
  • Community Support
  • July 9, 2026

Hey ​@DesmondLHB2026 , Celine from Figma here, stepping in for ​@Tom Reem .
I checked internally and can see that one of our Support agents replied to your case on July 7. When you have a chance, could you please check your inbox (and your spam folder, just in case) for their response? We replied via your email address: dxxxd.lxb@gxxxxl.xxm. And feel free to reply directly to your support case, it will re-opened automatically, thank you!

DesmondLHB2026

Hi Celine, thanks for checking in! I did receive Chris's July 7 reply and have now granted view access to support-share@figma.com on the HolyMomma.co file (ID: 3i3DklvXxH2VM5fi8xtRMk) as Tom originally requested.

 

One clarification though — Chris's reply covered DNS-troubleshooting tips (record mismatches, conflicting AAAA records, SSL cert delays), but my issue happens before any of that: clicking "Connect a domain" gets stuck on an infinite spinner and never even shows me a form to enter my domain or any DNS records to configure. So there's nothing on my end to check yet — the dialog itself isn't loading. Hoping the file access now unblocks the team's investigation into that. Thanks!

Celine_
Figmate
  • Celine_
  • Community Support
  • July 9, 2026

Thanks for the clarification, that's really helpful context!

I've added a follow-up note to your support case so Chris is aware of the additional details you've shared, including that the issue occurs before the domain configuration dialog even loads.

 

Update: Chris replied to you directly via your support case, please continue the conversation directly to your existing support as they are best equipped to continue investigating this issue with you. Thanks for your patience in the meantime while they are investigating it!

Terms & ConditionsAccessibility statement