Awaiting SSL certificate
Your DNS records were validated. Once Figma issues your SSL certificate, your domain will be securely
activated. Please check back later.
Solved
Figma site can not connect a domain
Best answer by Celine_
Hey
If you’re running into issues connecting your domain, there could be a few different causes. Please try the steps Gayani shared in this Help Center article and let us know if that helps.
I’ll also summarize those steps here for reference:
- Cloudflare domains: If Cloudflare is your custom domain provider, you need to set the proxy status for the domain to DNS only. This configuration is required to successfully verify the domain.
- DNS propagation delays: DNS changes can take time to update across the internet. If you think this might be the problem, we recommend waiting a while and checking back later.
- Incorrect record types or values: Ensure the provided values exactly match what’s required. Even a small typo can interrupt the process. Figma will display an error icon if one or both of the records can’t be verified.
- Conflicting DNS settings: Check for duplicate or conflicting entries in your DNS settings—for instance, multiple CNAME records for the same subdomain.
- Conflicting AAAA record on apex domain: If you're connecting an apex domain—like
example.com—using an A record, check whether there’s an existing AAAA (IPv6) record on the same host (@). Having both can prevent your domain from connecting properly. Remove the AAAA record from your DNS settings and try again. - Awaiting SSL certificates: Figma automatically provisions SSL certificates for custom domains, which ensures secure HTTPS access. This process typically takes up to 15 minutes, but can sometimes require additional time. If you're still waiting after 30 minutes, we recommend checking if you have any CAA (Certificate Authority Authorization) DNS records configured for your domain. If so, make sure they allow certificates from Google Trust Services, Let's Encrypt, and SSL.com.
Still, if the issue is still persisting, I’d recommend reaching out directly our support team so they can take a closer look at your case.
To do this, please:
- Open our Support Hub
- In the search bar, enter “report a bug”
- Click “Start a chat”
- Press “Enter”
- Respond to the next question with “Yes”
- Submit the bug report
Hey
-
DNS Propagation Delays: Sometimes, DNS changes can take a while to update across the internet. If you've recently made changes, and usually can take around 24 hours.
-
Incorrect Record Types or Values: Double-check that the DNS records you entered match exactly what Figma requires. Even a small typo can cause issues. Figma will show an error icon if the records can't be verified.
-
Conflicting DNS Settings: Look for any duplicate or conflicting entries in your DNS settings, such as multiple CNAME records for the same subdomain.
-
SSL Certificates: Figma automatically provides SSL certificates for custom domains, but it can sometimes take longer than expected to issue these certificates.
Thank you,
Gayani
Hi Gayani,
Thank you for your follow-up. I’ve confirmed that all DNS records (including CNAME and any required verification records) were correctly configured according to Figma’s requirements and have successfully propagated globally. It’s now been over 48 hours since the DNS changes were implemented, and the domain resolves correctly when tested.
However, the SSL certificate for the custom domain still hasn’t been issued by Figma’s system. Given that DNS is fully functional, the delay appears to be isolated to the SSL provisioning process.
Could you please investigate why the certificate hasn’t been generated or deployed? Let me know if additional details from my end would be helpful.
Best regards,
Vans Chen
Hi
I’ve gone ahead and created a support ticket so our team can take a closer look at this. For reference, your ticket number is #1422490.
Please reply to the email and share a screenshot of your DNS settings, and add "support-share@figma.com" to this file with "can edit" permissions, and then have your admin approve the upgrade request for that account? Once that has been approved, the support team can take a closer look. Please note, the seat counts for your plan will not change as a result of this, nor will you be charged for this support-share account.
If you're unsure on how to invite someone to a file, please follow these steps:
- Click the "Share" button at the top-right corner of the Editor
- In the next window, type support-share@figma.com into the text box
- Select the "can edit" permission option
- Click the "Send invite" button
The team will keep you updated as they investigate further. If anything else comes up or you have more details to share in the meantime, feel free to share with with them. Appreciate your patience and please let me know if there is anything else I ca help with, thank you!
Hi
I am experiencing the exact same issue. The DSN entries are correct and DNS have propagated for more than 4 days now.
Can you investigate the issue on your end please?
Thank you!
(I already added support-share@figma.com to the sharing option of the figma file)
Hi,
I have the same issue.
The DSN entries are correct and DNS have propagated for more than 4 days now.
Can you please take a look, it’s very urgent.
Thank you.
(I already added support-share@figma.com to the sharing option of the figma file)
Hey
I took a look at the support ticket from the previous user who reported this. Our support team investigated and suggested the following next step, which helped in that case:
Please check if the DNS records are properly configured and propagated. If it does, check one additional potential cause for the SSL certificate delay. Please verify if you have any CAA (Certificate Authority Authorization) DNS records configured for your domain. If you do, make sure they allow certificates from Google Trust Services, Let's Encrypt, and SSL.com. This is a common cause for delays in SSL certificate provisioning. The SSL certificate provisioning typically takes up to 15 minutes, but can sometimes require additional time.
If you’ve already checked the CAA records and everything looks good, I’d recommend reaching out directly to our support team using this form:
https://help.figma.com/hc/en-us/requests/new?ticket_form_id=360001731233. Be sure to include the file URL so the team can investigate more deeply.
Thank you,
Gayani
Also faced this issue. I managed to fix it with some help from support. What worked for me removing the AAAA record, which wasn’t explicitly mentioned on the guide. Once done you have to hit refresh on the domain settings in Figma then republish and it should work.
For reference, I put 2 entries for each, the explicit values for each CAA record (also not mentioned) I put is:
Google Trust Services
| Type | CAA | CAA |
| Name | @ | @ |
| Content | 0 issue “pki.goog” | 0 issuewild “pki.goog” |
| TTL | 14400 | 14400 |
Let’s Encrypt
| Type | CAA | CAA |
| Name | @ | @ |
| Content | 0 issue “letsencrypt.org” | 0 issuewild “letsencrypt.org” |
| TTL | 14400 | 14400 |
SSL.com
| Type | CAA | CAA |
| Name | @ | @ |
| Content | 0 issue “ssl.com” | 0 issuewild “ssl.com” |
| TTL | 14400 | 14400 |
I had originally had a site I made using Figma Make and everything was working - I remade my site using Figma Sites - updated all the DNS records, but now I am getting an SSL error when trying to view my site? Called Godaddy and everything seems correct on their end. Can some please help me out :)
I encountered the same issue where the domain status was stuck at "Awaiting certificates" even after DNS records were validated and propagated correctly.
If you’re also using Cloudflare, the fix that worked for me was:
-
Go to Cloudflare Dashboard → Domain → SSL/TLS → Overview
-
Change the SSL/TLS Encryption mode to Off
It seems Cloudflare’s CAA settings block the SSL certificate that Figma is trying to issue. Disabling SSL/TLS at the Cloudflare level allowed the certificate request from Figma to go through.
After doing this, the SSL certificate was generated successfully and the domain became active.
Hey everyone, thank you so much for taking the time to share your experiences and what worked for you. While our Help Center article on troubleshooting domain connections covers the most common scenarios, there are cases where everything seems to be correct on the DNS side but an SSL certificate still won’t issue or the site remains stuck in “awaiting certificates.”
If you’ve already tried the troubleshooting steps in the article and are still running into issues, the best next step is to reach out directly to our support team so they can dig into your specific setup. You can reach out to our support team via this Form. Please make sure to include the file URL and any details about your DNS provider or the changes you’ve made, that context helps the team investigate more quickly.
Let me know if there is anything else I can assist with!
Hello,
I'm currently stuck on the "Awaiting certificates" step for my custom domain.
I've verified that all the required DNS records, the A record, TXT record, and CNAME record, have been correctly configured and have successfully propagated. It's now been over 4 days since the records were updated. The domain is resolving correctly, but the SSL certificate still hasn't been issued by Figma.
Could you please investigate this issue and help me figure out why the SSL certificate is not being provisioned?
Thanks for your help.
Caroline
Hello
I’m experiencing the exact same issue as well. Is there a known fix or resolution for this problem?
Hey
If you’re running into issues connecting your domain, there could be a few different causes. Please try the steps Gayani shared in this Help Center article and let us know if that helps.
I’ll also summarize those steps here for reference:
- Cloudflare domains: If Cloudflare is your custom domain provider, you need to set the proxy status for the domain to DNS only. This configuration is required to successfully verify the domain.
- DNS propagation delays: DNS changes can take time to update across the internet. If you think this might be the problem, we recommend waiting a while and checking back later.
- Incorrect record types or values: Ensure the provided values exactly match what’s required. Even a small typo can interrupt the process. Figma will display an error icon if one or both of the records can’t be verified.
- Conflicting DNS settings: Check for duplicate or conflicting entries in your DNS settings—for instance, multiple CNAME records for the same subdomain.
- Conflicting AAAA record on apex domain: If you're connecting an apex domain—like
example.com—using an A record, check whether there’s an existing AAAA (IPv6) record on the same host (@). Having both can prevent your domain from connecting properly. Remove the AAAA record from your DNS settings and try again. - Awaiting SSL certificates: Figma automatically provisions SSL certificates for custom domains, which ensures secure HTTPS access. This process typically takes up to 15 minutes, but can sometimes require additional time. If you're still waiting after 30 minutes, we recommend checking if you have any CAA (Certificate Authority Authorization) DNS records configured for your domain. If so, make sure they allow certificates from Google Trust Services, Let's Encrypt, and SSL.com.
Still, if the issue is still persisting, I’d recommend reaching out directly our support team so they can take a closer look at your case.
To do this, please:
- Open our Support Hub
- In the search bar, enter “report a bug”
- Click “Start a chat”
- Press “Enter”
- Respond to the next question with “Yes”
- Submit the bug report
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.