Search results

Hmmmm... It's very strange that it's timing out, but not showing any errors... Let's try turning the debug level higher. You can't get into the WebAdmin, so you're going to have to edit the /usr/local/lsws/conf/httpd_config.xml file manually. Change <debugLevel> to 9 and restart —...

This is all there is in the error log? There is nothing after this? That is strange. Have you checked to see if the lshttpd process is running? Michael

This is normal. The WebAdmin cannot create this directory for you. You will have to create the directory yourself and add your website content in there. This is almost certainly not causing the WebAdmin to time out, though. Can you check that OpenLiteSpeed is actually running? Try accessing...

Hmmm. That is odd. Let's start with the one error we can see first. What are the permissions for /usr/local/lsws/BETAHOST? Michael

Glad to hear it! m

Hi Parham, That's exactly the situation we see a lot of people using OpenLiteSpeed. We're trying to add documentation as well as we can, but there's a long way to go. It sounds like you're not hitting the context or the context is misconfigured. What's the URL you're trying to protect? What...

And, as for ARM servers, we currently have no plans for this. Thanks for the suggestion, though. Maybe if we start hearing about ARM servers taking more of the market we'll think about it, but at the moment, it's kind of too small of a blip to be on our radar. Cheers, Michael

^^^ Lauren, by the way, is the developer in charge of the GUI. m

Hi Oyang, Thanks for the suggestion. We're not planning on doing anything like that anytime real soon, but it is a reasonable idea. I'll make a note of it and bring it up with the developers. There are, however, a number of ways to better secure your WebAdmin console currently: Change the port...

Hi Oyang, We've been unable to reproduce this. Can you try doing a clean reinstall? If you're still having this issue, please set the Debug Log Level to HIGH and send us the error log. This wiki explains how to toggle debug logging...

Thanks for following up. And that PHP setup looks fine to me, at least for most web applications. Cheers, Michael

Hi Oyang, Thanks for trying out OpenLiteSpeed. We're not exactly sure why you're getting this issue right now. Our developers are testing it out to see if they can replicate it. I'll notify you as soon as we know more. Cheers, Michael

Ha. Sorry. We're going to leave 1.4.x out of the repository until it's stable. We don't want people accidentally upgrading to a beta version. If you install from source, though, the config conversion functionality works. m

Hi Parham, First, welcome to the OpenLiteSpeed community. We'll need a little more information on what exactly doesn't work. When you go to the protected context URL, you don't get asked for a password? Your password doesn't work? You see an error? Cheers, Michael

Nope. You can have both on one listener. If you're stipulating particular IPs (i.e. not just listening for [ANY]), you should write the IPv4 IPs as an IPv4-mapped IPv6 address (i.e. [::FFFF:x.x.x.x]). m

Ah. That was you asking dotdeb? I saw that tweet and it brought dotdeb to my attention. At some point, I'd like to talk to them about including PHP packages for LiteSpeed. Unfortunately, I can't see having time for that in the near future. We can definitely add a wiki explaining the rewrite...

Hi Duy, That does seem to be a bug. Thank you for reporting it. I've passed it along to the developers. We'll try to have a new version out with it fixed by the end of this week or early next week. In the meantime, you could probably do these configurations directly into the config file, if...

Thanks for the feedback. What, specifically, are you comparing OpenLiteSpeed to (both for speed and ease of setup)? NGINX? Apache? We definitely have to make OpenLiteSpeed easier to set up. That's going to be one of the big focuses next year. Cheers, Michael

I will quote @lswave from another thread: This is one of the most frequently asked questions about OpenLiteSpeed: OpenLiteSpeed rewrite rules use vhost config mod_rewrite syntax, not .htaccess syntax. We will most likely need to find a more efficient way to deal with it. For now, though...

This is a very good idea. It's something that I believe has been suggested before and something that we've definitely been considering. We haven't had time to implement it before, but I'll bring it up again and see if we can't get it on the to do list. (If someone else wants to set up a site...