Website is down
-
Hello to all! I am a newbie so please bear with me. I hope this is the correct place to ask for help.
This site was built Feb 2024 and worked until approx the end of March 2014 when it was not assessible. The site was up but not usable. I am trying to revive the site instead of starting over. We have tried backups but they seem corrupt and now the site is completely down.
The page I need help with: [log in to see the link]
-
The site is online for me.
Would you please describe what you mean by “The site was up but not usable.” and “now the site is completely down”?
Hey James, so when we first noticed an issue we would have a completely blank white page. I could go to cached or saved links to see posts or other things but I could not navigate the website. The site owner went to support and they suggested to restore it and he did but now it is like everything is lost.
I did not help create the site but I am involved now trying to repair or rebuild but I am new.
You are correct technically the site is up but it is not what was created and usable.
This is from the owner and site builder of the timeline and symptoms
Site’s main page down but direct links to the site worked. Opened up a case. They said the root cause was a plugin issue, specifically the BlueHost created plugin for WordPress, and said it was a WordPress issue, even though the plugin is designed by BlueHost and on their platform. They recommended a restore from a backup. After doing a restore the the links stopped working.He tried a restore from the 1 week backup with a 500 server error and and backup from the 1 month backup with the same 500 server error. They said the index file being broken.
-
This reply was modified 1 year, 11 months ago by
youvegotmail.
Ok, for the restore, it sounds like they restored a backup prior to customizing the site. Do you have your own backups you can restore from? https://developer.wordpress.org/advanced-administration/security/backup/database/#restoring-your-database-from-backup
If not, ask your hosting provider’s support if there’s a more recent backup they can restore.
As for the error you were seeing, 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 Dashboard, try manually resetting your plugins (no Dashboard access required). If that resolves the problem, reactivate each one individually until you find the cause.
If that does not resolve the problem, try switching to the Twenty Twenty-Three theme to rule out a theme-specific problem. 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 problem.
If that does not resolve the problem, 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, ensure that you have set your SFTP or FTP client to view invisible files.
If you couldn’t resolve the problem by resetting your plugins and theme or renaming your .htaccess file, we might 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. If you don’t have access to your server error log, ask your hosting provider to look for you.
We only need the error log entries within a minute or two of generating the error. Sending the entire error log would be unhelpful.
There were three backups available and all three were no good. We did not back it up, lesson learned there.
I tried two other themes with the same result, no change.
I have full access to the dashboard could you help direct me to getting the logs?
I enabled the BlueHost Plugin and now the page is white like I was saying.
[Sat Apr 27 15:54:52.425491 2024] [autoindex:error] [pid 795814:tid 22686300632832] [client 174.53.55.94:0] AH01276: Cannot serve directory /home3/ltgayrmy/public_html/wp-content/plugins/bluehost-wordpress-plugin/: No matching DirectoryIndex (index.html.var,index.htm,index.html,index.shtml,index.xhtml,index.wml,index.perl,index.pl,index.plx,index.ppl,index.cgi,index.jsp,index.js,index.jp,index.php4,index.php3,index.php,index.phtml,default.htm,default.html,home.htm,index.php5,Default.html,Default.htm,home.html) found, and server-generated directory index forbidden by Options directive, referer: https://arguntrader.net/wp-admin/admin.php?page=bluehost
[Sat Apr 27 15:54:48.326946 2024] [autoindex:error] [pid 795814:tid 22686372075264] [client 174.53.55.94:0] AH01276: Cannot serve directory /home3/ltgayrmy/public_html/wp-content/plugins/bluehost-wordpress-plugin/: No matching DirectoryIndexError logs will be in your hosting account’s control panel, consult your hosting provider’s documentation or support for specifics.
Again, we only need the error log entries within a minute or two of seeing the 500 error on the screen, or seeing a blank screen. Sending the entire error log would be unhelpful.
Sorry, looks like the log entries were caught as spam.
Cannot serve directory /home3/ltgayrmy/public_html/wp-content/plugins/bluehost-wordpress-plugin/: No matching DirectoryIndex
That’s an odd one. Was that within a minute or two of seeing the 500 error on the screen, or seeing a blank screen?
And, why were you trying to access that directory directly?
-
This reply was modified 1 year, 11 months ago by
The topic ‘Website is down’ is closed to new replies.