Search results

For this kind of warning, I'd say it's best to follow it, but what is the exact warning?

Hmmmm. It could be related to that. Will you be upgrading to 1.3.6 now? Can you watch to see if it happens when you upgrade? Michael

Basically, it is what the thread title says it is. 1.3.6 fixes all known bugs in the 1.3 branch. Cheers, Michael

The admin listener port was reset by an OS upgrade? You didn't change anything in OLS? That does sound weird... m

Why thank you. We try to help everyone as soon as we can. I'm about to be in Russia for a couple days (a conference), so things might slow down a bit. Ran it by the developers (I never deal with source code myself). They say you should run: patch -p0 < dynrespstallpatch.txt Cheers, Michael

Hmmmm. This could be a separate issue. We have not had any reports of this on Standard or Enterprise. Here is a patch for 1.3. If it does not fix the issue, then you are experiencing a different problem. (This would also explain why you have the issue on Standard.) If you'd like the techs to...

Depends on if you're using Apache configs or not. If all your configs are in LiteSpeed-native files, there are not too many files to edit when you're switching back and forth. (Technically, you might be able to use the same XML files for LSWS Standard and OpenLiteSpeed, but this is not something...

Howdy, Thanks for reporting this. We believe this is a bug that was reported recently on the Google Group. It will be fixed in the next version. You should be able to use versions 1.3.5 or 1.2.11 without issue. Cheers, Michael

Thanks for your feedback! m

Thanks for considering us and for letting us know how your decision process went. Let us know if you ever have any other questions. (And tell your friends!) Michael

Moved this to it's own thread. Can you post your configs so we can reproduce it? m

Thanks for following up. We've removed 1.4 from the repository until we can fix that functionality. It won't be added back to the repository until that works better. Michael

Great. Let us know if you run into any issues or need any help. Cheers, Michael

Developers are looking into this now. Your configs should be automatically changed to the flat file style 1.4.x uses when you upgrade, but maybe this doesn't happen when you use the repository... m

Hi Akia, At the moment, I don't believe there are any outstanding issues with OpenLiteSpeed 1.2.11 and 1.3.5. As far as pros over NGINX, our benchmarks have OpenLiteSpeed beating NGINX pretty handily. (These are with small files, though.) We've also got a nice GUI. Cheers, Michael

Also, I'll start posting when new versions are out. We're up to 1.2.10, 1.3.4, and 1.4.1. 1.4.1 is still beta, 1.2.10 is stable, and 1.3.4 is this close to being stable but still has one existing bug. m

Howdy, I posted this to the Google Group, too, but I figure posting it here can't hurt. PHP with LSAPI is now available from the Remi Repository: http://rpms.famillecollet.com/ The package name is php-litespeed. Remi Repo contains packages for PHP 5.4, 5.5, and 5.6. It's widely used and...

Thanks for making this!

Howdy Shahin, Yeah. open_basedir is not supported on OpenLiteSpeed yet. If you'd like to work on it, the basic components for it are in the source code, but have not been implemented into a setting. Otherwise, we'll try to fit it on the road map when we get a chance. As for your second...

Hi Steven, Sorry for the long period of silence. For some reason the alert that you had made a post went to my spam box. Just to make sure, when you're stipulating the path to OpenSSL, you should put the path up to but not including "include". So your config command would look something like...