Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter cptwillard

    (@cptwillard)

    Wouldn’t the smarter thing to do be to provide the delay feature in the free version so as not to have someone run into the problems I have? Who would upgrade to Pro if they kept hitting this problem?

    Thread Starter cptwillard

    (@cptwillard)

    It’s interesting that you say that because my workaround is to use mobile data via mobile hotspot on my phone.

    I thought it was because the firewall treated IPv6 addresses differently. But it might have more to do with the way mobile data is delivered.

    As to your comment about additional questions…

    May I have a pro version of the migrate tool for free for testing purposes. I’ll share the results of the delay here.

    Thread Starter cptwillard

    (@cptwillard)

    It was in the pull stage, not the push. (Getting files for Local staging).

    From what I can gather, trying to pull down the WP Core files triggers a firewall rule that can make your hosting provider automatically put your ISP IP address on their challenge list (which is globally distributed) without any warning at all.

    I kept complaining of losing connectivity (email, WP, cPanel the lot while the site stayed live) whenever I tried to connect over my static IP (challenge-listed).

    It ended up in a big mess because as far as their sysadmins were concerned it wasn’t their systems that were triggering the block (it was), so they would repeatedly lodge a request to remove me from the distributed challenge list, my IP would be unblocked temporarily and then I’d be re-added each time that I retried the offending operation (including core files in the migrate profile). They eventually got their own requests blocked after lodging too many. Great.

    Eventually, they smugly satisfied themselves that it wasn’t their problem and that something else was causing me to be put on the challenge list “beyond their control”. All that they had to do was whitelist my IP, but they refused, sticking to their guns and telling me to check that I didn’t have malware on my site (which was still live so der) or on my home access PCs (Guh). Eventually we checked with our ISP and they confirmed that we weren’t blacklisted anywhere by them.

    My hosting provider lit slip in a screenshot who their FW provider was and I started reasearching their firewall system. Then I installeld it on a Linux box to see how it worked. I eventually had a support guy reach out and I explained the situation and he looked at the detailed incident logs and proved unequivocally what I was saying was true – their servers, my IP and my domain were the only end points involved.

    So you can get blocked without and warning at all just for using a simple tool if your hosting providers are incapable of logic or using their own software.

    I have a new static IP now and another workaround so I don’t care. After 5 days battling with arrgoant tech admins, I’m done. Last I heard, they referred the case up to their upper tiers after I forwarded a screen shot of my correspondence with their firewall provider with them. Somebody on the chain apparrently said “err…yeah that’s actually possible”. lol. And der.

    Anyway, you can probably tell I’d rather scrub my body with fire ants than help them anymore. But I thought you guys might be interested.

    • This reply was modified 1 year, 11 months ago by cptwillard.
    • This reply was modified 1 year, 11 months ago by cptwillard.
Viewing 3 replies - 1 through 3 (of 3 total)