I would still block it. We have tons from that 69.30.193.133 IP. Also lists a Russian name as customer for IP at a datacenter in Kansas City: http://whois.domaintools.com/69.30.193.133
69.30.193.133 - satrun77 [17/Feb/2017:09:10:10 -0800] "GET /rss/catalog/notifystock/ HTTP/1.1" 401 44 "-" "-"...
We are also seeing the same thing.
Until this is patched...
Block these IPs in your firewall:
188.120.224.0/24
188.120.226.0/24
188.120.232.0/24
188.120.234.0/24
188.120.235.0/24
188.120.236.0/24
69.30.193.133
Hello all,
While browsing a site, a user will load a page and it will result in a white page with only the following text:
text/html; charset=ISO-8859-1
The user is experiencing this on two sites located on two different LiteSpeed servers, both running 4.2.14.
The first server runs a site...
I have this exact same error appearing in our error logs, however We are using PHP 5.3.27, and have never installed 5.5.X.
This is a cPanel box with LiteSpeed WS 4.2.6.
We uploaded a chat script (called CometChat) onto a site, and the script gives out a 502 Error only when on the AT&T Mobile Network. It works fine on every cable, dsl, and other mobile networks.
However, The error goes away completely when I switch to Apache, including when on the AT&T...
Hello,
I upgraded LiteSpeed from 4.1.12 to 4.2.4 and now we see this in WordPress under WP Super Cache settings:
Are these safe to ignore? The site appears to be working fine.
Or should we switch to another plugin like W3 Total Cache?
I have an issue where a modsec rule is triggered but it is not sending the user to the 403 page.
It keeps the user on the same page and shows the page as requested.
For example, If I trigger modsec by typing in:
www.yourdomain.com/?<script>alert(1)</script>
The server error log shows...
I'm receiving these in our error logs every minute or two:
2013-07-24 13:18:18.425 [INFO] [IP.ADDRESS:12112-1#APVH_deprecated.com] connection to [/tmp/lshttpd/lsphp5.sock.585] on request #500, confirmed, 0, associated process: 2040, running: 1, error: Connection reset by peer!
I recently ran...
Hello,
Due to issues we are having in 4.2.x, I tried to force reinstall version 4.1.12, i the version manager, however it is failing.
I checked the error logs and see
PHP Warning: file_get_contents(http://download.litespeedtech.com/packages/latest/lsws-4.1.12-ent-x86_64-linux.tar.gz) [<a...
I'm not sure why this keeps happening. The site randomly will go down and will be back up immediately as soon as I restart LSWS.
This is a single site running LSWS on a cPanel server, the MySQL database is on a secondary server.
As soon as the site goes down, the logs constantly state...
Hi,
I'm running 4.1.12. I've noticed modsec is working on most accounts on our shared server, but not on some of them. It's very odd...
I'm throwing this out there, but I noticed it works on all WordPress sites that have a working .htaccess file.
It doesn't seem to be working on standard...
Right but programs that cache files, e.g. WP Super Cache, W3TC, and Timthumb for example, will then require nobody as the UID/GID to the folders/files, so that it can work.
Otherwise, it errors out
Excellent, thank you. That is good to know. Would you recommend I change the that number or leave it?
Another important thing to note we have litespeed installed on many servers (all are cpanel servers), some of them used for shared hosting, some of them for dedicated sites. While I don't...
I'm running a single site on a cpanel server.
I've installed litespeed with cpanel support and disabled suexec in the litespeed admin panel.
In order for everything to function properly with the current configuration (uploading, cache files, etc), I have to chown all the user's files to...
I just looked at my access-logs to see what these IPs are accessing that is causing that. It seems to be timthumb.php is causing that error.
The timthumb.php file is the latest version 2.8.10.
Thanks NiteWave,
I was able to fix the issue regarding the crash every time I emptied the cache. I rebuilt Apache/PHP with easyapache, then built matching PHP w/ LS.
That seemed to have fixed that portion of the issue.
However, the remaining issue now appears to be this:
2012-04-02...