[Help] Failed to fetch URL to validate. cURL error 35: error:1408F10B:SSL routin

There appears to be a cURL configuration problem on your server.

What do you see if you access Site Health in the WordPress admin? Does it report any similar problems?

Hello, nothing to report on the dashboard side. Everything seems to be normal.

Do you have access to WP-CLI?

Can you run wp shell and then enter var_dump(wp_remote_get(home_url('/', 'https')))?

Otherwise, can you add this code you a template to see what it outputs?

If adding this to a template beware of causing a situation where infinite recursion results.

So this code would prevent that from being a possibility:

if ( ! isset( $_GET['curlcheck'] ) {
    var_dump( wp_remote_get( home_url('/?curlcheck=1', 'https') ) );
}

The wp shell command comes with followinf errors.

dan@mail:/var/www/la-gazette-climontaine.info$ wp shell
PHP Warning:  ftp_nlist() expects parameter 1 to be resource, null given in /var/www/la-gazette-climontaine.info/wp-admin/includes/class-wp-filesystem-ftpext.php on line 402
Warning: ftp_nlist() expects parameter 1 to be resource, null given in /var/www/la-gazette-climontaine.info/wp-admin/includes/class-wp-filesystem-ftpext.php on line 402
PHP Warning:  ftp_pwd() expects parameter 1 to be resource, null given in /var/www/la-gazette-climontaine.info/wp-admin/includes/class-wp-filesystem-ftpext.php on line 226
Warning: ftp_pwd() expects parameter 1 to be resource, null given in /var/www/la-gazette-climontaine.info/wp-admin/includes/class-wp-filesystem-ftpext.php on line 226
PHP Warning:  ftp_pwd() expects parameter 1 to be resource, null given in /var/www/la-gazette-climontaine.info/wp-admin/includes/class-wp-filesystem-ftpext.php on line 226
Warning: ftp_pwd() expects parameter 1 to be resource, null given in /var/www/la-gazette-climontaine.info/wp-admin/includes/class-wp-filesystem-ftpext.php on line 226
PHP Warning:  ftp_pwd() expects parameter 1 to be resource, null given in /var/www/la-gazette-climontaine.info/wp-admin/includes/class-wp-filesystem-ftpext.php on line 226
Warning: ftp_pwd() expects parameter 1 to be resource, null given in /var/www/la-gazette-climontaine.info/wp-admin/includes/class-wp-filesystem-ftpext.php on line 226
PHP Warning:  ftp_nlist() expects parameter 1 to be resource, null given in /var/www/la-gazette-climontaine.info/wp-admin/includes/class-wp-filesystem-ftpext.php on line 402
Warning: ftp_nlist() expects parameter 1 to be resource, null given in /var/www/la-gazette-climontaine.info/wp-admin/includes/class-wp-filesystem-ftpext.php on line 402
PHP Warning:  ftp_pwd() expects parameter 1 to be resource, null given in /var/www/la-gazette-climontaine.info/wp-admin/includes/class-wp-filesystem-ftpext.php on line 226
Warning: ftp_pwd() expects parameter 1 to be resource, null given in /var/www/la-gazette-climontaine.info/wp-admin/includes/class-wp-filesystem-ftpext.php on line 226
PHP Warning:  ftp_pwd() expects parameter 1 to be resource, null given in /var/www/la-gazette-climontaine.info/wp-admin/includes/class-wp-filesystem-ftpext.php on line 226
Warning: ftp_pwd() expects parameter 1 to be resource, null given in /var/www/la-gazette-climontaine.info/wp-admin/includes/class-wp-filesystem-ftpext.php on line 226
PHP Warning:  ftp_pwd() expects parameter 1 to be resource, null given in /var/www/la-gazette-climontaine.info/wp-admin/includes/class-wp-filesystem-ftpext.php on line 681
Warning: ftp_pwd() expects parameter 1 to be resource, null given in /var/www/la-gazette-climontaine.info/wp-admin/includes/class-wp-filesystem-ftpext.php on line 681
PHP Warning:  ftp_pwd() expects parameter 1 to be resource, null given in /var/www/la-gazette-climontaine.info/wp-admin/includes/class-wp-filesystem-ftpext.php on line 226
Warning: ftp_pwd() expects parameter 1 to be resource, null given in /var/www/la-gazette-climontaine.info/wp-admin/includes/class-wp-filesystem-ftpext.php on line 226
PHP Warning:  ftp_pwd() expects parameter 1 to be resource, null given in /var/www/la-gazette-climontaine.info/wp-admin/includes/class-wp-filesystem-ftpext.php on line 226
Warning: ftp_pwd() expects parameter 1 to be resource, null given in /var/www/la-gazette-climontaine.info/wp-admin/includes/class-wp-filesystem-ftpext.php on line 226
PHP Warning:  ftp_mkdir() expects parameter 1 to be resource, null given in /var/www/la-gazette-climontaine.info/wp-admin/includes/class-wp-filesystem-ftpext.php on line 539
Warning: ftp_mkdir() expects parameter 1 to be resource, null given in /var/www/la-gazette-climontaine.info/wp-admin/includes/class-wp-filesystem-ftpext.php on line 539
PHP Fatal error:  Cannot redeclare postbox_classes() (previously declared in /var/www/la-gazette-climontaine.info/wp-content/plugins/noo-menu/noo-menu-demo-control.php:7) in /var/www/la-gazette-climontaine.info/wp-admin/includes/post.php on line 1312
Fatal error: Cannot redeclare postbox_classes() (previously declared in /var/www/la-gazette-climontaine.info/wp-content/plugins/noo-menu/noo-menu-demo-control.php:7) in /var/www/la-gazette-climontaine.info/wp-admin/includes/post.php on line 1312
Error: Une erreur critique est survenue sur votre site.En apprendre plus sur le débogage de WordPress. Une erreur critique est survenue sur votre site.

I guess there in an serious issue. But the site is working properly.

• This reply was modified 4 years, 7 months ago by Yui. Reason: please use CODE button for proper formatting

There does appear to be a misconfiguration of WordPress which is causing various problems, including the inability for AMP to make validation requests. I don’t know what advice to give you, other than perhaps to contact your host.

Thanks for this feedback. Unfortunately I am my own host and webmaster. So far my servers are working fine. There I will have to investigate to find out what is malfunctioning. I will come back to you after resolution.

Hello, I think the problem is solved. The noo-menu plugin was the source of the problem. It is a plugin that is no longer maintained. I replaced it with megamenu which is still maintained. Can you check if the problem is also fixed for you. Thanks again for detecting and reporting this anomaly in WP to me.

You’ll have to check if the problem is fixed for you, as no URLs were shared that showed any problem.

Hello, I would like to respond whith the process I took to find the cause. First you have to check the compatibility of the plugins with the version of WP. If plugins are no longer followed and adapted, they must be deactivated. In my case I found by this method the plugin causing the error.

Hello, this forum allows mutual assistance. Therefore we will continue to exchange through the forum. Have you ever tried to disable all the plugins and check if the problem persists?