PixelSoda

Hello! What domain are you trying to connect? Usually that error means that the URL connected to your site is being redirected to other URLs too many times. If you're pointing a Squarespace domain to a third-party platform like Unbounce, make sure to remove any conflicting Squarespace-related DNS records and that you've added the CNAME record mentioned in Unbounce's guide: Connecting your domain to Unbounce Squarespace also has their own guide for pointing a domain: Pointing a Squarespace domain to a non-Squarespace site

You can try resending the verification email as a quick test by clicking the "Resend verification email" link. Make sure to check your spam and junk folders, too. For reaching out to support, make sure that you're contacting them through the support form on their site. Otherwise they won't receive the emails you send them. Here's the support form - https://support.squarespace.com/hc/requests/new#choose-topic Alternatively, you can reach out to Squarespace on Twitter, Instagram, or Facebook Messenger.

Squarespace has been reporting an issue with Nameserver Connect. If the domain is defaulting to DNS Connect, use the provider's default nameservers and manually connect the domain, instead. If you see View DNS settings instead of Edit DNS, that means the domain is linked using DNS connect. GoDaddy has steps for changing nameservers here - GoDaddy - edit domain nameservers If you click View DNS settings, you'll see all of the DNS records that need to be added in GoDaddy. Squarespace also has steps in this guide - Manually connecting a GoDaddy domain to your Squarespace site

It looks like the verification record was taking a little time to update and the site is loading now! You can always check the status of new DNS records like this using Whatsmydns.com. Just make sure to include the Host value if it's not "@" (in this case you would be checking ataj4a5b95cswlsgwn8s.sutherlandsharksfc.com.au)

If you reach out to customer support on one of Squarespace's social media accounts, they can usually check on the status of a ticket. Did you already receive the verification email for your target email address and click the link to verify?

Usually if customer support created a ticket for an issue, it's because support has to help troubleshoot - either for security reasons or because they have a fix that has to be deployed from their end. Did you already reach out to customer support like those locked posts recommend? I have a few suggestions that might help in the meantime - 1. Changes Not Reflected or Updated: Any modifications I attempt to make to my domain settings are not being reflected. It’s as if the changes are not being saved or propagated at all. To be honest, if browser troubleshooting didn't help with this and you're not seeing any error messages that give you more info, this could be related to Squarespace. Customer support would be the best resource for help. 2. Connection to Website: I’m unable to connect my domain to my website. Despite following the steps outlined in the Squarespace support guides, my website remains disconnected from the domain. What domain are you trying to connect, and are you connecting it to a Squarespace site or a non-Squarespace site? 3. SSL Generation: No SSL certificate is being generated for my domain, which is crucial for ensuring the security of my site. Squarespace only provides SSL for domains that are connected to a Squarespace site, and the SSL certificate won't generate until the domain is fully connected. If your domain is connected to a Squarespace site and the SSL isn't generating, check the connection or reach out to customer support. Otherwise, if you have a third-party site, reach out to your website provider for advice on adding SSL protection. 4. DNS Management Issues: I am unable to create, change, or delete DNS records. The DNS management functionality seems to be completely unresponsive. Did you already try logging out and logging back in to fix the issue with editing your domain's DNS settings? That's been working for most users, even when browser troubleshooting hasn't.

Hello! Would you mind sharing a link to your site?

Did you already try reaching out to customer support? In the past, when the "Couldn't load collection" error pops up, they've been able to provide either a solution or a workaround.

When I look up the DNS records for your domain, I don't see any of the records that point your domain to Squarespace. Make sure that you've added Squarespace's default records in your domain's DNS settings: Add Squarespace defaults

Hello! There isn't a way to duplicate a collection page, so you'll need to add a new gallery page for the second category. Next to Main Navigation (in your first screenshot), click the + icon and select the gallery page, then begin adding images to the page - Gallery pages in version 7.0

Hi @JurgenB - Did you already try the browser troubleshooting that resolved this error for other users?

Hi @C2G - I think Squarespace updated the steps they have for forwarding both the "@" and "www" version of your domain. There's now a spot that reads: Out of curiosity, have you confirmed that the Squarespace default records are in your domain's DNS settings? If not, try using these steps: Remove the domain forwarding rule Add the Squarespace default records in the DNS settings using the Preset button Add the forwarding rule again (only for the "@" subdomain, there's no need to make a forwarding rule for the "www" subdomain) If that doesn't work and you've already had a lot of back and forth with the Squarespace team, you could ask them to escalate your case. The response time might be a bit slower but they'd be able to check if there's something else going on!

It's true that Squarespace doesn't support dynamic DNS. It looks like there are some Heroku add-ons you can use to route traffic through a static IP, like QuotaGuard Static. I'm not 100% familiar with Heroku, but it seems to me that this is specific to connecting a root domain. Squarespace did recently add support for ALIAS records, and Heroku's guide mentions using ALIAS records for other providers: Heroku - Configuring DNS for root domains Their guide also mentions getting around this issue by exclusively using subdomains, like the "www" subdomain: Heroku - The Limitations of DNS A-Records Heroku - Add a custom domain with a subdomain Hopefully some of this is helpful! It's certainly worth double-checking with Heroku support since I'm not entirely sure if this is all accurate.

Hey all - Domain forwarding converting to CNAME records As far as I'm aware, domain forwarding in Google Domains shouldn't have converted to CNAME records after migration, so the issue that @SNCGuru described is worth reporting to Squarespace support. If you're worried that your ticket is being ignored, contact one of Squarespace's social media accounts and ask them to check on it for you. Path forwarding You should be able to enable path forwarding when setting up a domain forwarding rule. If you're having trouble enabling path forwarding, trying a different browser might help. If path forwarding is enabled but it's not working, contact Squarespace support so they can take a look. Forwarding the "www" subdomain EDIT: It looks like they changed how this setup works. Now it seems you need to make a forwarding rule using @ as the subdomain and also have the Squarespace defaults record preset in place. The "Implementing this rule could interfere with how the domain works with the website" error does sound a little different though, and doesn't seem to be documented. I'd recommend reporting this to Squarespace, and in the meantime you could try pointing the domain instead of forwarding. Valid subdomain error If you're seeing the "not a valid subdomain" error, make sure that you've added a subdomain in the "Forward from" field of the forwarding rule. For @DecaturishDan, no subdomain has been specified in the "Forward from" field, which is why the error says there isn't a valid subdomain. To forward a root domain, use @ as the subdomain (there is a note on this beneath the "Forward from" field).

Oh no! I'm sorry to hear about this. A while back, there was a Squarespace-related issue that caused this to happen. Unfortunately, users had to manually move the subpages back into the correct order in their index page(s) to fix it. Even if that's still the case, the issue is definitely worth reporting to Squarespace to prevent it from happening again: https://support.squarespace.com/hc/requests/new#choose-topic