• I cannot access my website and the following message appears: There has been a critical error on this website. The link to my website is: delamanodemaria.com
    Please help.
    Héctor L. Márquez

Viewing 13 replies - 1 through 13 (of 13 total)
  • Please enable the debug log and then get the error message then we’ll able to guide how to fix that error.

    You can read about debugging here:

    Debugging in WordPress

    Thread Starter hectorops

    (@hectorops)

    Thank you for your response. Unfortunately, I have little to no knowledge of the technical aspects of web pages. How and where do I enable the “debug log”? Especially since I cannot access the webpage.

    • This reply was modified 2 years, 8 months ago by hectorops.
    Thread Starter hectorops

    (@hectorops)

    This was the last activity before the “critical error”, as reported by Jetpack:

    July 6, 2022
    9:09 PM
    Jetpack
    De la mano de María is unresponsive
    Site unavailable
    9:01 PM
    
    Gutenberg 13.6.0
    Plugin updated
    9:01 PM
    
    Gutenberg 13.5.2
    Plugin updated
    4:21 PM
    
    Héctor L. Márquez, O.P.
    Administrator
    REFLEXIóN PARA EL JUEVES DE LA DECIMOCUARTA SEMANA DEL T.O. (2) 07-07-22
    Post published

    You can access error logs from your Cpanel as well if you are not good with technical things. Without the error message it’s hard to know which plugin is causing the issue.

    You can ask the hosting support to access the error logs then you can provide us the last 10-20 error logs, then we will be able to guide you to resolve the issue.

    Thread Starter hectorops

    (@hectorops)

    You suggested that I ask the hosting support to access the error logs so I can provide you with the last 10-20 error logs, so you will be able to guide me to resolve the issue. I have?accessed the wordpress.com?site and do not find any link to obtain hosting support.

    However, I was able to run a debug through Jetpack and this is the return I received:

    XML-RPC is not responding correctly ( 500 )
    It looks like XML-RPC is not responding correctly. Please make sure XML-RPC is turned on for your site and is set up to respond to all content types. You can test this yourself by running the following command from the command line:
    
    curl -A 'Jetpack by WordPress.com' -d '<methodCall><methodName>demo.sayHello</methodName></methodCall>' https://delamanodemaria.com/xmlrpc.php
    The answer should be:
    
    <?xml version="1.0" encoding="UTF-8"?>
    <methodResponse>
      <params>
        <param>
          <value>
          <string>Hello!</string>
          </value>
        </param>
      </params>
    </methodResponse>
    If you continue to get this error, please check out our troubleshooting guide or contact support.

    I tried running the suggested command and did not get a response. Also, with my limited technical knowledge I have tried to access the files to deactivate the plugins by installing several external FTP client servers and none can access the host site.

    Where do we go from here?

    Héctor

    I think, you’re using GoDaddy as your hosting, so you need to login into your goaddy account and access the cpanel and then check for error logs or goDaddy hosting support for help accessing the php Error logs.

    Once you’ll get the log, you will be able to find which plugin is causing the issue then you can disable the plugin by renaming it using FTP Client or File Manager from you hosting/Cpanel.

    Thread Starter hectorops

    (@hectorops)

    This is the error log I received from GoDaddy (I as not aware that my “host” is GoDaddy):

    [Mon Jul 11 07:37:00.104819 2022] [autoindex:error] [pid 3889492:tid 140315113240320] [client 20.0.40.253:62010] AH01276: Cannot serve directory /home/yqxeia19y71u/public_html/wp-admin/css/: No matching DirectoryIndex (index.php,index.shtml,index.html,index.htm,home.html,home.htm,index.php5,welcome.html,welcome.htm) found, and server-generated directory index forbidden by Options directive, referer: binance.com
    [Mon Jul 11 04:34:38.374947 2022] [autoindex:error] [pid 2077608:tid 140314924422912] [client 79.124.8.3:56933] AH01276: Cannot serve directory /home/yqxeia19y71u/public_html/wp-admin/css/: No matching DirectoryIndex (index.php,index.shtml,index.html,index.htm,home.html,home.htm,index.php5,welcome.html,welcome.htm) found, and server-generated directory index forbidden by Options directive, referer: binance.com
    [Mon Jul 11 03:48:00.669019 2022] [autoindex:error] [pid 2461179:tid 140314997851904] [client 193.142.146.138:61158] AH01276: Cannot serve directory /home/yqxeia19y71u/public_html/wp-admin/css/: No matching DirectoryIndex (index.php,index.shtml,index.html,index.htm,home.html,home.htm,index.php5,welcome.html,welcome.htm) found, and server-generated directory index forbidden by Options directive, referer: binance.com
    [Mon Jul 11 03:35:17.675485 2022] [autoindex:error] [pid 2028660:tid 140315102750464] [client 194.87.84.194:52493] AH01276: Cannot serve directory /home/yqxeia19y71u/public_html/wp-admin/css/: No matching DirectoryIndex (index.php,index.shtml,index.html,index.htm,home.html,home.htm,index.php5,welcome.html,welcome.htm) found, and server-generated directory index forbidden by Options directive, referer: binance.com
    [Mon Jul 11 02:12:44.046515 2022] [autoindex:error] [pid 2066716:tid 140314987362048] [client 194.87.84.46:59640] AH01276: Cannot serve directory /home/yqxeia19y71u/public_html/wp-admin/css/: No matching DirectoryIndex (index.php,index.shtml,index.html,index.htm,home.html,home.htm,index.php5,welcome.html,welcome.htm) found, and server-generated directory index forbidden by Options directive, referer: binance.com
    [Mon Jul 11 01:17:03.327851 2022] [autoindex:error] [pid 229839:tid 140314934912768] [client 185.81.157.30:58801] AH01276: Cannot serve directory /home/yqxeia19y71u/public_html/wp-admin/css/: No matching DirectoryIndex (index.php,index.shtml,index.html,index.htm,home.html,home.htm,index.php5,welcome.html,welcome.htm) found, and server-generated directory index forbidden by Options directive, referer: binance.com
    [Sun Jul 10 19:23:28.704459 2022] [autoindex:error] [pid 3280214:tid 140314934912768] [client 103.142.204.121:62684] AH01276: Cannot serve directory /home/yqxeia19y71u/public_html/wp-content/uploads/2022/07/: No matching DirectoryIndex (index.php,index.shtml,index.html,index.htm,home.html,home.htm,index.php5,welcome.html,welcome.htm) found, and server-generated directory index forbidden by Options directive
    [Sun Jul 10 19:23:21.092762 2022] [autoindex:error] [pid 3142516:tid 140315050301184] [client 103.142.204.121:61670] AH01276: Cannot serve directory /home/yqxeia19y71u/public_html/wp-content/uploads/: No matching DirectoryIndex (index.php,index.shtml,index.html,index.htm,home.html,home.htm,index.php5,welcome.html,welcome.htm) found, and server-generated directory index forbidden by Options directive
    [Sun Jul 10 16:29:49.983436 2022] [autoindex:error] [pid 1396459:tid 140314871973632] [client 193.142.146.138:60232] AH01276: Cannot serve directory /home/yqxeia19y71u/public_html/wp-admin/css/: No matching DirectoryIndex (index.php,index.shtml,index.html,index.htm,home.html,home.htm,index.php5,welcome.html,welcome.htm) found, and server-generated directory index forbidden by Options directive, referer: binance.com
    [Sun Jul 10 14:14:13.241427 2022] [autoindex:error] [pid 1720910:tid 140315081770752] [client 193.142.146.138:61013] AH01276: Cannot serve directory /home/yqxeia19y71u/public_html/wp-admin/css/: No matching DirectoryIndex (index.php,index.shtml,index.html,index.htm,home.html,home.htm,index.php5,welcome.html,welcome.htm) found, and server-generated directory index forbidden by Options directive, referer: binance.com
    [Sun Jul 10 12:19:20.424268 2022] [autoindex:error] [pid 1122754:tid 140315302057728] [client 193.142.146.138:56396] AH01276: Cannot serve directory /home/yqxeia19y71u/public_html/wp-admin/css/: No matching DirectoryIndex (index.php,index.shtml,index.html,index.htm,home.html,home.htm,index.php5,welcome.html,welcome.htm) found, and server-generated directory index forbidden by Options directive, referer: binance.com
    [Sun Jul 10 10:49:43.432016 2022] [autoindex:error] [pid 949361:tid 140315092260608] [client 79.124.8.3:51598] AH01276: Cannot serve directory /home/yqxeia19y71u/public_html/wp-admin/css/: No matching DirectoryIndex (index.php,index.shtml,index.html,index.htm,home.html,home.htm,index.php5,welcome.html,welcome.htm) found, and server-generated directory index forbidden by Options directive, referer: binance.com

    I hope this can help you direct me. I really appreciate your time, effort and patience.

    Héctor

    This seems to access log, we need php error logs. Please check for error logs not for the access logs.

    Thread Starter hectorops

    (@hectorops)

    I have checked the CPanel in GoDaddy and that is the only error log I found.

    Ok, You can open File Manager in the root(/public_html/) you might find the error_log file, you can open that file and check the error log.

    Thread Starter hectorops

    (@hectorops)

    I was able to access the error log and it is a very lengthy document. I don′t know if I can send you the file but I cut and pasted the entries prior and after the “PHP Fatal error”:

    [03-Jul-2022 12:31:54 UTC] WordPress database error Lost connection to MySQL server during query for query 
    			SELECT DISTINCT t.term_id, tr.object_id
    			FROM wp_terms AS t  INNER JOIN wp_term_taxonomy AS tt ON t.term_id = tt.term_id INNER JOIN wp_term_relationships AS tr ON tr.term_taxonomy_id = tt.term_taxonomy_id
    			WHERE tt.taxonomy IN ('category', 'post_tag', 'post_format') AND tr.object_id IN (17670, 17680, 17684, 17688, 17693)
    			ORDER BY t.name ASC
    			
    		 made by require('wp-blog-header.php'), require_once('wp-includes/template-loader.php'), include('/themes/twentyeleven/tag.php'), get_sidebar, locate_template, load_template, require_once('/themes/twentyeleven/sidebar.php'), dynamic_sidebar, call_user_func_array, WP_Widget->display_callback, WP_Widget_Recent_Posts->widget, WP_Query->__construct, WP_Query->query, WP_Query->get_posts, _prime_post_caches, update_post_caches, update_object_term_cache, wp_get_object_terms, get_terms, WP_Term_Query->query, WP_Term_Query->get_terms
    [06-Jul-2022 01:01:26 UTC] WordPress database error Lost connection to MySQL server during query for query SELECT option_value FROM wp_options WHERE option_name = 'jetpack_waf_mode' LIMIT 1 made by do_action_ref_array('wp_version_check'), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, wp_version_check, do_action('wp_maybe_auto_update'), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, wp_maybe_auto_update, WP_Automatic_Updater->run, WP_Automatic_Updater->update, Plugin_Upgrader->upgrade, WP_Upgrader->run, do_action('upgrader_process_complete'), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, Automattic\Jetpack\Waf\Waf_Runner::update_rules_if_changed, Automattic\Jetpack\Waf\Waf_Runner::define_mode, get_option
    [07-Jul-2022 01:00:59 UTC] WordPress database error Lost connection to MySQL server during query for query SELECT option_value FROM wp_options WHERE option_name = 'jetpack_waf_mode' LIMIT 1 made by do_action_ref_array('wp_version_check'), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, wp_version_check, do_action('wp_maybe_auto_update'), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, wp_maybe_auto_update, WP_Automatic_Updater->run, WP_Automatic_Updater->update, Plugin_Upgrader->upgrade, WP_Upgrader->run, do_action('upgrader_process_complete'), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, Automattic\Jetpack\Waf\Waf_Runner::update_rules_if_changed, Automattic\Jetpack\Waf\Waf_Runner::define_mode, get_option
    [07-Jul-2022 01:01:02 UTC] PHP Fatal error:  Cannot use isset() on the result of an expression (you can use "null !== expression" instead) in /home/yqxeia19y71u/public_html/wp-content/plugins/gutenberg/lib/compat/wordpress-6.1/class-wp-theme-json-6-1.php on line 190
    [07-Jul-2022 01:01:26 UTC] PHP Fatal error:  Cannot use isset() on the result of an expression (you can use "null !== expression" instead) in /home/yqxeia19y71u/public_html/wp-content/plugins/gutenberg/lib/compat/wordpress-6.1/class-wp-theme-json-6-1.php on line 190
    [07-Jul-2022 01:01:35 UTC] PHP Fatal error:  Cannot use isset() on the result of an expression (you can use "null !== expression" instead) in /home/yqxeia19y71u/public_html/wp-content/plugins/gutenberg/lib/compat/wordpress-6.1/class-wp-theme-json-6-1.php on line 190
    [07-Jul-2022 01:02:23 UTC] PHP Fatal error:  Cannot use isset() on the result of an expression (you can use "null !== expression" instead) in /home/yqxeia19y71u/public_html/wp-content/plugins/gutenberg/lib/compat/wordpress-6.1/class-wp-theme-json-6-1.php on line 190
    [07-Jul-2022 01:03:16 UTC] PHP Fatal error:  Cannot use isset() on the result of an expression (you can use "null !== expression" instead) in /home/yqxeia19y71u/public_html/wp-content/plugins/gutenberg/lib/compat/wordpress-6.1/class-wp-theme-json-6-1.php on line 190

    I don′t know if it is relevant, but the only event prior to the error was the automatic updating of the Gutemberg plugin.

    I have been navigating uncharted (for me) waters. I hope this sheds some light.

    Héctor

    Thread Starter hectorops

    (@hectorops)

    Maybe if I can somehow deactivate or remove the Gutemberg plugin without access to the webpage, it would solve the problem.

    Thread Starter hectorops

    (@hectorops)

    Dear Vijay: I tried deleting the Gutenberg and the problem was immediately resolved. The website is back online.

    I never could have done it without your knowledge, guidance and, above all, patience in dealing with a senior citizen with minimal technical knowledge. In the process, I have gained knowledge which I hope can help me in the future.

    Thank you again!
    Héctor

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘Message: There has been a critical error on this website’ is closed to new replies.