Check it at https://ssllabs.com/ssltest and it will tell you what’s wrong with the chain. Source: about 1 year ago

Didn’t know that one. I generally use ssl server test at https://ssllabs.com/ssltest. Source: over 1 year ago

As far as the SSL error, your browser does not consider the certificate to be valid. It looks like you’re trying to use Let’s Encrypt (based on your .well-known/acme-challenge location. You’ll also need to provide the intermediary certificate, but there also may be something else wrong (e.g., are you using the staging CA and not the production CA when brokering the certificate?). I can’t tell what’s wrong without... Source: over 1 year ago

If you want to prove it, check your site with https://ssllabs.com/ssltest. It checks web servers for safe TLS configurations, including whether or not you have TLS compression enabled. Source: about 2 years ago

Try running SSL test on server. https://ssllabs.com/ssltest/ It reports incomplete certificate. Did you add whole chain on "ssl_certificate" file? Root cert is not needed but intermediate should be in there with server certificate. Source: about 2 years ago

I also like WP Rocket's database cleaning tool: https://wp-rocket.me/. Source: about 1 year ago

This will have a serious impact based on that kind of database. A good caching plug-in like WP Rocket should help with the overheads and speed things up. If you have server side caching like memcached or lighspeed make sure you are utilising it. Source: about 1 year ago

Purchase a license from the WP Rocket website (https://wp-rocket.me/). Source: about 1 year ago

Sounds like your colleague bought a nulled/"GPL free" copy of WP Rocket - probably not purchased from https://wp-rocket.me/. Source: over 1 year ago

One of the most beloved WordPress caching plugins is WP Rocket. They’ve managed to take something complex and make it extremely easy, yet still powerful and configurable. They have also made it easy to integrate with a CDN in just a few clicks. - Source: dev.to / over 1 year ago