403 Forbidden Error on whole blog!

  • Resolved xzyber

    (@xzyber)


    15 years, 10 months ago

    Ok guys, I give up! Been working on this and searching for 7 hours!

    I was on my blog site yesterday everything was perfect! I didn’t even post anything or nothing at all just viewed my site as always just to make sure it was working properly.

    Today I went to my site and I got this:

    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.
    Apache/1.3.33 Server at AppStuff Port 80

    So I have searched and searched. I have tried everything!
    Permissions are correct: 755 on folders, 644 on files.

    I even have another blog (different domain) that is also hosted on this same hosting account and within the same file manager. It is working perfect! I even compared a few of the files. Everything is the same!

    I then came across the .httaccess files:

    # BEGIN WordPress

    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>

    # END WordPress

    Both blog’s .httaccess files are the same!

    What I know:
    1. It isn’t my hosting provider as I have another blog on this hosting account that is in the same file manager and everything is the same.
    2. It isn’t the .httaccess as they are the same compared to the working blog.
    3. It isn’t the permissions as the files are 644 and the folders 755

    Please help, I get the same 403 forbidden error when I go to the wp-admin.php and wp-login.php and any other part of this blog.

Viewing 5 replies - 16 through 20 (of 20 total)
  • Thread Starter xzyber

    (@xzyber)

    Stop with the drama. Less whining and more answers.

    WOW what support this place gives… I’ll find support some where else.

    Perhaps you thought that someone would magically provide you an answer? Judging by your remarks that is how it sounds.

    Some times things need to be troubleshooted, and that requires more than reciting pat answers, “ive done that, ive done this”, as well as actually answering questions when theyre asked.

    Im wasting my time responding to you if the only thing you do is recite what you said in your last post.

    Best of luck, I hope you can answer their probative questions better than you answered mine.

    Please, stop fighting. Is the best way to close a question without getting any answer. I’m just sharing my experience. I had the idea of deleting through the FTP the last plugin I installed and “magically” my blog came into life again. Then I realize that there was a sentence that told me that this plugin was not tested with my WordPress version (which, by the way, is the 2.7), but in previous experiences, the plugin supposedly fitted. In some way, the answer still remains unanswered, because we didn’t know why all this happens… It would be a good thing to ask this to one of wordpress programmers… just an idea…

    Thread Starter xzyber

    (@xzyber)

    Blog is now fixed, it was on godaddy’s side. DNS entry: Ip address didn’t get updated in a recent update on godaddy’s side. So if anyone has this problem check your dns ip address and make sure they are right! Call your hosting provider for help if needed. Thanks Whooami I probably wouldn’t have figured out without that little tip on the dns entries.

    Thanks guys!

    I think I triggered this issue today by having a looped forwarding. Not 100% sure, awaiting hosting reply for webtechglobal.co.uk

    It rendered a page as 403 plus all children of that page! So its a nice big chunk of my blog that cannot be accessed now. If you feel you have done a loop in forward don’t mess about and let it happen again to avoid this.

    I’m trying to setup sub-domains and forwardings in order to shorten url’s for affiliates on my site. Somewhere along the line the plugins I’m using clashed with the server I think!

    Ryan

Viewing 5 replies - 16 through 20 (of 20 total)
  • The topic ‘403 Forbidden Error on whole blog!’ is closed to new replies.