Search results

plop this in a .htaccess in the directory where you want to force https: rewriteEngine On rewriteCond %{SERVER_PORT} !443 rewriteRule ^(.*)$ https://www.example.com/securedir/$1 [R,L]

I believe the issue is that LSWS does not format the security message the same way the mod_security does. CSF is looking for a specific patter and not finding the LSWS lines. Frank

Your going to have to look at the mod_security entries in the LSWS log vs the Apache log and see if they are similar enough to get picked up. I'd have to look at how CSF scans the logs in more detail to know for sure. The exact value for MODSEC_LOG is going to depend on where you installed...

Hello vivek, I'm sorry, but I think you are missing my point. In our config Apache logs to /etc/httpd/logs/error_log. LSWS on the other hand logs errors to /opt/lsws/logs/error.log. Where your LSWS logs are is going to depend on where you installed LSWS and if you changed the default...

Thanks, that helped me track it down. Just a bad path to the extension and it was fixed up. Frank

Hello vivek, I'm guessing that mod_security is really working with LSWS. Take a look at the value of "MODSEC_LOG" in your csf.conf. I'm guessing that Apache and LSWS are not logging things to the same place, so CSF is not finding the mod_security (like) messages from LSWS. Frank

What version of LSWS are you using (free, paid, trial)? What is emailing you that things are being blocked by mod_security? Frank

Anyone have any luck with the 4 of these together with LSWS. We have Zend/Ioncube/eAccelerator working fine. If I try to add in the Suhosin extension php simply stops with 503's. Nothing in any error log (I checked). TIA, Frank

Brainlag, Don't think in terms of how many CPU's/cores you have (they are the same to LSWS as far as I know) think about how many you want LSWS to "use". If, for example, you are running a heavy PHP/MySQL application you may only want a 2-CPU license. That then "logically" leaves 1/2 your...

LSWS sets it's own directives for the access and error log. Just go to "Server" "Log" and you can change the location to the same location cPanel uses. Frank

Thnx. I just saw the announcement. I'll just give it a bit to hit the auto-download. A nice early xmas present :-)

This is also affecting PHP file downloads. We've reverted back to 3.3.1 until the release of 3.3.3. Frank

Thanks for the quick easy fix. We're back to auto-updates now :) Frank

Hello, I saw in the release post that 3.3.2 might not auto-download and I believe we're having that issue. I know that we can manually install, but the auto-installer is just so much nicer :) Is there any way we can manually download and then "trick" the web console installer to believe it...

What does the LSAPI_AVOID_FORK=1 do? Frank

That sounds very nice. Looking forward to a gui build (not that command line is very difficult). Frank

Hello, From memory you suggested downloading / installing the 3.3 release to fix some cPanel "quirks". Any idea when the 3.3 release will be "officially" released/documented and available via the LSWS control panel for install? Thanks, Frank

Assuming you followed the WIKI doc, it restarts because httpd.conf is updated. When httpd.conf is updated, LSWS will restart automatically. Frank

We still have Apache running. For now (at least) LSWS does not handle SSI so those all still have to be proxied back to Apache. I'm also not sure how adding a new domain will work if cPanel can't restart Apache. Frank

So far no major issues. Frank