Search results

please refer http://www.litespeedtech.com/support/forum/threads/solved-404-not-found-on-all-domain.9918/#post-82332 it should cover your case,

>there is a /bak_core directory with a core file. Is this it? yes. please run #gdb /usr/local/lsws/bin/lshttpd /tmp/lshttpd/bak_core/core.xxxx ... >bt to get the stack trace.

it's lsphp5, just borrow the name "suphp" however, there are 3 "suphp" or suEXEC PHP, please refer http://www.litespeedtech.com/products/litespeed-sapi/php for more detail.

can you tell why you need mod_spelling feature ? it's a bad choice in performance point of view. if you do need it, I think modify the index.php can archive it.

I did tests on a lsws native virtual host: Options +Indexes in .htaccess works. your requests actually need support Options +Indexes in .htaccess, not relating to mod_speling which lsws don't support I've not tested on a virtual host from apache's httpd.conf. but in general, if AllowOverride...

please add a trailing "T" to 1.2,3,4, i.e., "ALL, 1.2.3.4T"

>Even with the IP address of Litespeed added to the ACL in Litespeed's configuration how did you do it ? let's double check if this is correctly done before going forward.

have you changed the default settings(or what's the current settings)? lsws web admin -> Server -> Security -> File Access

>is it me or having this ini physical file makes things a little slower? there are many factors which cause php slow. php.ini-production should be faster than php.ini-development and you can fine-tune php.ini to make it faster.

any message in error log?

>but the compiled version of php 5.6 I have in LSWS shows that php.ini is at /usr/local/lsws/lsphp5/lib but there is not an actual php.ini file. there are 2 php.ini under root of php source: php.ini-development php.ini-production copy one of them as /usr/local/lsws/lsphp5/lib/php.ini, then edit...

have you upgrade to lastest lslb 1.8 ? please refer the release log: http://www.litespeedtech.com/products/litespeed-load-balancer/release-log

if you use WHM/cPanel, you can put above directives in a global include file, so every account have them as part of rewrite rules.

lslb should not be the bottleneck, the network card(NIC) is. you can add another 1G bps NIC card on the server and bond 2 1Gbps NIC to a 2G bps NIC. or replace it a 10G bps card.

PHP suEXEC: Yes should be safer. "Run under home directory" is there mainly because of directadmin. if you can get update from directadmin developer, will be best. WHM/cPanel doesn't seem need this option.

this doesn't look much helpful ... please try lsws's debug logging: 1.lsws web admin->Actions->Toggle Debug Logging 2.watch error.log 3, reproduce the 403 error 4."lsws web admin->Actions->Toggle Debug Logging " again check error.log, see if any 403 related logs

you can enable wordpress debug http://codex.wordpress.org/Debugging_in_WordPress and check /wp-content/debug.log if any log in it when 403 error happens

any error message in error log for the 403 forbidden ? if you've enabled mod_security, can disable it temporarily to see if still 403 ?

not sure if it's a wordpress(php) issue you can try switch to apache to see if same issue. which URL cause 403 ? your-domain-com/wp-signup.php or other URLs ?

you can check mysql slow query log, see if any query takes very long time. also can run #mysqladmin processlist to see if many current query running old forum php code may be easier to get attack of sql injection.