I now get
Warning: require(./wp-blog-header.php) [function.require]: failed to open stream: No such file or directory in /home/.marylou/thedolphinsfly/deptfordjourneys.com/index.php on line 4
Fatal error: require() [function.require]: Failed opening required ‘./wp-blog-header.php’ (include_path=’.:/usr/local/php5/lib/php’) in /home/.marylou/thedolphinsfly/deptfordjourneys.com/index.php on line 4
I have uploaded and empty .htaccess file but not sure if this is correct
everything seemed to be going fine until I suddenly
Usually, when you find yourself typing the words “…and suddenly..” you can bet that whatever it is that “suddenly” happened occurred right after you did something else. What did you do right before the “sudden” 403 happened? Did you upload a plugin? Put up a new theme? Edit your functions.php file? Edit your permalink structure? It has to be somethign that you did just prior to this happening. Whatever it was, undo it.
I think it was the ‘sudden’ atempt to change the the Blog URL combined with the server issue which the ISP has said themselves was ‘strange’
I now get the same error no matter what page I attempt to access, whether it be
http://www.deptfordjourneys.com/blog/
http://www.deptfordjourneys.com or
http://www.deptfordjourneys.com/blog/wp-login.php
All the files are in the blog folder and I will happily go back to leaving everything there including the index file.
Is there a standard .htaccess file I can upload?
I’ve deleted the index and the htaccess from the root and uploaded a new empty htaccess file with 666 permissions and the index.php back into the /blog folder. Still I get
Forbidden
You don’t have permission to access /blog/ on this server.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
Help!
I think it was the ‘sudden’ atempt to change the the Blog URL
You tried to change the blog URL? Are you sure it was the Blog URL you changed, or was it the wordpress URL? Sounds like you meesed up some of your configuration settings. the .htaccess file has absolutely nothing to do with this – that only comes into play when you’re messing with the permalink structure.
Delete the .htaccess file you have from your server (and no, there is not “standard” .htaccess file. If you don’t have one, and you need one, just upload a blank txt file and rename it to “.htaccess” on the server.)
Then you’ll need ot be sure your settings are correct in your database by logging into your hosting control panel and delving into your phpMyAdmin area. Follow this tutorial.
That should get you started.
Many thinks for your help doodlebee. It was definitely the blog url that I was in the process of changing. However, I’ve taken your advice, deleted htaccess file, no change. I also checked phpMyAdmin and everything is OK in there too, all pointing to the correct place, still no joy.
I have also been back in touch with the host who is still trying to pull the ‘3rd party software’ trick even though initially they said “That was very strange, indeed. I was accessing everything just fine via SSH but noticed the same problem you had via FTP” and it seems more than just a coincidence that it all happened at the same time.
What I don’t understand is why I get a 403 forbidden which suggest a permissions issue which obviously I haven’t touched.
Anyway any other suggestions welcome and thanks again for your help. I can feel a re-install coming on!!
This is indeed a permissions issue, I have just checked CHMOD is set at 744 for my ‘blog’ folder and this is when I receive the 403 forbidden. If I change it to 755 then I can access the site.
This seems like a hosting issue but they still haven’t replied.
755 is typically what your folders should be set at. Files should be 644.
The same thing happened to me today. I was playing around with my brand new blog and the admin panel. I changed the permalink appearance and – poof! – I was out of the system.
A .htaccess file was indeed created and it read exactly the same thing as deptford’s did so everything should’ve been okay. However the file permissions were somehow to blame in this case as well, I think it was originally 755 or 744. When I set it to 666 or 644, everything works. The permissions were set by wordpress while creating the file, there was no .htaccess in my directory previously.
A bug or whatever… hope it helps someone.
