# 404 Page Not Found Error **URL:** \ **Category:** Blog, Website & Page Publishing\ **Tags:** website-pages\ **Created:** [June 30, 2025, 7:01am UTC](https://community.hubspot.com/t/404-page-not-found-error/135388 "2025-06-30T07:01:48Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![DocK](https://avatars.discourse-cdn.com/v4/letter/d/97f17d/32.png) [@DocK](https://community.hubspot.com/u/DocK)\ **Post date:** [June 30, 2025, 7:01am UTC](https://community.hubspot.com/t/404-page-not-found-error/135388/1 "2025-06-30T07:01:48Z")
Hi, I have built a website with the free Hubspot website builder and connected my custom domain by adding Hubspot’s A and CNAME records to my DNS provider - Microsoft is where my nameservers are pointing to. All my Primary and Redirected Domains on Hubspot show “Connected” but when I type in my primary domain, my website shows a 404 Page Not Found Error. I’ve tried unpublishing and re-publishing, clearing browser cache, and using different browsers. I’ve tried adding a dedicated page language. And I deleted the default “home” slug from my website page and the associated Blog site (as my primary domain was actually directing to a blog site that I am not using). I currently only have one website page that I want to show up when my primary domain is typed into a browser. Any other ideas or suggestions to resolve this 404 error and make my site live? ---
**Author:** ![GiantFocal](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/giantfocal/32/41969_2.png) [@GiantFocal](https://community.hubspot.com/u/GiantFocal)\ **Post date:** [June 30, 2025, 7:35am UTC](https://community.hubspot.com/t/404-page-not-found-error/135388/2 "2025-06-30T07:35:31Z")
Hi @DocK, DNS propagation may take anywhere from a few minutes to several hours. If everything is set up correctly, you can wait for a few more hours. ---
**Author:** ![Aakar](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/aakar/32/107785_2.png) [@Aakar](https://community.hubspot.com/u/Aakar)\ **Post date:** [June 30, 2025, 6:11pm UTC](https://community.hubspot.com/t/404-page-not-found-error/135388/3 "2025-06-30T18:11:51Z")
@DocK - It could be a DNS issue, as it takes time for changes to propagate. If it’s still not working, I suggest checking the Blog slug settings (inside content settings) and ensuring that the blog has a different slug than your homepage. Additionally, make sure you’ve published a website page on the homepage (/). ---
**Author:** ![Berangere](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/berangere/32/220784_2.png) [@Berangere](https://community.hubspot.com/u/Berangere)\ **Post date:** [July 1, 2025, 11:29am UTC](https://community.hubspot.com/t/404-page-not-found-error/135388/4 "2025-07-01T11:29:50Z")
Hi @DocK, I wanted to check on you, is it working now? If it’s not, what is the URL of your webpage, please? Thanks a lot @GiantFocal and @Aakar for your help! ❤ I think this article “[Published content is displaying a 404 error](https://knowledge.hubspot.com/website-pages/troubleshoot-content-issues#published-content-is-displaying-a-404-error)” can also give you some ideas and help! I know that our Top Experts @TomM2 and [@Mike\_Eastwood](https://community.hubspot.com/t5/user/viewprofilepage/user-id/9259) have a great amount of experience in terms of websites: Hi both, do you have additional suggestions to help @DocK, please? Thanks so much in advance and have a wonderful day! 🌞 Bérangère ---
**Author:** ![DocK](https://avatars.discourse-cdn.com/v4/letter/d/97f17d/32.png) [@DocK](https://community.hubspot.com/u/DocK)\ **Post date:** [July 2, 2025, 4:44am UTC](https://community.hubspot.com/t/404-page-not-found-error/135388/5 "2025-07-02T04:44:03Z")
Hi [@BérangèreL](https://community.hubspot.com/t5/user/viewprofilepage/user-id/230185) @Aakar @GiantFocal I appreciate your response and input. After waiting, adjusting language settings, unpublishing, republishing, and going through all settings, I ended up disconnecting and going through the connect a domain process again from scratch. This seemed to resolve the issue and the site is now published and visible.