500 Internal Server Error on blog only

  • Resolved cathytxtwfr

    (@cathytxtwfr)


    11 years, 1 month ago

    Hello, I tried to upgrade the my Jetpack plugin, and now my entire blog has the “500 Internal Server Error”

    I have tried all the solutions listed here: https://www.wpbeginner.com/wp-tutorials/how-to-fix-the-internal-server-error-in-wordpress/

    -Renaming my .htaccess did nothing
    -Increasing my .php memory limit by adding a line to wp-config.php did nothing
    -Deactivating plugins by renaming the folder did nothing
    -Re-uploading core files did nothing

    Now, all my wordpress stuff is located here: https://cathywu.com/journal/ – and the stuff under this folder is the ONLY place where I get the 500 error. If I go to any other site on my domain, such as https://cathywu.com/index.php or cathywu.com, they load and work perfectly.
    So I am not sure if this is a host issue or not since the non wordpress folders work fine. Yet, I have tried all the solutions and the last step is contacting the hosting company.

    What should I do?
    thank you for any advice.

    Cathy

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

  • Have you tried deleting the jetpack directory from the /wp-content/plugins directory? If the Jetpack upgrade seems to have triggered the issue, try removing it.

    If that doesn’t work, try disabling all plugins. If that rectifies the issue, enable them again one by one until the site breaks to narrow down the source of the issue.

    Thread Starter cathytxtwfr

    (@cathytxtwfr)

    Yes, I have deleted the jetpack folder and nothing changed. I also renamed the entire plugins folder and the 500 error is still there

    I’m not seeing a 500 error accessing your site at this point. Perhaps your browser has the error cached?

    Thread Starter cathytxtwfr

    (@cathytxtwfr)

    Hi, I just received this note from my host:

    “The errors were caused by changes in the htaccess. Specifically the error was Bad Flag Delimiter. The flag delimiters are the [L], [OR], etc tags at the end of some of the lines. I’m not sure which was causing the error. I moved the modified .htaccess to htaccess.txt. I replaced it with the default htaccess (modified for /journal/). “

    The site is back up, but now my multisite URLs are pointing to my domain name instead of the multisites. For example https://cathywu.com/journal/kalali/wp-admin/ should point to my wordpress multisite dashboard, but instead it is going to https://cathywu.com/ .

    I can, however, access the main wordpress dashboard, but cannot do anything with my sub blogs.

    Thread Starter cathytxtwfr

    (@cathytxtwfr)

    Ok, I kind of fixed it… fingers crossed.

    I used the codes from here to make a new htaccess: https://codex.www.ads-software.com/Multisite_Network_Administration

    And everything came back! But since I had deleted jetpack, none of my custom CSS was working and my site looked very strange. So i redownloaded and installed jetpack, then my CSS came back as well.

    Whew, for now I think everything is okay. This has shown how every little thing is connected and affects everything, one little click can wreck all sorts of havoc, but can also restore things too. Thanks for the help!

    Glad it’s working for you!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘500 Internal Server Error on blog only’ is closed to new replies.