• Hello! My WordPress site was working fine until I made a change in Settings to the home URL and site URL. I don’t remember what exactly it was that I did, but suddenly my site was inaccessible. I had just changed my theme to the Storefront one also.

    Now I get a 403 Forbidden error page any time I try to access my site. It’s been down for over a week.

    Someone instructed me to create a /wordpress database inside my main one and move all of my files there, so I tried that, and it didn’t help.

    I’ve also tried the advice on changing the site URL in the wp-config file and that didn’t help either.

    At this point I’d be thrilled to be able to just get my site back up and running, even if I lost all of my blog posts and such. Is there a way to do that? Please advise. Thank you!

    Site: maitribathbody.com

Viewing 6 replies - 1 through 6 (of 6 total)
  • http://codex.wordpress.org/Changing_The_Site_URL

    There are several ways to try.

    Thread Starter MaitriBathBody

    (@maitribathbody)

    That’s the link that I linked in this sentence: “I’ve also tried the advice on changing the site URL in the wp-config file and that didn’t help either.”

    I tried it and it didn’t help.

    In that link there are several ways to try in addition to the wp-config file.
    Scroll down to see the various ways.

    Thread Starter MaitriBathBody

    (@maitribathbody)

    Part of my problem is that I’ve done so much futzing around in my File Manager in cPanel that I have several wp-config files and several .htaccess files and I don’t know which one is the one I should be editing 🙁

    You can also modify the functions file as well as go into the database. I think the functions file is the easiest.

    It is not possible to have more than one wp-config.php and one .htaccess file in the root directory (the directory where WordPress is installed)

    You also should ask your host about the

    Forbidden

    You don’t have permission to access / on this server.

    Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request.

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

The topic ‘Site totally unavailable’ is closed to new replies.