Viewing 11 replies - 1 through 11 (of 11 total)
  • Moderator James Huff

    (@macmanx)

    Internal server errors (error 500) are often caused by plugin or theme function conflicts, so if you have access to your admin panel, try deactivating all plugins. If you don’t have access to your admin panel, try manually resetting your plugins. 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 Fourteen theme to rule-out a theme-specific issue. If you don’t have access to your admin panel, access your server via FTP or SFTP, 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 FTP or SFTP and rename the .htaccess file. If you can’t find a .htaccess file, make sure that you have set your FTP or SFTP 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 time period. If you don’t have access to your server error log, ask your hosting provider to look for you.

    Thread Starter Africa Travel Guide

    (@traveltorastafrica)

    Hi MacManX,

    Thanks for the message. At the moment, I have deactivated all plugins and the themes accept Twenty telve, thirteen and forteen.

    Still it shows the same proble. Please, take a loo and let me know if there is anything that I could have misssed.

    Regards
    Elly

    Moderator James Huff

    (@macmanx)

    You’re missing the rest of my reply above. 😉

    If you still have the problem with all plugins deactivated and Twenty Fourteen active, proceed to .htaccess testing and then the server error log.

    Check Server log for the cause of internal server error. If you dont find any error, check your .htaccess for any error. Try removing your .htaccess and run website, if it runs then the problem is in .htaccess.

    Moderator James Huff

    (@macmanx)

    . . . which is exactly what I said 2 days ago and just now an hour ago?

    Thread Starter Africa Travel Guide

    (@traveltorastafrica)

    Dear All,

    1. If we can slow down. I have removed .htaccess and instead it brought the empty white screen.
    2. I actually do not know how a activate Twenty fourteen when i don’t access the wp-admin.
    3. I don’t know how to check the server log.

    If I can be able to do the above then may be it could word but unfortunately, I don’t know with my little knowledge of wp. Any assistance is highly appreciated

    Regards
    Elly

    Looks like your hosts are JustHost. So, here are some help pages to assist you reading your logs:

    https://my.justhost.com/hosting/help/562
    https://my.justhost.com/hosting/help/315

    Thread Starter Africa Travel Guide

    (@traveltorastafrica)

    Hi Dave,

    I have been able to access the log error file and this is what I can see (latest)

    41.138.212.69 – – [19/Aug/2014:06:57:52 -0600] “GET /favicon.ico HTTP/1.1” 500 947 “-” “Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0”
    112.5.236.64 – – [19/Aug/2014:06:58:37 -0600] “POST /wp-login.php?action=register HTTP/1.0” 500 1029 “-” “Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.23) Gecko/20110920 Firefox/3.6.23”

    Is there anything that I can get from this?

    Many thanks
    Elly

    Moderator James Huff

    (@macmanx)

    2. I actually do not know how a activate Twenty fourteen when i don’t access the wp-admin.

    From the first reply:

    Try switching to the Twenty Fourteen theme to rule-out a theme-specific issue. If you don’t have access to your admin panel, access your server via FTP or SFTP, 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.

    Is there anything that I can get from this?

    No, it looks like your log isn’t detailed enough. If switching to the default theme, as directed above, doesn’t work, generate the error again, note the date and time, then immediately ask your hosting provider to check their error log for you.

    Thread Starter Africa Travel Guide

    (@traveltorastafrica)

    Hi,

    I have renamed the theme and seems not to be working. Is there a way I can activate Thwenty fourteen them fro the Cpanel?

    On accessing the .htaccess file a) renaming it has instead brought an empty white screen and b) this is what is there: # BEGIN WordPress
    <IfModul

    # 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

    Is there anything wrong there?

    Ths is frustrating as i don’t know what to do.

    Moderator James Huff

    (@macmanx)

    I have renamed the theme and seems not to be working. Is there a way I can activate Thwenty fourteen them fro the Cpanel?

    If a /wp-content/themes/twentyfourteen/ directory exists, it will be forced to activate if you change the name of /wp-content/themes/[current-theme]/ to anything else, like /wp-content/themes/bad-theme/

    If you do not have a /wp-content/themes/twentyfourteen/ directory, you will need to download Twenty Fourteen from https://wordpress.org/themes/twentyfourteen and manually install it via FTP (expand the .zip file and upload the twentyfourteen folder to /wp-content/themes/).

    That .htaccess file looks fine, so if you couldn’t fix the issue by resetting plugins, forcing Twenty Fourteen to activate, and renaming .htaccess, it’s time to contact your hosting provider as directed above.

Viewing 11 replies - 1 through 11 (of 11 total)

The topic ‘Internal Server Error’ is closed to new replies.