Ask your WordPress questions! Pay money and get answers fast! Comodo Trusted Site Seal
Official PayPal Seal

403.14-Default document not configured: wp-admin fail, and more WordPress

  • REFUNDED

403.14-Default document not configured (and more)
I keep getting a 403.14 error when trying to access the wp-admin part of my newly installed wp site. All the files are located in a subdirectory for testing purposes while the current site is still live, so the path is: example.com/test. The database is fine, the index.php page loads ok, but when I go to example.com/wp-admin or any other page I keep getting this:

HTTP Error 403.14 - Forbidden
The Web server is configured to not list the contents of this directory.
Detailed Error Information
Module: DirectoryListingModule
Notification: ExecuteRequestHandler
Handler: StaticFile
Error Code: 0x00000000
Requested URL: http://example.com:80/test/wp-admin/
Physical Path:
\\HOSTING\DFS\20\7\3\7\201845xxxx\user\sites\example.com\www\test\wp-admin\
Logon Method: Anonymous
Logon User: Anonymous

Most likely causes:
• A default document is not configured for the requested URL, and directory browsing is not enabled on the server.
Things you can try:
• If you do not want to enable directory browsing, ensure that a default document is configured and that the file exists.
• Enable directory browsing using IIS Manager.
1. Open IIS Manager.
2. In the Features view, double-click Directory Browsing.
3. On the Directory Browsing page, in the Actions pane, click Enable.
• Verify that the configuration/system.webServer/[email protected] attribute is set to true in the site or application configuration file.
Links and More Information
This error occurs when a document is not specified in the URL, no default document is specified for the Web site or application, and directory listing is not enabled for the Web site or application. This setting may be disabled on purpose to secure the contents of the server. View more information »

This is a rush at this point, as I'm quite behind on showing the new site to the client. Here's my .htaccess file in the wp folder:

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


Can't think of anythings else at this point. Maybe the files that start the php loop aren't right either? Could be a few things. My client's site is hosted on a Windows server at Web.com and I don't have any say in the matter. And the forums fixes I've tried for the past 36 hours have had no effect. PLEASE someone help and I'll be way happy and you'll get holiday moolah.

Answers (3)

2010-12-16

Pippin Williamson answers:

Go to example.com/test/wp-admin instead.


Scott Daris comments:

Hey Pippin. No, that's what I've been doing the whole time (minus the port 80 - that just shows up in the error). It's something to do with a default document not being set, or the loop not starting. Emergency! Seriously.

2010-12-16

Sébastien | French WordpressDesigner answers:

where is the index.php and what is his content ?
the path to the wordpress folder in the index.php is probably wrong


Scott Daris comments:

example.com/wordpress/index.php - the index page loads fine.

It's getting to http://example.com/wordpress/wp-admin/ where I get the 403.14 error.

Apparently it's a hierarchy thing, index.php in relation to Document and Folder roots, that's generating the error. But I haven't touched anything - it's the default wp folder structure. 2 days on this problem :(


Scott Daris comments:

Whoops, I meant to type:

example.com/test/index.php - the index page loads fine.

The http://example.com/test/wp-admin/ is where I get the 403.14 error.

(not example.com/wordpress/etc....)


Sébastien | French WordpressDesigner comments:

the index.php is here : example.com/wordpress/index.php

the url of the homepage is that : http://example.com

that's it ?

And the content of index.php is what ?


Scott Daris comments:

index.php contains:
</code><?php
/**
* Front to the WordPress application. This file doesn't do anything, but loads
* wp-blog-header.php which does and tells WordPress to load the theme.
*
* @package WordPress
*/

/**
* Tells WordPress to load the WordPress theme and output it.
*
* @var bool
*/
define('WP_USE_THEMES', true);

/** Loads the WordPress Environment and Template */
require_once('wp-blog-header.php');
?> </code>

That loads fine. It's EVERYTHING relative to example.com/test that doesn't load. In other words, the entire loop. For instance, when I click on the header image, it should take me home to example.com/test/index.php, but instead takes me to just example.com/test. there's a structural thing going on and I can't figure out how the files are 'talking' to each other.


Sébastien | French WordpressDesigner comments:

the index.php is here : example.com/wordpress/index.php

and you want that the url of the home = http://example.com

that's it ?


Scott Daris comments:

No. Everyone is not listening. The index.php is here :

example.com/wordpress/index.php

I want the homepage to be: example.com/wordpress/index.html
(I'll change permalinks later)

It's a <em>development test site</em> nested INSIDE the /wordpress folder. Everything is set up perfectly inside the /wordpress folder. Why is this so hard? I spend too much time and money searching for answers.


Sébastien | French WordpressDesigner comments:

if your index.php is on the "wordpress" folder and your home has an url like examaple.com/wordpress/index.html, why do you have a "test" folder and a "dev" folder in your htaccess ?!


Sébastien | French WordpressDesigner comments:

rename you .htaccess to .htaccessdisable and go to your admin


Scott Daris comments:

Nope - doesn't work. I did that a lonngggg time ago. Where are the Wordpress pros? The real geeks that know how to troubleshoot...


Sébastien | French WordpressDesigner comments:

if your index.php is on the "wordpress" folder and your home has an url like examaple.com/wordpress/index.html, why do you have a "test" folder and a "dev" folder in your htaccess ?!


Scott Daris comments:

Sorry - /test and /dev were old. It's now only /wordpress everywhere...but still the same problems.


Sébastien | French WordpressDesigner comments:

in a precedent message you write
<blockquote>example.com/wordpress/index.php

I want the homepage to be: example.com/wordpress/index.html</blockquote>

index.html ? Not index.php ... ?


have you do everithing about index.php or index.html ? (change permalink, add a redirection, change an extension...)


Sébastien | French WordpressDesigner comments:

Make a test :

1-save all the folders wordpress in your ftp.
2-change server and paster al the folders wordpress in the new server ftp.
3-go to install.php

if wp works fine the problem is in your first serverand it's not a wp-problem
if wp don't work, the problem is in wp.

2010-12-17

Peter Michael answers:

What is in your root .htaccess?

Also see [[LINK href="http://codex.wordpress.org/FAQ_Installation#What_is_the_403_error_I_get_when_trying_to_see_my_site.3F"]]http://codex.wordpress.org/FAQ_Installation#What_is_the_403_error_I_get_when_trying_to_see_my_site.3F[[/LINK]]