Search results

Not so sure since it only shows facebook-for-wooconerce plugin has such an issue on your site. Do you have any firewall or security plugins? Maybe you can try to turn those off temporarily and see how it goes.

Maybe you can try to ask on the WordPress forum, https://wordpress.org/support/plugin/litespeed-cache/

Cache has nothing to do with the SSH, have you tried to connect via the platform panel? Or reboot the server? Did you change any firewall?

No problem :)

please run as root permission, e.g. sudo -s

It shows active from the page source. To verify from the browser, you can open the developer tool, tick the Disable cache, and set No throttling to Fast 3G, and you should see it works.

Hi, Run the following command should work. apt-get install lsphp74-ioncube -y killall lsphp Please do not give 777 to the document root folder, not secure.

You need to run, e.g. "certbot certonly --webroot -w /var/www/html/ -d example.com -d www.example.com" instead of "certbot certonly --webroot -w /var/www/html/ -d example.com" So it will apply to both the root domain and the www domain.

By using the OpenLiteSpeed-WordPress image, you don't really need to change those configs. I'm not sure your status now, are you still using ols1clk? or using cloud images now? Which OS did you use for the ols1clk before?

okok glad to know it works now.

Hi, May I know which OS you installed the ols1clk? Have you tried openlitespeed wprdoress image on GCP? https://console.cloud.google.com/marketplace/product/gc-image-pub/openlitespeed-wordpress should be much faster for you to launch the solution.

Please share your Environment Report: Navigate to **LiteSpeed Cache > Toolbox > Report**, press the **Send to LiteSpeed** button, and let us know what it says under "Report Number." We'll be able to access the report from here and get some information about your configuration that might be helpful.

No problem

Hi, Only mod_pagespeed has a problem. Since it is optional and openlitespeed binary is ready, maybe you can give it a try.

Hi, The method you built boringssl is incorrect, also the cmake failed due to cache. Please try to remove third-party/src/boringssl/ completely, and try build_bssl.sh again.

Not sure what did you mean, /wp-login.php and /wp-login.php?123 should all be restricted.

May I know which CMS you are using?

Not sure. But you could access to the "/usr/local/lsws/conf/httpd_config.conf" from SSH console, edit it with vi and scroll down to the listener section like follows, and remove the '*' from the 3rd one. listener wordpress { address *:80 Hope it helps.

Thanks for the information, Please run the following command and make sure it is completed successfully ../third-parity/script/build_bssl.sh

Hi, Please remove the "third-party" directory parallel to openlitespeed source directory. Then run the build.sh again, make sure "third-party" libraries have been built successfully.