• Resolved JeskaD

    (@jeskad)


    Hi all.

    I updated my self-hosted wordpress blog on 12/31 and have not been able to access my site since then.

    Today, I attempted to manually reinstall via FTP following these directions, disabling plugins, removing and replacing files, the whole bit – and I still get nothing but 500 server errors everytime I try to access anything on my site (including the wp-admin)

    The weirdest thing is that I can access this page:
    http://jeska.org/wp-admin/upgrade.php
    Which tells me my site is all up to date.

    Anyone have any suggestions on what to try next? I’ve got another wordpress blog that I host on the same server which has updated and is working fine, so I don’t think it’s my hosting (although I’ve filed a support ticket just in case).

    Thanks in advance for any tips.

Viewing 9 replies - 1 through 9 (of 9 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 (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 Fifteen theme to rule-out a theme-specific issue. If you don’t have access to your admin panel, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel, 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 time period. If you don’t have access to your server error log, ask your hosting provider to look for you.

    Thread Starter JeskaD

    (@jeskad)

    Thanks. renaming my theme solved it. Now to figure out what’s wrong with the theme! 😉

    Thread Starter JeskaD

    (@jeskad)

    Hmm. Now my posts are not being found. I’m getting 404 errors for the posts…

    Moderator James Huff

    (@macmanx)

    What is the name of the theme, and where did you get it from?

    Moderator James Huff

    (@macmanx)

    For the 404, try re-saving your permalink structure at Settings/Permalinks in your admin panel. If WordPress cannot automatically edit the .htaccess file, it will provide manual instructions after saving.

    Thread Starter JeskaD

    (@jeskad)

    Thanks, that helped with the 404 error. (how frustrating!)

    The theme is Mani – https://creativemarket.com/IlgeloDesign/257751-Mani-MultiPurpose-Wordpress-Blog

    I’ll start digging into their help to see if they have any ideas…

    Moderator James Huff

    (@macmanx)

    Ok, since that is a commercial theme, we ask that you please go to their official support channel, so you can get support from the people who know it best.

    To reach their support, click the envelope icon on the Creative Market page for the theme.

    Forum volunteers are also not given access to commercial products, so they would not know why it is not working properly. Other community members who may have faced your issue might be able to help you but your best bet is your product’s developer. Keep in mind we encourage you to use the official support venues, as it allows the developers to be aware of issues with their code and gives back to the community in a more robust way.

    Thread Starter JeskaD

    (@jeskad)

    Thanks James – I think I got it all sorted out. Still not sure what went sideways, but hey – it’s fixed now 😉

    THANK YOU SO MUCH! <3

    Moderator James Huff

    (@macmanx)

    You’re welcome!

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

The topic ‘Self hosted – Update went sideways’ is closed to new replies.