Search results

Did you try to upgrade to LSWS, and then switch back to OLS? Better to submit a ticket to support@litespeedtech.com for this one.

Maybe you can submit a ticket to support@litespeedtech.com or join golitespeed community on Slack(https://litespeedtech.com/slack) and DM me @Eric from there, we can discuss more quickly about this weird issue.

I just tested it on my site, add the following rules to the document root's .htaccess file works for me. RewriteCond %{REQUEST_URI} ^/backend $ RewriteRule ^(.*)$ http://%{HTTP_HOST}/$1/ [R=301,L]

I just launched one but no such an issue since the defaultwebpage.cgi file is not found. May I know which virtual host you hit? And does the file exist on the server? Also, if Ipv6 returns the file, then IPv4 should do the same, does IPv4 returns the same file from your end?

HIHI The image comes with only the necessary port opened, you can add/delete the firewall rules easily after the server launch. If you check other WordPress solutions on the Google Cloud marketplace, they all apply similar basic rules for the web server only.

What if you remove the '/' static context, and add the rewrite rules to the .htaccess file? So the request to /backend/ will not be hit.

For the email part, you might want to check from others, e.g. https://www.wpbeginner.com/plugins/how-to-set-up-wp-mail-smtp-with-any-host-ultimate-guide/ or ask on https://wordpress.org/support/plugin/wp-mail-smtp/.

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. :)

Agree, if the load increased when enabling the plugin, please submit the issue to bug@litespeedtech.com so our dev team can help to take a look.

Hi @dens, for this shopping site, I'd recommend you to enable LSCache (https://docs.litespeedtech.com/lscache/lscwp/) to reduce the PHP and DB load.

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.

It works for me, see curl -I https://api.vitrimix.com.br/ HTTP/2 200 x-powered-by: Express access-control-allow-origin: * content-type: application/json; charset=utf-8 etag: W/"f-V8aY9BKXDVLrPXkVFrx47mMSg74" date: Wed, 30 Nov 2022 01:48:03 GMT server: LiteSpeed alt-svc: h3=":443"; ma=2592000...

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.

May I know the site URL?

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...

Globally. And the virtual host level can overwrite it.

Fixed, thanks for the report.

Thanks for the report, will forward it to the team.

I guess you did not set up a listener, or map the virtual host?

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...