Getting database connection error instead of Page not found error

  • hcleary

    (@hcleary)


    13 years, 3 months ago

    I am runnig WP 3.0.4 multi-site with subfolders. I am running BP 1.2.7 on a secondary blog, blogs.otis.edu/community. If you go to base URL, visitors are redirected that secondary blog.

    I can access the site, log in and do stuff. The database seems fine. As long as the URL contains an existing /BLOGNAME, e.g. blogs.otis.edu/otisvrc, the site behaves. 404 Errors will appear for blogs.otis.edu/otisvrc/TYPO.

    If the /BLOGNAME doesn’t match one of the subfolders, e.g. blogs.otis.edu/summer, it displays the page “Error establishing database connection.” instead of a 404 Page Not Found Error.

    Any ideas why? Thanks.

Viewing 1 replies (of 1 total)
  • Thread Starter hcleary

    (@hcleary)

    13 years, 3 months ago

    I have more information provided by my sysadmin:

    “After closer inspection it was discovered that the ‘Error establishing …’ message is generated by the WordPress application and not the Apache server. This behavior indicates that a routine within WordPress is inspecting all URL request before they are send to the Apache web engine.”

    Can anyone point me to where the URL inspections happen in the code? Or could this be fixed with an alteration to the .htaccess or wp-config.php files?

Viewing 1 replies (of 1 total)
  • The topic ‘Getting database connection error instead of Page not found error’ is closed to new replies.