WordPress.org

Forums

WordPress Site IP Blocked/Blacklisted (11 posts)

  1. rappeneckers
    Member
    Posted 2 years ago #

    Hi there,

    I recently designed a website for a local school, meposchools.org. We launched the website this past weekend (08/17), and everything has been working fine up until today. I hope I can explain the issue we are having in good enough detail:

    When someone at the school tries to access the website while using the wireless internet connection at the school, the website will not load or show up no matter how many tries. If you are viewing the website using the school's wired/ethernet connection, it will load perfectly.

    Since the wireless connection uses a dedicated IP address: (209.152.119.138), we have come to the conclusion that WordPress has possibly blacklisted/blocked the dedicated IP address, thus explaining why the website is showing up correctly everywhere but on the school's wireless connection.

    I have contacted GoDaddy 5 times today in regards to this issue and they have told me every time that it is an issue strictly within WordPress. If you could let me know what steps we need to take to resolve this issue ASAP I would appreciate it. The website will be unavailable for most of the faculty/students while this issue continues to occur, any help would be greatly appreciated!!

    Thank you in advance for your help,

    Kyle

  2. ClaytonJames
    Member
    Posted 2 years ago #

    When someone at the school tries to access the website while using the wireless internet connection at the school...
    ...If you are viewing the website using the school's wired/ethernet connection, it will load perfectly.

    WordPress doesn't block or blacklist any IP's on its own, and Godaddy has no control over the schools network infrastructure. It's more likely an internal network issue. Contact the IT department at the school and be prepared to demonstrate/duplicate the issue for them. They will point you in the right direction.

  3. rappeneckers
    Member
    Posted 2 years ago #

    Thank you for the response, but the school's IT department is certain it's because of some issue with WordPress. Do you have any idea what could be causing this problem and the steps we can take to get things resolved?

    Thanks for the additional help,

    Kyle

  4. rappeneckers
    Member
    Posted 2 years ago #

    Also, could any WordPress plugins be causing this issue? Here are the plugins currently activated on the website:
    Akismet
    All in one Favicon
    BackUpWordPress
    Deactivate | Edit | Backups
    category post shortcode
    Custom Menu Shortcode
    Display Posts Shortcode
    Easy2Map WordPress Plugin
    Facebook Feed Grabber
    flickrRSS
    Get The Image
    Go Daddy Quick Setup
    Hello Dolly
    Jetpack by WordPress.com
    JSL3 Facebook Wall Feed
    List Pages Shortcode
    My WordPress Login Logo
    Post Content Shortcodes
    Revolution Slider
    Role Scoper
    U-Design Shortcode Insert Button
    U-Design WooCommerce Integration
    Welcome to WordPress
    WP-PageNavi
    WP125

  5. shamratdewan
    Member
    Posted 2 years ago #

    as wordpress should not be blocking wifi traffic for center IP. i would suggest (just to check its not WP who is blocking) put a plain html file on the root naming it index.htm and see wifi machines can see the page.

  6. rappeneckers
    Member
    Posted 2 years ago #

    If the dedicated IP address at school used for the wireless connection received hundreds of hits this week at the same time, would WordPress consider that IP address spam and block it? That is the conclusion that the IT department has made at the school and they are certain of this after running trace routes test side-by-side for the wired/wireless connections. The wireless connection get's stuck when it hits the dedicated IP address, where it goes through fine for the wired/ethernet connection since it isn't passing through that dedicated IP.

    I will add the index.htm file to the root folder and see if this does anything. In order for them to view the index.htm file, wont they have to use the same IP address that has been blocking the site already?

    Thanks,

    Kyle

  7. ClaytonJames
    Member
    Posted 2 years ago #

    WordPress consider that IP address spam and block it?

    No. Again, not on it's own. Not by itself.

    That is the conclusion that the IT department has made at the school and they are certain of this after running trace routes test side-by-side for the wired/wireless connections.

    Traceroute alone seems a very limited tool set for any accurate conclusions at this point. It implies "where", but not "why" the problem could be happening.

    Since the wireless connection uses a dedicated IP address: (209.152.119.138)....
    ....The wireless connection get's stuck when it hits the dedicated IP address,

    As far as I can tell - from the limited external window with which an outsider can look upon your issue - 209.152.119.138 resolves to a mail server for the mepovollyball.org and meposchools.org domains.

    I think it's possible that the 209.152.119.138 IP address belongs to a CIPAFilter network security appliance. You might Google CIPAFilter for a quick description of what that particular appliance does.

    So, if your outbound traffic is stopping at the IP address of a network security appliance located inside your own network, you may want to get your IT department involved again. It's strange that they wouldn't recognize the device at that address (assuming it's on site, of course).

    If you still want to test the WordPress theory, you can start by temporarily disabling all of your plugins and then temporarily applying the default WordPress theme to see if the behavior changes.

    Just guessing, mind you..

  8. rappeneckers
    Member
    Posted 2 years ago #

    Still no fix to this issue, any further help would be greatly appreciated.

    After further investigating, GoDaddy is 100% certain it isn't an issue with their servers, they are certain it has to be an issue with WordPress. We enabled the 'error logs' that were received when trying to connect to the wireless connection at the school and this is what it said:

    [Fri Aug 23 04:15:31 2013] [11410783] [core:error] [client 198.153.112.222:62648] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace., referer http://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=3&ved=0CDMQFjAC&url=http%3A%2F%2Fnew.meposchools.org%2Fteachersstaff%2Ftechnology-help-desk%2F&ei=TEQXUpCTF9C02wXIu4CYBA&usg=AFQjCNGb-ARpxsy_s4an4Fgy_T5yRlrt2A&bvm=bv.51156542,d.aWc
    [Fri Aug 23 04:15:31 2013] [11410783] [core:error] [client 198.153.112.222:62650] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.
    [Fri Aug 23 13:33:04 2013] [11410783] [core:error] [client 66.249.75.86:53069] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.
    [Fri Aug 23 13:34:07 2013] [11410783] [core:error] [client 66.249.75.98:41658] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.
    [Fri Aug 23 13:55:39 2013] [11410783] [core:error] [client 66.249.75.106:62937] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.
    [Fri Aug 23 14:03:18 2013] [11410783] [core:error] [client 66.249.75.94:40524] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.
    [Fri Aug 23 16:40:10 2013] [11410783] [core:error] [client 66.249.75.112:43277] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.
    [Sun Aug 25 14:45:04 2013] [11410783] [core:error] [client 66.249.72.76:35199] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.
    [Sun Aug 25 15:53:03 2013] [11410783] [core:error] [client 66.249.72.76:36419] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.
    [Sun Aug 25 16:33:56 2013] [11410783] [core:error] [client 66.249.72.76:35625] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.
    [Sun Aug 25 18:26:15 2013] [11410783] [core:error] [client 66.249.72.76:55200] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.
    [Sun Aug 25 20:05:55 2013] [11410783] [core:error] [client 66.249.72.76:55397] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.
    [Mon Aug 26 04:14:39 2013] [11410783] [core:error] [client 66.249.72.76:54052] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.
    [Mon Aug 26 04:14:39 2013] [11410783] [core:error] [client 66.249.72.76:43864] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.

    GoDaddy said that the error has to do with the .htaccess file for the website. After doing some research on the error and it's connection to the .htaccess file, I added these codes to the .htaccess file (they were added and tested one at a time, none of them solved the issue):

    1.)
    RewriteRule ^(.+)$ /index.php/$1 [NC,L,QSA]

    2.)
    RewriteCond %{ENV:REDIRECT_STATUS} 200
    RewriteRule ^ - [L]

    At this point, what else can I try?? Could it be a plugin causing the issue? (the list of installed plugins is posted in the above messages)

    Any further help or advice would be appreciated.

    Thanks,

    Kyle

  9. lnemeth
    Member
    Posted 1 year ago #

    I am having this same very issue. My users cant access our new district website internally. It goes off and on, but mostly loads blank pages for them. Works fine externally. http://www.fairviewparkschools.org/

    Were you able to resolve??

  10. rappeneckers
    Member
    Posted 1 year ago #

    I was only able to resolve the issue by moving the site from GoDaddy to BlueHost. Unfortunately I spent weeks looking for a solution, but it always ended up being GoDaddy's blacklisting issue that they never admitted to. I hope this information helps, contact your hosting provider and check with them.

  11. lnemeth
    Member
    Posted 1 year ago #

    Thank you so much for your quick reply. I had the same thought and may roll back to Host Gator -- this all started happening when I migrated to a new host provider. I came off HG because I felt like it was super slow. I personally think it's a network firewall issue, but our IT dept. doesn't seem to have any answers for me right now. Grrrrr!
    Thanks again.

Topic Closed

This topic has been closed to new replies.

About this Topic