Domain still not connected after 48 hours!!!!!

[MARedpine]

After I connected my domain to my Weebly account, my status is still showing that it is NOT connected after 24 hours.

maredpine.com was successfully connected. It can take 24 hours for changes to appear across all browsers.

It's been more than 36 hours that my domain is still not connected!  What is wrong with this?  I have NO clue how to resolve this stupid problem!

[MARedpine]

I tried to edit my message but it doesn't work.  ARGH!  The glitch needs to be fixed up!

Anyway, I want to clarify what I mean.  I did follow the instruction on how to verify and connect my domain to my Weebly account.  I purchased my domain at GoDaddy last week.  Of course I purchased the Weebly Professional site for 2 years.

I don't know why my domain is still not connected after 36 hours!  I have been so exhausted and frustrated with this unsolved problem!!!!!!  I had tried to use the support chat but it doesn't help me at all.  As I am counting the hours from yesterday, it's been almost 24 hours after I sent an email to the technical support team.  I don't know if they will ever get back to me. That is why I am posting this in case if I cannot get the response within the next 24-36 hours.

I hope to hear from someone who can help me to resolve this problem.

[MARedpine]

Here are the snapshots of the big issue I am having in the last 48 hours!

@BernadetteA @Ellie_  Based on your answer to the most recent posts of the other users who had similar problem as I do.  I hope that one of you can help me.  Read my thread above.

[Ellie_]

Hi there, @MARedpine,

Welcome to the Seller Community! 🥳 We are so happy to have you here. When we visit your site, we are not seeing an error with it publishing. Are you able to try from an incognito browser?

While you are here, we recommend checking out our Orientation & Etiquette. Hope this helps! 😊

[MARedpine]

Hi there, thank you for a quick response.  I check my site on both Safari and Chrome browsers.  I don't know why it is not working on the Safari browser while it is perfectly working on the Chrome browser.  On the Safari browser, I guess that I may need to clear the caches and histories and then reboot.  Thanks again.