Search results

Howdy, No problem. It really should not matter which you choose. Apache + ModSSL should be safe choice, though. (This is a really weird list, by the way. cPanel, Plesk, H-Sphere, etc. are not web servers. Zeus is dead. I've never heard of a bunch of these other ones, but they don't have nginx...

Hey, The developers don't know why you're getting this error. So they're really glad you contacted them. They added better logging for the cache function in 1.3.2 so that they can figure out why this is happening. Can you set your debug log level to 10 and reproduce the error? Then please send...

Howdy, Well, the first place to start would be to check you error log. It's located in /usr/local/lsws/logs/ What kind of error are you seeing? Cheers, Michael

Yup. yum upgrade openlitespeed Add the version number afterwards if you want to switch to a particular version as opposed to the latest version (for example: yum upgrade openlitespeed-1.2.9)

Sweet!

Howdy Blaze, Sorry to make you wait. I was on vacation and I guess all the other guys are busy with other things. (Especially, I haven't seen @Slavik around recently.) OpenLiteSpeed isn't a drop in replacement for Apache the way LiteSpeed Web Server Enterprise is. You can definitely do most...

We beg to differ. :) It's not that easy to add. And especially when there's the yum option already, adding in version manager functionality seems les important than many other things. And, no, using yum upgrade will not get rid of your configs. m

Hi Saeid, OpenLiteSpeed is not meant for use with cPanel. OpenLiteSpeed does not read Apache configurations, which means that cPanel will not be able to communicate with OpenLiteSpeed. If you want an event-driven web server to use with cPanel, you should check out our Enterprise edition...

Yup. yum install openlitespeed-1.2.9 Using yum is discussed here: http://open.litespeedtech.com/mediawiki/index.php/Repositories m

You're welcome. m

Hi Joe, Sorry your having trouble with this. This is a bug in 1.3.1. (The bug is with protected contexts and has been addressed in other threads.) It will be fixed in 1.3.2, which is about to come out. Please keep in mind, also, that the current stable version is 1.2.x, not 1.3.x. Cheers...

Sweet. Let me know.

I asked around: We did look into adding memcached in the past, but had trouble adding it to our PHP compiler. We're definitely up for looking into this again in the future. I'll see that it's put on the to do list, but it may be a little ways down on the list. Cheers, Michael

You do need the source code in some form or another. You can apply the changes directly by using the patches outlined on the group. (I know you won't be doing this, as per your other thread, but it pains me to leave this unanswered.) m

Oh. It should definitely be this month. :) m

Howdy, There does seem to be a bug: https://groups.google.com/forum/#!topic/openlitespeed-development/8hCiIDd-0Ek The developers are working on it and expect to release 1.3.2 soon.

I'm sorry there was confusion. I will look into making a separate URL for the latest stable version. It's not going to be the top priority, but I'll make sure it gets on there. Until then, I'll be more careful about announcing which is stable and which is not. (It's listed here, but I can...

Hey Tracy, The developers also have said that, if you're willing, they'd like to help fix the image problem you're having. They'd need to be able to log into your machine to troubleshoot, though. Cheers, Michael

Hi Tracy, I'm really sorry to hear that. 1.3 (and 1.3.1) have been a pretty huge jump from 1.2 — integrating the new API and adding caching. This is why we've continued to call 1.2.9 the stable version. Possibly, though, we should have been more vocal about which version is the stable version...

Sorry. On Github, we only upload the final releases. The development repo is internal only. m