“Index of /wp-admin” on first login

try adding this line to the wordpress .htaccess file

DirectoryIndex index.php index.html

I didn’t have an .htaccess file, so I created one. Not being that knowledgeable, I’m assuming that the only text I need in that file is the text you provided?

I checked around and wasn’t able to figure out if I needed to put anything else in there.

Again, many many thanks.

/edit – I also changed permissions on .htaccess to 666.
/second edit – Interestingly enough, I just clicked on the index.php file from the original file directory screen, and it took me to the Dashboard. So that’s good.

But I’d still obviously have it send me there immediately.

Hopefully that narrows things down a little.

Just an update; I tried deleting all the previous existing content (and using a separate “wordpress” directory (with the proper addresses set in the “general” section of the dashboard, yes)) but all I get upon doing that is a basic screen telling me Apache has been installed on this site/server.

A contact at my hosting provider did suggest, upon creating a database for me, this: “You should have permissions to install the PHP code, but if not, let me know and I can install it.”

Could that be the problem? Otherwise, I’m just repeatedly getting the directory screen in my browser, which is an obvious security problem.

If you’re getting a directory screen, there’s more going on than just PHP not being installed, as the index.php should be loading and simply produce a blank screen if PHP is not installed. If an index.php file does in fact exist in /wp-admin/, this definitely sounds like a hosting issue, and you should probably continue to work with your hosting provider on a solution.

I’m having the same problem, but it is on a brand new install. However, I can use edit.php and edit posts and pages. I just cannot display anything in reader mode. If I click on a View Post link it takes me to the correct URL, but it shows the directory listing instead.
I can see the posts showing up the database as well. So this means that PHP is working, MYSql is working. All the PHP files appear to be there. It seems like a bug in this release 2.9.2.
I’m running this on Windows 7.

It’s definitely not a WordPress bug. Otherwise, the millions of us who use it would have seen that too and there would have been an emergency update released months ago.

Would you mind sharing a link to your blog?

Hello I have also problem on the /wp-admin. I installed WP on my addon domain on hostsmonter lastnight. Everything seems ok then, I can access the dashboard and setup the basic jobs (installing theme, plugins, etc.).

But when I tried logging in on my site using mysite.com/wp-admin this morning, I get a blank page. Then I tried accessing it using mysite.com/login.php, it gets me to the login screen but when I hit enter, it gets me to a black page again.

Please any one know what might be the problem? I really appriciate you help. Thank you.

Algen

algen, please create your own thread. Your problem is unrelated to the issues being discussed here.

Unfortunately, I don’t have my site live yet. When I say bug, I don’t necessarily mean that it is a bug with the ongoing usage of the product. I mean that something is missing in the installation or it doesn’t work on Windows 7.

Does anyone have a working installation on Windows 7?

yes I do

I use this and it works every time
https://www.tamba2.org.uk/wordpress/xampp/

Here’s some detailed information that should help. I believe it is a problem with running php 5.2.13.

There is a problem in the code when it calls the action “template_redirect”. When it is running the “redirect_canonical” function and it gets ready to return on this line
—
if ( !$redirect_url || $redirect_url == $requested_url ) // yes, again — in case the filter aborted the request
{
file_put_contents(‘log_file_name’, ‘returning false’, FILE_APPEND);
return false;
}
—–
It dies. It doesn’t make a clean return back to the caller.

When I comment out the line
/* add_action(‘template_redirect’, ‘redirect_canonical’); */
so that the action doesn’t run, then it works fine and I can see my posts.

Is this sufficient to get this back to the developers?

That may be sufficient, I suppose. The devs will have a better idea of whether or not that is actually a problem. Follow the guide here:

https://codex.www.ads-software.com/Reporting_Bugs

I had the same problem as skirkster and it was caused by the directory index variable in the Apache config file not including index.php.

Basically I modified the Directory Index line to read

DirectoryIndex index.html index.php index.htm index.cgi

and it worked. This was running Apache 2.2.4 and PHP 5.3.1 on Windows

HTH
Gaz

major problem for wp-login.php my site problem Username —–

Password —— but not support this password or user name

my site login details are true but after

ERROR: Incorrect password. Lost your password?
ERROR: Cookies are blocked or not supported by your browser. You must enable cookies to use WordPress.

send your replay

having a similar problem skirkster described – with no .htaccess file!
My site is running on:
Red Hat 7.1 utilizing PHP 4.4.1 and MySQL 3.23.47. On our Fedora Core 3 Fully Managed servers, we are utilizing PHP 5.0.5 and MySQL 4.0.

after a painful install the only thing visible is the directory index