Search results

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.

1. Use the same should be fine. 2. Can skip this and see if the web admin page loads fine or not

Looks fine to me, and there should has no permission issue if you created the file by the web admin. I just tried $SERVER_ROOT/conf/vhosts/$VH_NAME/htpasswd and it works for me, could you try to test it without the group?

Could you share some of the 500/503 error logs? Maybe it's due to you are using GET HTTP/1.1 whereas PUSH is a feature for HTTP/2?

Quic Log also can be found in the /usr/local/lsws/logs/error.log, you can change the log level to display more if needed.

Seems only port 80 and 443 can go through, maybe you have firewall setup on the server or network level.

It's not a problem, the web admin will use an invalid cert by default in order to use HTTPS by default. If you want to set a valid cert for the web admin, check https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:config:admin-ssl which is similar to OpenLiteSpeed.

Yes, the secure is needed. No problem, glad to know it works now.

May I know where the pass file is located, maybe it's due to the permission so you can not pass it at all.

If this is on a shared server, it's might be LSWS instead of OLS. https://www.litespeedtech.com/support/forum/ I'm not sure about your setup steps, maybe you can contact the hosting manager for help?