# Staging site is not loading... what to do?

**URL:** <https://community.kinsta.com/t/staging-site-is-not-loading-what-to-do/3400>\
**Category:** Application Support\
**Created:** [May 6, 2024, 4:56am UTC](https://community.kinsta.com/t/staging-site-is-not-loading-what-to-do/3400 "2024-05-06T04:56:35Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![grnatog](https://avatars.discourse-cdn.com/v4/letter/g/f6c823/32.png) [@grnatog](https://community.kinsta.com/u/grnatog)\
**Post date:** [May 6, 2024, 4:56am UTC](https://community.kinsta.com/t/staging-site-is-not-loading-what-to-do/3400/1 "2024-05-06T04:56:35Z")

</div>

Help! I just created my staging environment to push my local changes to, which I just pushed my local environment to. However, when I open my staging environment URL, the page does not load.

What am I doing wrong? How can I get help?

I’ve ensured my PHP is the same version as local. I’ve disabled cache and also enabled Site Preview. What next?

I need to push these changes to prod, but I don’t want to until I can verify staging is working as needed.

---

<div class="post-metadata">

**Author:** ![VladimirM](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/vladimirm/32/2786_2.png) [@VladimirM](https://community.kinsta.com/u/VladimirM)\
**Post date:** [May 6, 2024, 7:11am UTC](https://community.kinsta.com/t/staging-site-is-not-loading-what-to-do/3400/2 "2024-05-06T07:11:31Z")

</div>

Hello **grnatog** 👋

Staging site usually doesn’t require Site Preview, even with custom domains. What is the site in question so I can check on our end?

Kind regards  
Vladimir

---

<div class="post-metadata">

**Author:** ![VladimirM](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/vladimirm/32/2786_2.png) [@VladimirM](https://community.kinsta.com/u/VladimirM)\
**Post date:** [May 10, 2024, 8:58am UTC](https://community.kinsta.com/t/staging-site-is-not-loading-what-to-do/3400/5 "2024-05-10T08:58:16Z")

</div>

Hello Grnatog,

The issue here is the _www_ prefix. The kinsta.cloud domains only cover first-level subdomains… Adding a www makes it a second-level subdomain and our SSL doesn’t cover it for Kinsta.cloud domains.

The solution here is to run a search-replace via Mykinsta or WP CLI to replace:

[https://www.sitename.kisnta.cloud](https://www.sitename.kisnta.cloud)

with

[https://sitename.kinsta.cloud](https://sitename.kinsta.cloud)

I’ve sent you a reply in DM as well. In this reply, I’ve redacted the actual site name and replaced it with ‘sitename’.

Kind regards