Search results

The 'hit' means served with public cache and 'hit,private' means served with private cache.

Yes. Please paste the log around this one, actually, all logs about module cache should help.

Please change the errorlog level to DEBUG High and reproduce this error. The you will get more logs which can say the reason. Thanks. David

Yes. This is a bug and I have fixed it. So did you build with the source code or you just use the RPM package? Thanks. David

You can download the latest code and exact to new DIR to build, just like, ./configure .......; make Then you can stop your server and copy the output file "src/openlitespeed" to "/usr/local/lsws/bin/", you may want to make a backup before you overwrite the binary. And now you can start the...

Thank you for your feedback. I have a Debian 9 platform to test and did some test, I will re-test on it to verify there is a bug or not. And I am glad that you can build BoringSSL and use it in openlitespeed, this way is good.

Sorry, I did not see what your platform is. Can you tell me that and I will try to do test on the same platform?

The source code compiling and the RPM actually are the same. They both are using openssl-1.1.1. Actually I always use openssl 1.1.1 for testing on different platforms and never saw such issue. I will keep checking if can find something wrong. Please try to use RPM package or try to build...

The above way may not work if you are porting to a different OS. If so, you may just ./configure & make to create a new binary and overwrite the old one.

Yes, please check the new release, and it should be fixed.

BTW, if you want to do the re-installation with ols1clk, please rename your previous installation directory. Such as ./>mv /use/local/lsws /use/local/lsws_bak Because ols1clk will always install to this directory.

If it is all right, can you do a simple installation with ols1clk? https://raw.githubusercontent.com/litespeedtech/ols1clk/master/ols1clk.sh you just run ./ols1clk Then you can test if you site SSL is good or not. The url is https://your_ip/

Do you have any ciphers setting in the config?

Hi, I did a installation with the latest openlitespeed package on debian 9 and it is good for SSL. MY config is (Beside the default conf) listener Defaultssl { address *:443 secure 1 map Example * keyFile...

Hi Brian, Please make sure you build the module and openlitespeed with the same source code. It seems the module is not loaded correctly. Thanks. David

Thank you for letting me known. Nice.

I just fixed this bug in the latest version 1.4.28. Can you try this version? And for the GitHub last commit, I fixed another bug of duplicate response headers, so if you want to try 1.4.28, you may want to download the code from GitHub. Thanks for your feedback.

I did some tests locally with a newly installed OLS and instantiated a new vhost from template PHP_SuEXEC, set the public_html DIR another as own as test:test. It runs as DOC GUID. 1207 postfix 20 0 92108 4112 3020 S 0.0 0.0 0:00.00 pickup...

Once the VHost was created, you still need to set the Virtual Host Mappings in the listener. Did you do that?