Title: Why cannot I access my free Cloud WordPress Instance?
Last modified: November 22, 2024

---

# Why cannot I access my free Cloud WordPress Instance?

 *  Resolved [kimmikke](https://wordpress.org/support/users/kimmikke/)
 * (@kimmikke)
 * [1 year, 6 months ago](https://wordpress.org/support/topic/why-cannot-i-access-my-free-cloud-wordpress-instance/)
 * When I login to my Boldgrid free Cloud WordPress Dashboard and choose Login, 
   I cannot reach my Instance. Only thing seen is the web browser searching for 
   a long time and then, it gives error message (even though nothing is changed,
   no firewall or proxy is used, connection is working). A month ago last time this
   worked fine. The error message is “Hmmm… can’t reach this page. demo2.cloudwp.
   dev took too long to respond”
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fwhy-cannot-i-access-my-free-cloud-wordpress-instance%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 2 replies - 1 through 2 (of 2 total)

 *  [brandonco](https://wordpress.org/support/users/brandonco/)
 * (@brandonco)
 * [1 year, 6 months ago](https://wordpress.org/support/topic/why-cannot-i-access-my-free-cloud-wordpress-instance/#post-18157969)
 * Hi [@kimmikke](https://wordpress.org/support/users/kimmikke/),
 * I’m sorry to hear you’re experiencing difficulties accessing your BoldGrid Cloud
   WordPress instance. I checked the [demo link in question](https://demo2.cloudwp.dev/trial-65xyx099/)
   and I’m noticing an error message stating that “The location you requested is
   inactive” typically indicates that the instance has expired or encountered an
   issue. Here’s how you can address this:
    1. **Check for Expiration** and navigate to the **Cloud WordPress** section. Here,
       you can view all your instances and their statuses.
    2. **Manage or Renew Your Instance**: If you find that your instance has expired,
       you may have the option to renew or recreate it. In BoldGrid Central, select
       the expired instance and look for options to renew or duplicate it. Keep in 
       mind that if the instance has been inactive for an extended period, its data
       might have been deleted, and you may need to start anew.
    3. **Contact BoldGrid Support**: If you’re sure this is by error you can contact
       us on at our [Support Center](https://www.boldgrid.com/support/ask-a-question/)
       so that we can investigate further.
 * Thanks [@kimmikke](https://wordpress.org/support/users/kimmikke/), hoping for
   a speedy resolution to this for you!
 *  [brandonco](https://wordpress.org/support/users/brandonco/)
 * (@brandonco)
 * [1 year, 5 months ago](https://wordpress.org/support/topic/why-cannot-i-access-my-free-cloud-wordpress-instance/#post-18204187)
 * Hi [@kimmikke](https://wordpress.org/support/users/kimmikke/),
 * We haven’t heard from you in a while so we’re closing this out. Please don’t 
   hesitate to reach back out if you need further assistance.
 * Thank you!

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Why cannot I access my free Cloud WordPress Instance?’ is closed to new
replies.

 * ![](https://ps.w.org/post-and-page-builder/assets/icon-256x256.png?rev=1768477)
 * [Post and Page Builder by BoldGrid - Visual Drag and Drop Editor](https://wordpress.org/plugins/post-and-page-builder/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/post-and-page-builder/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/post-and-page-builder/)
 * [Active Topics](https://wordpress.org/support/plugin/post-and-page-builder/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/post-and-page-builder/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/post-and-page-builder/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [brandonco](https://wordpress.org/support/users/brandonco/)
 * Last activity: [1 year, 5 months ago](https://wordpress.org/support/topic/why-cannot-i-access-my-free-cloud-wordpress-instance/#post-18204187)
 * Status: resolved