Search results

We are seeing these too. What do they mean, and how can we resolve them?

We get white pages when we try to use the cache with WordPress and caching rules in .htaccess. Can you provide a step-by-step guide to making LS cache work with WordPress?

Isn't 777 on a temp folder a security risk?

Thank you.

So memcache/memcached should work okay with suPHP?

I know that APC and eAccelerator have limitations in suPHP mode. I've heard mixed opinions about whether memcache/memcached will work. Can someone confirm or deny? If it will work, can someone provide the best process for installing and configuring it? Thanks, Mark

I'm wondering what the optimal LSWS settings are for WordPress. Particularly, if we use LS cache should we also use WordPress caching programs like W3 Total Cache? I've heard both yes and no, so I would love to hear an authoritative answer. Thanks, Mark

Thank you. However, disabling suEXEC would be a significant security risk, right? So the best combination of security and performance would be suPHP/suEXEC + older version of eAccelerator, correct? I have also heard some people say that memcache/memcached will work with suPHP. Is this true...

Hello, I want to get the most effective opcode caching when running in suPHP mode. In another thread, it was said that eAccelerator is the best opcode cache to use with Litespeed. And, in WHM, it was advised to install eAccelerator using EasyApache. However, that installs the latest...

@nitewave, thank you! This is exactly the kind of information I was looking for. Mark

Hi Again, Atomicorp still tells me that LiteSpeed does not fully support mod_security. Can LiteSpeed please supply complete details? We are about to deploy additional servers, but we can't put LiteSpeed on them (or continue using it on our existing servers) if LiteSpeed cannot even tell us...

Does that enable LVE in general, or also the SecureLVE (jailed files mode)?

Thanks for the reply. According to the Atomicorp Wiki, LiteSpeed's mod_security 2.x support is still incomplete, as least as of a month or two ago: http://www.atomicorp.com/wiki/index.php/Litespeed If this is true, even if you "support 2.5 rules," that does not mean that your implementation...

Same here. We see more and more hack attempts every day, and we need full mod_security support. I am a bit upset that we weren't told from the start that LiteSpeed's mod_security support is very incomplete. And now, even with Atomicorp doing all they can to help LiteSpeed implement it, it...

Congratulations! We will soon upgrade to 4.1, and we will need to upgrade from the VPS version to the 1-CPU version. (It is a VPS but we are going to go above the 2 GB memory limit.) How can we do that without losing the money we paid for the rest of the month on the VPS license? Also...

I've heard that the latest version of eAccelerator (0.9.6, which I believe is included in EasyApache), does not support caching of user objects...it only optimizes and caches PHP scripts. Is this true? If so, is it better not to compile eAccelerator in EasyApache, and instead to manually install...

When will 4.1 be released?

We will compile this information. Whatever the cause, it is very frustrating to have so many things which work in Apache but do not work in LiteSpeed. We are also experiencing issues saving theme settings in WordPress. In Apache, settings are saved almost as soon as the "Save" button is...

Hi, We're experiencing various 403s when doing various admin functions in WordPress (saving plugin settings, etc.). They don't happen in Apache. We're using the gotroot rules, and gotroot says that the 403s are probably being triggered by LiteSpeed's incomplete support for mod_security...

I wonder if it was the gotroot automatic rules installer that restarted httpd. It has a default command for doing that: /etc/init.d/httpd restart Should I enter a different command instead? I did try your suggestion, and the LiteSpeed plugin still shows only LiteSpeed running.