Google Cloud does not place any restrictions on traffic sent to external destination IP addresses using destination TCP ports 587 or 465. So no need to change the firewall. But you might want to set up the wp-smtp + port 587 on your own. :)
Saw a similar ticket/issue from other places, reply here too,
Our header x-litespeed-cache is not included in the health tools check for http response header, that's why it complains. If you check the site from https://check.lscache.io/, it should shows LiteSpeed cache is a hit.
Also, I did a quick test.
Launch the server and apply Let's Encrypt, SSL report = B
Then I went to web admin > Listener > SSL > SSL protocol, and only enable TLS v1.2 and TLS v1.3, and the score turns to A immediately. No need to bother OCSP and ECC cert.
2. Sure you can delete it, won't cause any issues.
3. I didn't compare the score with ecc before. To answer your question, no need to delete the existing certificate, since you will need to manually apply the new ecc cert to the web server. No harm to keep both cronjobs.
4. No alert, I...
hi, let me help to answer all the questions.
1. Those are still secure, it just not using a valid SSL certificate so your browser will show the warning. You can also assign a valid certificate to the web admin > admin > listener if needed.
2. That is not for cloud images. For the image, the...
I just installed lsphp81-dev on a Ubuntu system, it may install some php8.1 packages, but it won't cause any issues. Not sure what's the switch bothers you? If you want to specify lsphp81, can also run lsphp with full command /usr/local/lsws/lsphp81/bin/php, or, set a soft link by pointing...