Hi,
For the cert part, if you can visit the site without issue on the browser, then it should be no problem.
You can also run this example to verify
openssl s_client -connect origin-domain-name:443 -servername CNAME
Read...
Sure, my test env is simple,
1. max_execution_time=120
2. RewriteRule and Rewrite log Level 9 are Enabled
3. Add the following script under the doc root with any name you want
<?php
set_time_limit(0);
$i = 0;
while($i < 1000) {
echo $i.'<br />';
if($i == 900){
echo...
@LiteCache
I just tried a long-run script to verify it, and "RewriteRule .* - [E=noabort:1,E=noconntimeout:1]" seems to be working in my case. Just want to share it with you, maybe you can also give it a try. :)
Maybe you have some long-run script, please try to use "[E=noabort:1,E=noconntimeout:1] " in your rewrite More https://docs.litespeedtech.com/lsws/cp/cpanel/long-run-script/
Apply www-data to the whole lsws folder is incorrect.
Once you changed the permission, better to reinstall OLS in order to apply the right permission to each folder.
apt-get -y install --reinstall openlitespeed
Let us know if it works.
Hi,
It looks good to me. Maybe you can join golitespeed community on slack(https://litespeedtech.com/slack) and message me @Eric from there for further check?
Hi
You might want to add all domains to the listener > virtual host mappings, and the Virtual hosts> General > Domain Aliases.
Let us know if it works.
I assume you want to use the app server from the OLS context, then please check https://docs.litespeedtech.com/cloud/images/nodejs/#how-do-i-use-an-express-app-on-this-image, let us know if it works.
Hi,
I think the client/device will choose to use strong cipher by default, and we can still serve the device which only supports weak cipher. If you want to get rid of the 128, please specify the cipher you need.