Search results

TQ. Any advantage of doing this for production server? or only for the purpose of benchmark?

Is there any guides on how to enable two processes for port 80 to fully utilize the 2-CPU license?

TQ, the latest build of 5.1.3 fix the issue.

I send you a private message containing the log file.

Yes, I try to get rewrite log but sure what I did correct as I don't see "rewrite.log" file in /usr/local/apache/logs/ <FilesMatch "wp-login.php|xmlrpc.php"> RewriteEngine on RewriteLog "/usr/local/apache/logs/rewrite.log" RewriteCond %{HTTP:CF-IPCOUNTRY} !^(AU)$ RewriteRule ^ - [F,L] </FilesMatch>

5.1.3 still give the same redirect loop. 5.0.13 is giving the correct 403 forbidden.

then why v5.0.12 give the correct 403 forbidden error?

I found out that redirect loop issue start with v5.1 and above. All version 5.0+ return the correct 403 forbidden error.

Yes file matching works but the result is the same redirect loop instead of 403 on the specified file. Other files is having a normal access.

I upgraded to 5.1.2 build 5 but the problem still there.

Hi, Now, I'm using Cloudflare CF-IPCOUNTRY to do this. The code below works very well to block access wp-login.php except in my country. However after I upgrade to the latest version 5.1.2, it cause redirect loop instead of 403 forbidden error. Any idea what is wrong? <FilesMatch...

TQ mistwang. Find the error is in .htaccess file in public_html folder & fix it. I put in "//" for comments. It works in LiteSpeed but not in Apache.

Hi, I'm using LiteSpeed with cPanel. Recently, I switch back to Apache but found out the the server throw out 500 server error for all sites. If I switch back to LiteSpeed everything back to normal. Try a few times same things happen. For your info, switching went succesfully, no error. What...

I can't get litespeed to work after installing EasyApache 4. I also unable to compile PHP to match. Is this general issue or just my installation?

Yes, I could arrange for that. I will PM you shortly.

I already have "ALL" in the allowed list. I still add Railgun server IP in the allowed list with trailing "T" just to try. Unfortunately the problem persist.

4.2 never have any problem. The problem is with 5.0. I did not add trailing "T" in the IP. I'll try again & report back. It did not block Cloudflare IP but only Railgun server IP which operated by my hosting provider. LiteSpeed did not block Railgun server IP that frequently maybe only 1-2...

For your info the error 502 shown by Cloudflare not LiteSpeed.

Yes, if I turn Railgun off, the problem gone. Railgun server is run by my hosting provider. Right now I can't check any error as I already switch back to 4.2.24. I did add Railgun server IP in LiteSpeed "Allowed List" but the problem persist. Sometimes, I also can see Railgun server IP been...

Yes, I did that & the problem persist. It only occur with LiteSpeed v5.0+. LiteSpeed v4.2+ perfectly fine.