Search results

Yes, I adapted that one to fit my needs. I didn't like the 3 in 10 seconds and prefered 15 in 3 minutes. Adding just the Jooomla and the Wordpress rule reduced the load on our server by nearly half and hasn't noticibly reduced the response times. I'm quite impressed by litespeed's...

I'm testing the following rule at the moment : # Joomla Brute Force Protection # <LocationMatch "/administrator/index.php"> SecAction phase:1,nolog,pass,initcol:ip=%{REMOTE_ADDR},initcol:user=%{REMOTE_ADDR},id:00113 SecRule user:bf_block "@gt 0" "deny,status:403,log,id:00114,msg:'IP address...

Just got this working. I recompiled with easy apache adding mod security and placed the code in /usr/local/apache/conf/modsec2.user.conf (I had to create the file). Next step, work out a rule for Joomla ! :)

Hello, We are currently being hit quite hard from brute force attacks on wp-logins so I wanted to implement this too. I must be doing something wrong though… In cPanel went to apache include editor and added the following to the pre_main include : <IfModule mod_security2.c> # This has to be...

I'm sorry I'm not sure why you are asking me to test under apache… I t's working well here under litespeed, the only issue are the ports. I'm quite sure if litepeed isn't running under the username it would not be able to access a nodejs process running on CloudLinux's future virtual...

Hello, Went one step further… installed npm on the user account and ran npm install forever -g Then added to user crontab @reboot /home/USER/.nave/installed/mynode/bin/forever start /home/USER/example.js In therory (haven't tested a reboot yet the users process should run permanently The...

Ok, I've tested creating and external app + the .htaccess rules above and using the following code var http = require('http'); http.createServer(function (req, res) { res.writeHead(200, {'Content-Type': 'text/plain'}); res.end('Hello World\n'); }).listen(50000, '127.0.0.1')...

I've found some documentation here : http://www.a2hosting.com/kb/installable-applications/manual-installations/installing-node-js-on-shared-hosting-accounts Thant says to use : RewriteEngine On RewriteRule ^$ http://127.0.0.1:XXXXX/ [P,L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond...

Hello, You specify that the latest version of litespeed supprots proxy rewrites in hatcess for usage with nodejs. Nodejs is easy to install with nave: https://github.com/isaacs/nave It would be nice to have some documentation about getting it up and running with litespeed :)

Thanks, we will wait for cPanel to be ready to announce this too then :)

Hello, any news on this ? I see you announced that Plesk now supports litespeed as an official plugin, it would be nice to know a bit more about cPanel's official support :)

We had a similar issue, we created a ramdisk for gzip cache and litespeed was using up all the inodes. Moving the cache to /dev/shm or increasing the numer of innodes available in the ramdisk solved the issue. If you have configured alot of cache for litespeed maybe you should try reducing it...

You tweeted it :) https://twitter.com/litespeedtech/status/486562556345974784

I belive this is now in the process of becomming true… can you give us any details about the official litespeed support ?

Ok, I tried to switch to Apache but Apache refused to start, so I'm going to wait for a very calm moment before trying the switch again…

Ok, thanks, I hope you find out why this doesn't work :)

I don't think this would work with solutions like owncloud as owncloud manages it's own webdisk for syncing files from folders on your computer to your hosting accont. I belive for this to work it has do be done over the same port as you access owncloud's webinterface. OwnCloud works well with...

Hello, if this is too complicated we would be satisfied with an automatic proxy to apache when webdav is detected.

I think it is sni the issue as non sni accounts have it working, I'ill switch back to apache if it still doesn't work after you have added sni support to https proxy. Thanks

I've got 4.2.11 and as this is a production server I would prefer to not have to install the developpement version. It seems to be working on sites that have their own IP but not on sites that share the main server IP.