Search results

  1. N

    [Resolved] Problem for per user php.ini

    Thanks for update. lsphp-5.4.17 should be ok as well. if still problem, please update here.
  2. N

    [Resolved] Problem for per user php.ini

    no idea ... if you're ok I can ssh to your server or give lsws admin console access(:7080) to take a quick look.
  3. N

    [Resolved] Problem for per user php.ini

    please show the last part of phpinfo.php -- PHP Variables
  4. N

    [Resolved] Problem for per user php.ini

    in the first screenshot, show "Server API: LiteSpeed" maybe you build lsphp with the php source code ? the lastest API should show "Server API: LiteSpeed V6.3" please download latest lsapi for php 6.3: https://www.litespeedtech.com/open-source/litespeed-sapi/download copy *.h and *.c to...
  5. N

    [Resolved] Problem for per user php.ini

    in cPanel, it should be /home/username/ it's really strange that in your phpinfo.php: Scan this dir for additional .ini files : /opt/lsws/admin can you give a screenshot about the phpinfo.php (from top to "Zend Extension" is ok)
  6. N

    [Resolved] Problem for per user php.ini

    I tested PHP_INI_SCAN_DIR=$VH_ROOT it's working as expected. what's your $VH_ROOT should be ? how do you know it's scanning /opt/lsws/admin/ ? by phpinfo() "Additional .ini files parsed" ?
  7. N

    [Resolved] Problem for per user php.ini

    please provide more information regarding this. how did you check ? $VH_HOST or $VH_ROOT ?
  8. N

    php not run :(

    you can verify and activate license yourself -- http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:license:activate_license cache need 2-CPU and above license. for set up steps, you can follow our wiki to do it yourself -- all steps are there, nothing hide...
  9. N

    php not run :(

    the general steps to switch from apache to litespeed: first, make it work under apache. now your website is not under apache: http://www.yourdomain.org/index.php Not Found The requested URL /index.php was not found on this server. Apache/2.2.3 (CentOS) Server at www.yourdomain.org Port 80...
  10. N

    Rate limiting and Google bot

    yes, just information. please try latest 4.2.4, this info may not exist any more .. but I'm not 100% sure. if it still exist, please inform us here.
  11. N

    overwrite authentication

    you can try http://httpd.apache.org/docs/2.2/howto/auth.html#satisfy looks apache 2.4 not use "satisfy" but compatible with it
  12. N

    Anyone else have to manually check for license this am?

    for license issue, please open ticket in WHMCS, our sales can trace your license issue individually and find out the root cause. maybe a temporary bug, or only a special case etc.
  13. N

    Rate limiting and Google bot

    this is just information, not error. in php suExec mode, each lsphp process will be killed if it's idle for some time. this is by design. since on a shared hosting environment, there may be thousand of accounts, thousands of websites powered by php, each lsphp process has its own uid/gid...
  14. N

    APC uptime?

    have you enabled php suExec ? this is a known issue for apc/xcache with php suExec. so in shared hosting environment which php suExec is enabled, only recommend eAccelerator, since it stores opcache on disk, not in memory. There are some detail discussion regarding this issue on this...
  15. N

    [Resolved] Cannot enable gzip compression.

    while I still can't see Content-Encoding:gzip response header for js/css, per your feedback, I'll mark this thread as [solved]. maybe you disable the gzip purposely.
  16. N

    [Resolved] Cannot enable gzip compression.

    yes, by default, css/js etc is gzip'd. and no need zlib.output_compression = On there must be a setting somewhere which override the default setting.
  17. N

    [Resolved] Cannot enable gzip compression.

    may not need. can you post the setting in your lsws admin console ->Server ->Tuning ->GZIP Compression or PM your admin console's access so I can take a quick check.
  18. N

    PHP not reading php.ini?

    sounds not possible. in particular, which parameter you tried to change but no effect? it's possible it's overridden by php_value php_flag in .htaccess
  19. N

    overwrite authentication

    while not do testing yet, I don't think password protected directory will be conflict with upload. for example, you can password protect a whole wordpress site, but you can upload file/publish new post/access the site just like a normal wordpress site, except it need input a password when you...
  20. N

    is there any way to limit litespeed use by domain

    you have to manually do it, as long as apache and litespeed listener not conflict, you can run litespeed and apache or nginx at the same time. listenter means IP:PORT.
Top