Error 500 when access only Index.php in wp-admin

  • solutionorange

    (@solutionorange)


    5 years, 10 months ago

    Strange issue.

    I can’t get into wp-admin/index.php
    I can get into any other admin links, after log in. Likes post.php, plugin.php, options-general.php, ..
    I’ve desactivate all plugins and themes and nothings changes, also i’ve brings back the original files from the wordpress installation folder into wp-includes and wp-admin, same results.

    I found a workaround for my customer with direct links to wp-admin/edit.php?post_type=page so he can works on his website.

    If anyone has an idea.. thanks.

    Here the system stats :

    ### WordPress Environment ###

    WP Version: 4.8.5
    WP Multisite: –
    PHP Memory Limit: 512 MB
    WP Debug Mode: ✔
    Language: en_US

    ### Server Environment ###

    Server Info: Apache
    PHP Version: 7.0.30
    PHP Post Max Size: 128 MB
    PHP Time Limit: 300
    PHP Max Input Vars: 5000
    SUHOSIN Installed: –
    ZipArchive: ✔
    MySQL Version: 5.5.5
    Max Upload Size: 128 MB
    DOMDocument: ✔
    WP Remote Get: ✔
    WP Remote Post: wp_remote_post() failed. Some theme features may not work. Please contact your hosting provider and make sure that https://envato.com/ is not blocked.
    GD Library: bundled (2.1.0 compatible)

    ### Active Plugins (20) ###

    InfiniteWP – Client: by Revmakx – 1.8.3
    Gravity Forms: by rocketgenius – 2.2.4.1
    WPML Multilingual CMS: by OnTheGoSystems – 4.0.3
    All-in-One WP Migration: by ServMask – 6.70
    BackupBuddy: by iThemes – 8.2.5.1
    Broken Link Checker: by Janis Elsts
    Vladimir Prelovac – 1.11.5

    Broken Link Checker: by Tobias Merz – 1.2.1
    Contact Form 7: by Takayuki Miyoshi – 5.0.2
    Duplicate Page: by mndpsingh287 – 2.6
    Fusion Builder: by ThemeFusion – 1.1.2
    Fusion Core: by ThemeFusion – 3.1.2
    Google XML Sitemaps: by Arne Brachhold – 4.0.9
    Gravity Forms Multilingual: by OnTheGoSystems – 1.3.17
    Health Check: by The WordPress.org community – 1.1.1
    Health Check: by Rinku Yadav – 1.6
    WPML CMS Nav: by OnTheGoSystems – 1.4.23
    WPML Media: by OnTheGoSystems – 2.3.3
    WPML Sticky Links: by OnTheGoSystems – 1.4.4
    WPML String Translation: by OnTheGoSystems – 2.8.3
    WPML Translation Management: by OnTheGoSystems – 2.6.3

Viewing 1 replies (of 1 total)
  • Moderator James Huff

    (@macmanx)

    Volunteer Moderator

    5 years, 10 months ago

    Internal server errors (error 500) are often caused by plugin or theme function conflicts, so if you have access to your Dashboard, try deactivating all plugins. If you don’t have access to your admin panel, try manually resetting your plugins (no Dashboard access required). If that resolves the issue, reactivate each one individually until you find the cause.

    If that does not resolve the issue, try switching to the Twenty Seventeen theme to rule-out a theme-specific issue. If you don’t have access to your Dashboard, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel (consult your hosting provider’s documentation for specifics on these), navigate to /wp-content/themes/ and rename the directory of your currently active theme. This will force the default theme to activate and hopefully rule-out a theme-specific issue.

    If that does not resolve the issue, it’s possible that a .htaccess rule could be the source of the problem. To check for this, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel, and rename the .htaccess file. If you can’t find a .htaccess file, make sure that you have set your SFTP or FTP client to view invisible files.

    If you weren’t able to resolve the issue by either resetting your plugins and theme or renaming your .htaccess file, we may be able to help, but we’ll need a more detailed error message. Internal server errors are usually described in more detail in the server error log. If you have access to your server error log, generate the error again, note the date and time, then immediately check your server error log for any errors that occurred during that specific time period. If you don’t have access to your server error log, ask your hosting provider to look for you.

Viewing 1 replies (of 1 total)
  • The topic ‘Error 500 when access only Index.php in wp-admin’ is closed to new replies.