• Resolved vladimirknight

    (@vladimirknight)


    Hi guys!

    I’ve got a rather pesky issue with several wordpress installations.
    Whenever I try to visit wp-admin subpages, such as
    /wp-admin/update-core.php
    /wp-admin/themes.php
    /wp-admin/plugins.php

    etc etc., the pages all return a 404 error. /wp-admin/widgets.php is also severely crippled but at least it loads half of it.
    Jetpack integration on the WordPress dashboard is also broken, but the corresponding stats on wordpress.com are still appearing with no problem.

    It also prevents me from updating existing pages, as /wp-admin/post.php, which it redirects to after editing a post returns a 404 error. Interestingly enough, the changes to the page are still saved.

    Here’s some quick info:

    – I run three sites, all on one hosting account with one provider.

    – The only thing the three sites share is the host. The themes, plugins and everything else are completely different.

    – This started when 4.3 was released and affects all three sites. On one of them, I cannot access the /wp-admin/ at all. I updated the main site through Softaculous (since the update page doesn’t work) and the issue persists throughout 4.3 and 4.3.1.

    Because the issue is shared across all sites which have nothing in common between them, I’m 90% sure it’s the host but I thought I’d ask here before I contact them. I have no idea what I would tell them or ask them to look at.
    I’ve done all the “usual” things of removing all plug-ins, etc and it didn’t change a thing.

    Long story short, my wp-admin is broken across three different sites hosted with one provider.
    Is there anything on my end I can look at, change, fix, etc., with my installation?
    If I have to talk with my host, what could I tell them?

    Thanks for reading, folks. <3

    ~Vladimir

Viewing 7 replies - 1 through 7 (of 7 total)
  • Hello, Vladimir, & welcome to the WordPress support forum. Could you please:
    * Provide us w/your site’s url’s? &
    * Paste your .htaccess file here for us to look at?

    Thread Starter vladimirknight

    (@vladimirknight)

    Certainly, thanks for your response!

    The three sites are:
    https://youarelowonhealth.com
    https://knightofsnow.com
    https://vladimirknight.com

    The .htaccess for all three is identical:

    AddHandler application/x-httpd-php52 .php .php5 .php4 .php3
    
    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ - [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>
    
    # END WordPress

    _____________________________________________
    One interesting thing I’ve noticed while playing around with the installation a while back – renaming (or completely removing) the plugin folder allows me to access the /wp-admin/plugins.php page. Keeping the folder, however, even if it’s completely empty, still gives the usual 404 error.

    I thought it might be a database error because of this, but checking through cpanel and Softaculous it appears to be pointing at the correct database. I’m stumped. ??

    Vladimir, Where are your addon domains pointing? You can go into your hosting provider’s control panel under the domain subheading to determine this.

    Also, in some hosting provider’s control panels, & I’m thinking CPanel specifically, there are error logs that may prove very helpful. An error log may also be found in your root folder, as well as subfolders of themes or plugins that are throwing errors. But the site error logs in particular could be very revealing here.

    Thread Starter vladimirknight

    (@vladimirknight)

    The addon domains point to [home]/public_html/[addondomain] which was the default. I did mean to change it at one point, but never got around to it. They can also be accessed via [addondomain].[maindomain].com.

    This setup worked for months before 4.3 was released (for the record, I don’t think 4.3 broke anything) and I’m just confused what did break.

    The error log in cpanel is completely empty (is meant to show the last 300 entries, but either there are none or it’s not showing them).

    In the main site, (youarelowonhealth) the error log in the root does have entries, though most are a month old (Aug 27) with the most recent on 10 September. These are the last two entries, the other 10 entries from Aug 27th are all “WordPress database error Table”.

    [27-Aug-2015 12:19:26] WordPress database error Table 'snknight_wp745.wp_posts' doesn't exist for query SELECT SQL_CALC_FOUND_ROWS  wp_posts.ID FROM wp_posts  WHERE 1=1  AND wp_posts.post_type = 'post' AND (wp_posts.post_status = 'publish')  ORDER BY wp_posts.post_date DESC LIMIT 0, 3 made by require('wp-blog-header.php'), require_once('wp-includes/template-loader.php'), include('/themes/hueman/404.php'), get_sidebar, locate_template, load_template, require_once('/themes/hueman/sidebar.php'), get_template_part, locate_template, load_template, require('/themes/hueman/sidebar-2.php'), dynamic_sidebar, call_user_func_array, WP_Widget->display_callback, AlxPosts->widget, WP_Query->__construct, WP_Query->query, WP_Query->get_posts
    
    [10-Sep-2015 23:43:36] WordPress database error Deadlock found when trying to get lock; try restarting transaction for query DELETE FROM <code>wp_options</code> WHERE <code>option_name</code> = '_site_transient_timeout_security_report_performed_recently' made by require('wp-load.php'), require_once('wp-config.php'), require_once('wp-settings.php'), do_action('init'), call_user_func_array, Jetpack::perform_security_reporting, get_site_transient, delete_site_option, delete_option

    Thank you so much for your time, Jackie.

    Vladimir, each domain should point to its own folder, i.e., youarelowonhealth, knightofsnow, etc.

    Just out of curiosity, what happens when you rename the plugins folders & change to default themes on all 3 sites? Can you get to a dashboard on vladimirknight.com that way?

    Lastly, do you know how much memory you’ve got? How big are your databases?

    Thread Starter vladimirknight

    (@vladimirknight)

    On vladimirknight, renaming the plugin folder lets me log into the dashboard, but the subpages (like /wp-admin/update-core.php) still return a 404.

    Same for knightofsnow. On youarelowonhealth, I was always able to log into the dashboard, but the subpages return a 404.

    Disabling the theme via ftp (by renaming the individual theme’s folder, since I can’t access /themes.php) blanks out the sites. Every page becomes plain white, and the wp-admin pages that gave a 404 before now only come up with these white pages.

    The databases for knightofsnow and vladimirknight are about 3.5 MB each, the one for youarelowonhealth is slightly over 13 MB.

    My host plan is “unlimited” everything (on shared hosting). Total disk usage across all 3 sites is 620MB.

    If it makes a difference, the main domain is knightofsnow with the other 2 being addon domains.

    Vladimir, any time you disable the theme, the site front end won’t work. You should be able to log into the dashboard, though.

    Here’s what I think your next steps are.
    * Ask your hosting provider to search its server logs, specifically looking for out-of-memory & ModSec errors your site may be throwing.
    * Go into your wp-config.php & change:
    define(‘WP_DEBUG’, false);
    to define(‘WP_DEBUG’, true);
    Note: This is a security risk, & you’ll want to reset that as soon as we gain needed information, but in this case it may prove helpful.

    I’d also like to know if you’re running any security plugins, WordFence, for example, as these can block IP’s, etc.

    Lastly, I can offer to set up a staging site on my server for you to see if your site works as it should. Clearly, if it does, then you’ve got hosting issues. If it doesn’t, then we look further at where the installation has gone awry or if there are out-of-memory errors, etc, that are contributory.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘wp-admin subpages return a 404 error’ is closed to new replies.