Asif

Hey @optimizingmatters
Cool. Thanks for the update.
And, appreciate the quick response here.

Cheers
Asif

Hey @optimizingmatters
Yes, this version works fine. Thanks.
Any idea when will the fix be officially released?

Cheers
Asif

Thanks @arnaudbroes.

Hi,

We are also facing the same issue after the upgrade.
AIOSEO version: 4.1.6.2
WordPress version: 5.8.3 (multisite)

The message appears for Author and Editor roles. It doesn’t show for admins.

Any help would be appreciated.

Thanks
Asif

• This reply was modified 3 years, 2 months ago by Asif.

Sounds good, @niklasinpsyde

Cheers,
Asif

Hey @niklasinpsyde
Thanks for the response.
Is there any tentative timeline for BackWPup 4.0?

Regards
Asif

Apologies. I have posted it in the wrong forum. Not sure whether I can delete/revoke this.

Hey @arnaudbroes
Sure, thanks for the response.

That’s all @99robotsteam.
Appreciate the support.

Thanks
Asif

Hey @99robotsteam
A quick update here. The issues got fixed after upgrading to the latest release (1.1.14) of HFCM.

Thanks
Asif

• This reply was modified 3 years, 5 months ago by Asif.

Hey @99robotsteam – Have you reproduced the issue?

Thanks
Asif

Hi,
Thanks for getting back.

To isolate the issue fully, I have set up another site in the multisite mode that has only two plugins, W3 Total cache version 2.1.8 and HFCM version 1.1.13.

The network has two sites. W3 total is active at the network level and HFCM is active for one of the sites. HFCM is not active at the network level. The site which has HFCM throws errors. I have enabled debug mode, so the error messages are displayed on the page. Here are site URLs, the first site throws errors but the 2nd one works fine.

https://wordpressmu-533274-2195421.cloudwaysapps.com/
https://wordpressmu-533274-2195421.cloudwaysapps.com/site2/

The log file doesn’t have any other errors but let me if you still want the log file.

Note, I wasn’t able to reproduce the issue without the multisite setup.

Thanks
Asif

Hey,

Following up here with more details specific to WordPress.
The WordPress comes with a default CA bundle – /wp-includes/certificates/ca-bundle.crt
This bundle contains the expired DST Root CA X3 certificate – https://github.com/WordPress/WordPress/blob/b3c6ad3a6ba4a83e2ed342b5385b7c8faba8c044/wp-includes/certificates/ca-bundle.crt#L739

Looks like this certificate is now causing the issue.

As cURL in php works with PHP’s cURL extension. One solution is to set the value for curl.cainfo option in php.ini. The value should be set to a valid file containing CA certificates. Here is an example for Ubuntu.
curl.cainfo = /etc/ssl/certs/ca-certificates.crt

If you are using PHP FPM, and want to set the value in the fpm config:
php_admin_value[curl.cainfo] = /etc/ssl/certs/ca-certificates.crt

Hope this helps.

Hey,
This might be related to expiration of Let’s Encrypt root certificate on 30th Sep. Please refer here – https://serverfault.com/questions/1079199/client-on-debian-9-erroneously-reports-expired-certificate-for-letsencrypt-issue

• DST Root CA X3 root certificate expired on Sep 30 14:01:15 2021 GMT. It was used as one of certification paths for Let’s Encrypt certificates Older cURL version has a bug that will cause expired root to fail connection instead of trying other roots in local ca store.

  As of 30 september 2021 ca store for curl (https://curl.se/docs/caextract.html) still contains expired DST Root CA X3 root certificate so updating it won’t fix problem. You can either update your cURL (which might be quite challenging in some situations) or edit local ca store (f.e. /etc/pki/tls/certs/ca-bundle.crt) and manually remove certificate after line “DST Root CA X3

• This reply was modified 3 years, 5 months ago by Asif.
• This reply was modified 3 years, 5 months ago by Asif.
• This reply was modified 3 years, 5 months ago by t-p.

Hey Marko,
An update here. We found that it’s conflicting with the Header and Footer Manager plugin. The DB cache works fine if we disable this plugin. I have been in contact with W3 Total premium support. They have advised me to reach out to Header and Footer Manager plugin support.

Thanks for the support here.