Search results

  1. lsfoo

    Never mind, it was the firewall!

    I approved it so that hopefully you won't need approval next time :)
  2. lsfoo

    OpenLiteSpeed v1.5.4 Now Available

    Announcing: OpenLiteSpeed v1.5.4 In this release: added support for HTTP response code 413, updated install.sh script, bug fixes, and more! RELEASE LOG: [Improvement] Added support for HTTP response code 413: response is larger than defined max dynamic response length. [Improvement] Updated...
  3. lsfoo

    recaptcha dont work

    Yes, we will get to it. I am not sure when, but it should be in the next version.
  4. lsfoo

    recaptcha dont work

    My apologies, I think I see the problem - it looks like the code where reCAPTCHA rewrites are processed is missing. I will get this looked at, this is definitely a bug. Apologies for the inconvenience - thank you for the report.
  5. lsfoo

    recaptcha dont work

    Thank you. It looks like there may be something wrong with handling the RewriteCond result. If you remove the condition and just keep the RewriteRule, will it redirect to reCAPTCHA?
  6. lsfoo

    recaptcha dont work

    Apologies for the late reply. To clarify, these are two ways to toggle reCAPTCHA. The regConnLimit and sslConnLimit check the number of concurrent visitors to each VHost on a single worker process. Upon crossing the threshold, new visitors should redirect to reCAPTCHA. The rewrite rule is a...
  7. lsfoo

    recaptcha dont work

    Could you set debug log to DEBUG and level to 10/high and check the debug log for anything related to reCAPTCHA?
  8. lsfoo

    recaptcha dont work

    It is listed in the second snippet you pasted above, under google.com.
  9. lsfoo

    recaptcha dont work

    Ultrasparc, If you set the reg conn limit and ssl conn limit both to 1, then restart the server, will it work? Kevin
  10. lsfoo

    OpenLiteSpeed v1.4.36 Now Available

    Hallo! OpenLiteSpeed v1.4.36 was released yesterday. In this release: Various updates and a fix for an HTTP/2 server push bug. Full release log: Server Core [Update] Updated WebAdmin PHP to a newer version. [Update] Updated SSL to enable ECDHE with X25519 curve. [Update] Updated...
  11. lsfoo

    OpenLiteSpeed 1.5.0 RC2 Now Available!

    Greetings! OpenLiteSpeed v1.5.0 RC2 was released today. This is our first announced release candidate of version 1.5. There are significant changes to the server core, so please be aware that there may be some strange behavior when trying out this version. Highlights of 1.5 include: Module...
  12. lsfoo

    php-xdebug

    Nice work! Looks good!
  13. lsfoo

    Terminated with signal 11 - OCSP Stapling

    Hi Michael, Glad to hear that it works! Let us know if you run into any more issues! Kevin
  14. lsfoo

    Terminated with signal 11 - OCSP Stapling

    Hi @Nichael Ibanes If you compiled from source, the bug is located in src/util/httpfetch.cpp ~ line 221: AdnsReq *pReq; Should become AdnsReq *pReq = NULL; Cheers, Kevin
  15. lsfoo

    phpmyadmin php7 openlitespeed?

    Hah, sometimes, it's the small things. Always good to know some silly steps that were forgotten, because it may help other users. Cheers, Kevin
  16. lsfoo

    No request delivery notification has been received from LSAPI application, possible dead lock.

    Hi @jivy26 Do you see anything in our stderr.log or in any php error logs? Kevin
  17. lsfoo

    phpmyadmin php7 openlitespeed?

    Glad to hear you were able to get it working! If you don't mind explaining, what issues did you encounter when trying to set this up? Cheers, Kevin
  18. lsfoo

    Curl issue on Debian and Ubuntu in 1Click install

    Hi @jivy26 Please check the vhost's configurations to make sure you're using the correct PHP version. The PHPInfo you sent is using PHP Version 7.0.22-1+xenial The output above is for lsphp71.
  19. lsfoo

    wont bind to port 80 or 443

    Glad to hear it! Let us know if you run into any more issues, we're always happy to help!
  20. lsfoo

    wont bind to port 80 or 443

    Hi @Rudi, First off, please make sure that nothing else is listening on the same port. in the server configurations, please check to see that the log level is set to DEBUG and HIGH. After that, try starting the server and check the log. There should be some log messages regarding attempting...
Top