Search results

Hi @skooboy, I'll put this on our list of things to do. Updating it, though, will not be a really easy process (it will require a lot of testing), so it may be a while before we get to it. If you come across or figure out settings that improve this, we'd be happy to update the wiki. Cheers...

This has really become a hot topic recently: I don't know of anyone making a plugin for Joomla! right now (though I can think of at least one company that might be working on it). I do know of a couple hosting companies that are working on Drupal and/or WordPress plugins, so keep you eyes...

Hi @Kynao, I'm sorry to report that we haven't made any progress since the last update. We've been going full steam on HTTP/2 support and our Magento caching extension. There hasn't been time to look into what the Interworx plugin is going to take. I know, though, that Interworx is still open...

If you're looking for an expert outside of your hosting provider, by the way, these guys are pretty good: http://www.litespeedtech.com/partners/support-partners m

Well, the first thing I would suggest is to harden your kernel (see the blog post I referenced above). That, though, is not meant to block big SYN floods. If that hardening doesn't stop the flood (and I suspect it might not), you'll have to look to another option: 1. Rent a hardware firewall...

Oh! No. That won't work. I'm sorry. I should have mentioned. The proxy service doesn't support HTTPS. Sorry. It's in the fine print on the Anti-DDoS Proxy intro page: http://www.litespeedtech.com/products/anti-ddos-proxy-service

Hard to say whether those are from using the two together or just one being set up improperly. Page caching is effective, but it's not easy. Time to start isolating which rules are causing the issues...

Howdy, Really, it's not the size of the attack that matters, but how distributed it is. I would suggest you begin by setting up our free proxy service. You can setup the service by clicking the "config" link under My Services. You might also want to look into hardening your kernel...

I stand corrected, I guess? Why did you decide to cache logged in members' content through Varnish and not LSCache? Also, I'd be interested in whether caching the static content makes a difference in performance. Theoretically, caching static content in front of LSWS shouldn't help performance...

Howdy, I'm assuming that you've entered your information in the product form and now you need to set up the CNAME entry to redirect traffic from your domain to the assigned subdomain. You can find a step-by-step guide to using a CNAME entry in WHM to redirect your traffic here...

Howdy, First and foremost: You'd probably be fine with a 2-CPU license or perhaps even a 1-CPU license. When you have a chance, you should really consider trying a downgrade to see if it effects your performance. Obviously, this isn't going to make your server faster, but it will save you...

You're very welcome.

Howdy, No problem at all. We absolutely understand how that goes. Check out the wiki I mentioned. It will explain this in more detail, but you're probably never going to need more than a 1-CPU license. (You don't qualify for the Ultra VPS, though, as you've probably figured out.) Cheers, Michael

Oops. Ignore that last request. Now I see the responses on your second thread. Cheers, Michael

Hi Darren, Saw your email. Sorry for not replying sooner. The trial license is a 2-CPU license: http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:license:what_license_to_choose If your VPS fits within the Ultra VPS RAM limits (8GB RAM), I would suggest the Ultra VPS license...

Hello Darren, Yes. If you uninstall LSWS, all LSWS files will be removed (unless you check the box to keep your conf or log files). You don't have to uninstall LSWS to switch your settings back, though. All your settings are switched back when you switch to Apache. Cheers, Michael

Thanks for filling us in!

Many methods of installing LSWS with the WHM Plugin (like using our auto-installer script) automatically build matching PHP when LSWS is installed. Building it again won't hurt, but it sounds like it was built when you installed. m

Ah. OK. LSWS's PHP needs to match Apache's PHP (the PHP you build with EasyApache). If you have EasyApache Integration enabled, you only need to build matching PHP once. EasyApache Integration automatically builds matching PHP every time you change PHP (with EasyApache) after that. If you do...

Howdy, Not quite sure what you mean. You need to build matching PHP when you first install LSWS so that it has a PHP build to match your Apache PHP build. If you have EasyApache Integration enabled, it will automatically rebuild matching PHP every time your Apache PHP changes. If you don't...