Recent content by fidojones

  1. fidojones

    SSL Fails at 1.4.36 and 1.4.35

    And finally 1.4.39 solved all, works fine again: V1.4.39 (Stable) 2018-9-21 Server Core [Update] Reverted default OpenSSL v1.1.1 back to the more stable v1.1.0i.
  2. fidojones

    SSL Fails at 1.4.36 and 1.4.35

    Well I compiled 1.4.36 with Boring SSL and now it works fine, without touching anything. ./configure --with-bssl=../boringssl --with-group=nogroup make make install If I compile with: ./configure --with-group=nogroup make make install The compilation scripts download openssl (1.1.1-pre8)...
  3. fidojones

    SSL Fails at 1.4.36 and 1.4.35

    Dear david I tested the ols1clk and it works FINE, but if you compiled it it doesn't. So I think the bug is when you compile it. Perhaps when you compile it from source and openlitespeed download openssl 1.1.1 beta library the problem it's there. I don't know what version of openssl library is...
  4. fidojones

    SSL Fails at 1.4.36 and 1.4.35

    Dear David I attached a simple config in previous post if you want to check it. And no, I don't have any ciphers defined. This morning I did a clean installation to test if some config were wrong. And with the default config it fails with the same result. In the last two versions 1.4.35 and...
  5. fidojones

    SSL Fails at 1.4.36 and 1.4.35

    Mi openlitespeed is compiled, and yes if you see my config files, I had the same config as you. I have three servers working now with openlitespeed 1.4.34 version and they are working perfect. For example https://www.neeo.es if working with SSL perfect with 1.4.34. If I upgrade to 1.4.35 or...
  6. fidojones

    SSL Fails at 1.4.36 and 1.4.35

    I installed a new test server today, debian 9 stretch clean. I installed openlitespeed 1.4.36 clean. Configure a simple virtualhost without php. I added a simple letsencrypt SSL and same result you could call here https://test.fidojones.com. I attached my configuration.
  7. fidojones

    SSL Fails at 1.4.36 and 1.4.35

    I'm using version by version all 1.4 releases and in last two versions 1.4.36 and 1.4.35 and obtaining this error: With CURL or W3m linux command line browsers: * TCP_NODELAY set * Connected to panel.fidojones.com (163.172.140.19) port 443 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 *...
  8. fidojones

    Gzip not working last version OLS 1.4.27

    Yes it works fine in 1.4.28. I upgrade it some days ago and the problem disappear.
  9. fidojones

    Gzip not working last version OLS 1.4.27

    Here is a test with a phpinfo: The gzip compression is enabled in general settings and in virtualhost: enableGzip 1 https://checkgzipcompression.com/?url=http://www.baifox.org/testinfo.php By the way if for example I activate the Litespeed Cache plugin in wordpress and LSCACHE...
  10. fidojones

    Gzip not working last version OLS 1.4.27

    Ok, but : Enable Dynamic Compression Yes Why only static files are compressed, why dynamic content it's not compressed?
  11. fidojones

    Gzip not working last version OLS 1.4.27

    Gzip compression activate en general settings Compression activated in virtual host Testing gzip compression it's not enabled.... https://checkgzipcompression.com/?url=http%3A%2F%2Fwww.neeo.es%2F
  12. fidojones

    How to run php in user level?

    Yeah tested it works fine now, really thanks :D
  13. fidojones

    How to run php in user level?

    Dear kevin: I sent you some data to test the problem by conversation.
  14. fidojones

    How to run php in user level?

    I detected that doesn't work if you add de suexec user in the lsphp at server level (in litespeed standard mode it works). I you defined the suexec user in a external app at vhost level. But should work as litespeed standard, I supposed....
  15. fidojones

    How to run php in user level?

    Hi lsfoo I have the same problem. I installed opelitespeed 1.4.21 in debian and suexec doesn't work. I installed litespeed standard, and I configure the virtual host with the same configuration, and works perfect. I don't see any error in debug.log
Top