Search results

  1. M

    How to enable TLS1.3

    OK thanks. I'm assuming it will just work "out of the box" or does something specific need to be configured?
  2. M

    How to enable TLS1.3

    Hi All, How do we enable TLS1.3 on a cPanel server running LSWS via the plugin? I've done some searching, but I'm not finding anything definitive. TIA :)
  3. M

    [solved] LiteSpeed cache stopped working after upgrading the LiteSpeed

    and here. Reported: Report number: BWOIPINI Report date: 05/24/2018 16:28:51
  4. M

    Unable to add licence.

    Thanks :)
  5. M

    Unable to add licence.

    Back up current license files under /usr/local/lsws/conf/ ... Trying to switch to a new production license ... ... Saved serial number "XXX" to /usr/local/lsws/conf/serial.no ... Serial number is available. ... Contacting licensing server for license key ... ... failed to...
  6. M

    Unknown rewrite rule flag while parsing: RewriteRule ipv6

    Yes, I'm suspecting it's a routing issue with Linode, as the default IPv6 address works, but the new range they have allocated aren't responding.
  7. M

    Unknown rewrite rule flag while parsing: RewriteRule ipv6

    Thanks, the errors are gone, but it's still not working. ping works, and the TCP listen is there, but the web server doesn't respond at all.
  8. M

    Unknown rewrite rule flag while parsing: RewriteRule ipv6

    I've just set up another server with Linode, and added an ipv6 range. When adding the ipv6 addresses to the domains, Litespeed is throwing the following error: APVH_176.58.122.54:443 [2a01:7e00:0000:0000:0000:0000:003f:4000]:443_unused.we] Unknown rewrite rule flag while parsing: RewriteRule .*...
  9. M

    PHP Fatal error: Unknown: Failed opening required

    I've set all my servers back to: from suEXEC Daemon until the update is pushed, as I wanted to get the updated PHP versions on them.
  10. M

    PHP Fatal error: Unknown: Failed opening required

    Same here, I'm sticking with PHP7 until the actual fix is released.
  11. M

    PHP Fatal error: Unknown: Failed opening required

    Check the yum.log file in /var/log and it will show you when it was updated.
  12. M

    PHP Fatal error: Unknown: Failed opening required

    I've had the exact same issue starting this morning. It's happening on PHP7.1 and PHP7.2 since the update: https://forums.cpanel.net/threads/ea-php71-7-1-16-causing-500-errors.625879/ I have another server with the exact same setup, which is still on PHP7.1.15 and PHP7.2.3 that doesn't have the...
  13. M

    cPanel 68.0.27 crashing / killing Litespeed

    Thanks, this isn't running on any of the servers which I've checked. Is this something that is supposed to start manually, or are we expected to start it after each reboot?
  14. M

    cPanel 68.0.27 crashing / killing Litespeed

    https://forums.cpanel.net/threads/litespeed-not-restarting-automatically-after-update.620475/ 5.2.2 doesn't crash during the cPanel update, so it's something specific to the 5.2.3 release.
  15. M

    cPanel 68.0.27 crashing / killing Litespeed

    This has just happened again as part of the update to 68.0.28.
  16. M

    cPanel 68.0.27 crashing / killing Litespeed

    Had alerts from one of my servers shortly after the auto update to 68.0.27 that all the sites were down, and had to manually restart Litespeed. Saw another of my servers still had to update to run, so ran it manually, and that also killed off Litespeed, and didn't restart it automatically...
  17. M

    /home/cpeasyapache/ls.src Directory

    I've recently switched to EA4, so is it safe to delete the old folders in the below directory? root@cpanel [/home/cpeasyapache/ls.src]# du -sh * 208M php-5.6.10 211M php-5.6.12 211M php-5.6.13 211M php-5.6.15 210M php-5.6.18 210M php-5.6.19 211M php-5.6.23 212M...
  18. M

    503 errors with EA4 and PHP7

    Getting intermittent 503 errors with Litespeed and PHP7 (via EA4) 2017-01-14 10:36:10.712 [DEBUG] [175.143.131.79:51435:HTTP2-33#APVH_74.86.200.109:443_physicsforums.com] Find .htaccess context with URI: [/], location: [/home/physicsf/public_html/] 2017-01-14 10:36:10.712 [DEBUG]...
  19. M

    Litespeed Stopped Working

    OK, so you can't allocate more than 1024mb to Opcache opcache.memory_consumption=1024 Although, I actually changed the setting about 4 days ago to increase to more than 1GB of memory
  20. M

    Litespeed Stopped Working

    I've disabled ZendOpcache, and I can get Litespeed to start now. # php -v PHP 5.6.12 (cli) (built: Aug 22 2015 19:39:48) Copyright (c) 1997-2015 The PHP Group Zend Engine v2.6.0, Copyright (c) 1998-2015 Zend Technologies
Top