‘Internal Server Error’ on site and can’t reach dashboard

• 

  blogqinninn · Member · Oct 19, 2023 at 11:03 am

  • Copy link
  • Add topic to favorites

  I found my site, which started showing ‘Internal Server Error’ message and could not function properly, it start showing the same message when I tried to login the admin dashboard by adding ‘wp-admin’ after the domain. I then tried to login via Bluehost, but same problem happened.

  I tried to login my WordPress account and check the dashboard but most of the pages are empty in it, like in the post page it said ‘You haven’t created any content yet.’ even if there are clearly numbers next to the Published and Drafts. There’s a message popped up at the top that said ‘Jetpack can’t communicate with your site due to a critical error on the site.’ So I checked for solutions which told me to ‘Deactivate the plugin or switch the theme’. However, neither of them has shown properly in my dashboard just like the situation I mentioned on the post page.

  Therefore, I’m reaching out for help and hoping for further assistance. Thank you.

  WP.com: Yes
  Jetpack: Yes
  Correct account: Yes

  The blog I need help with is: (visible only to moderators and staff)

• 

  amajeedali · Member · Oct 19, 2023 at 11:13 am

  • Copy link

  I guess your wordpress is corrupted that cause this error, so try to update the wordpress, and try disable all plugins, and go to themes, and apply the default Twenty Seventeen or Twenty Twenty-Three themes. May be it may helps you to see the page is working properly or not

• 

  blogqinninn · Member · Oct 19, 2023 at 11:41 am

  • Copy link

  oops, I just found the solution to this,

  1. First login to the Bluehost account, and click on ‘Advanced’.
  2. It would automatically link to the cPanel, find ‘File Manager’ in the FILES column and click on it.
  3. In File Manager, find ‘public_html’ and click on it.
  4. Press the ‘Settings’ button on the top-right-hand corner, click ‘Home Directory’ and tick ‘Show Hidden Files (dotfiles)’, and Save.
  5. Find ‘.htaccess’ and rename it to ‘.htaccess-old’
  6. Refresh your own website to see if your website has come back or not. Or try add ‘/nocache’ after your domain.

  The above steps do work on my situation, hope it helps.

• 

  amajeedali · Member · Oct 19, 2023 at 11:48 am

  • Copy link

  Great, thanks for sharing your answer to me, i hope it will helps all the members in this Worpdress Forum who face this kind of issues.