It all makes sense now and I hope this helps others googling the same issue. Being from the era of IBM 360s and PDP10s, I assumed the server was a physical machine at their office, not somewhere else like Lansing Michigan. Once our HOST told me that some of our issues are probably because we are using a "Cloud Server" I started to put the pieces together. I am not a computer techie, just an Admin running a board and learning more every day - harder at 67! Eventually I figure most things out, the group here is very helpful. Like me at the start, you look at it and go " that IP of 207.246.240.121 is not my IP!". At Liquid Web, we respond to your phone and chat support requests in less than a minute, but if you need a quicker response, there are alternative options that you can try to gain access promptly. There are a lot of others with the same problem (when you google that issue) but I don't think they have noticed that the block is because of the address in the REMOTE_ADDR. The first step to resolve a blocked IP is to submit a support request to Liquid Web with the blocked IP address (which you can look up online ). As I worked through the issues, I realized that SPAMHAUS was doing its job as it had detected that our REMOTE_ADDR of 207.246.240.121 was apparently being set by our HOST and not by the PHP. I should have marked it as the initial issue was trying to stop SPAMHAUS from blocking access, which I found. Nobody seems to be doing anything to correct the problem at their end. They did not appear before we added the SSL certificate, but I have no idea why that changed. They cover the complete range of NetRange: 207.246.240.0 - 207.246.255.255, so it must fluctuate between different IP addresses, explaining why the SPAMHAUS error reports appear intermitently. Somehow it has got itself listed as being an abuse when it is a remote server. which is a Data Center / Web Hosting / Transit. If you do a ABUSE check for 207.246.240.121 and look at the Raw Whois Results for that IP, you find out it is located in LANSING, MICHIGAN and it belongs to Liquid Web L.L.C. I presume that is directly related to the fact that our system is on a cloud server and that is where it is located. Either our host changed it or it changes on its own, I don't know. At the time of this posting it has switched to PHX and yesterday it was LAN. If I click on the "?" it says " Your website can either be in the Lansing (LAN) or Phoenix (PHX) Region". For the REGION I had noticed that sometimes PHX and sometimes LAN.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |