Search results

OK thanks for clarifying. If I do see other requests get affected, how do I turn the throttling off? That's part of what I was asking originally, what piece of LSWS is actually doing the throttling and how is it that the requests are getting throttled if I have added the Railgun IP to the...

OK but I am 100% certain the Railgun is being affected. I am tailing both LSWS' error_log and the messages log on the Railgun server, and whenever LSWS issues Brute force detected for IP [xxx.xxx.xxx.xxx], throttle. the railgun rg-listener log shows origin timeout: cloudflare/http: timeout...

OK now in the logs I see the new format, Brute force detected for IP [XXX.XXX.XXX.XXX], throttle. 2018-01-10 23:49:37.523 [NOTICE] [XXX.XXX.XXX.XXX:42318] Brute force detected for IP [YYY.YYY.YYY.YYY], throttle. where XXX.XXX.XXX.XXX remains the Cloudflare Railgun server on my network and...

OK I had been running 5.2.3 but ran the updater, perhaps I had an earlier build. But just as FYI the IP address noted in LSWS error_log was the IP of the Railgun on my network, not the external Cloudflare IP... Will let you know if I see any different behavior with the new version. But to be...

I am seeing lines like these in my error logs: 2018-01-10 22:11:03.423 [NOTICE] [XXX.XXX.XXX.XXX:39804] Brute force detected, throttle. I know the IP Address is from a Cloudflare Railgun on my network, so I do not want its access to ever be throttled. I assumed the throttling was being caused...

Not sure what you mean by "Please give a report number." Do you mean have I filed a support ticket yet? I have not... The device we are seeing the desktop theme on is an iphone, so I assume it is on everyone's list of mobile user agents... How would the desktop version get into the mobile cache?

We've got several sites using the LSCP for WP that use a mobile theme plugin that intermittently show the desktop theme instead of the mobile theme. Clearing the cache solves the issue. Has anyone experienced this? How to resolve? Our setup is out of the box, with "Cache Mobile" set to On and...

That does not seem to allow editing of our htaccess yet...

We are seeing a problem on several WordPress installs ... using the latest version of Litespeed, WordPress, and the Litespeed Cache WordPress plugin... The issue is that the contents of the htaccess file can not be read nor edited. When we go to the /wp-admin/admin.php?page=lscache-settings...

That's very clear and helpful, thanks!

OK If I set those particular settings at the server level, will that have any impact on sites not running WordPress?

Inside the Litespeed WordPress plugin, there is the Information section which shows the following... Just want to make sure that a) these instructions are still accurate and b) should be fine in a shared server environment? LiteSpeed Cache Configurations Please check to make sure that your web...

PHP user has permission to write to directory, all other WordPress operations requiring that like plugin and theme updates work successfully. Plugin was installed via the Add New plugin button in WP itself (ie via control panel not FTP so again PHP has permission on these folders. Errors I see...

Yes, I mean the document root... None of my sites installed into a subdirectory off the document root can read or write settings into the .htaccess files using the latest version of Litespeed server and WordPress plugin...

I have had success with the latest wordpress Litespeed cache plugin on sites that have Wordpress installed into the root, but when I try it on sites that have WordPress installed inside a directory like /wordpress from the root, Litespeed plugin can not find or read from or write to htaccess...

Looks like the rule is fine, the files were just being caught by some rule earlier in the chain... When I moved them to the top of the file it worked fine. Thanks!

OK, I was using those hosts to protect the client's privacy. They were trying to block other hosts than myspace. I will send in a ticket. Thank you.

RewriteEngine on and rewrite log doesn't seem to tell me anything... Site is real busy so rewrite log went to 1 GB in minutes so it's hard to find anything in there...

As per this doc: http://docs.joomla.org/How_do_you_block_direct_hot_linking_to_image_files_using_.htaccess I am trying to ban specific domains from hotlinking using this: RewriteCond %{HTTP_REFERER} ^http://(.+\.)?myspace\.com/ [NC,OR] RewriteCond %{HTTP_REFERER}...

I ended up deleting the installation and reinstalling it... Not sure what the issue was but the reinstallation seemed to solve the issue. I'll be sure to update this thread if I see it again...