• After reviewing our logs, we believe that MailPoet may be blocking or rate-limiting requests from our external IPs. We have also seen a few reports similar to this recently, so it may be a recent change that MailPoet have made. I would recommend contacting MailPoet and asking them to check their logs for any blocks/rate-limits on the following IPs:

    London (LHR) Packages:
    45.8.227.174, 45.8.227.175, and 45.8.227.176

    Please can this be resolved ASAP? It is causing intermittent connection issues.

Viewing 1 replies (of 1 total)
  • Plugin Support Gui A. a11n

    (@guicmazeredo)

    Hi there,

    Thanks for the detail here, and for including the specific IPs and the pattern you’re seeing. That gives us a good starting point.

    To set expectations up front: we don’t currently have any known block or rate-limit in place against those IPs (45.8.227.174–176). That doesn’t mean nothing’s wrong, just that “MailPoet is rate-limiting these IPs” isn’t something I can confirm yet, so I’d like to narrow down where exactly the connection is failing before pointing anywhere.

    A few things that would help a lot:

    1. Which MailPoet feature is hitting the error? “Intermittent connection issues” can come from a few different places: activating/validating your license key, sending through the MailPoet Sending Service, or the general connection to our API. Knowing which one narrows this down quickly.
    2. The exact error text. If you can copy the full message (and where it appears), that tells us whether the request is even reaching our servers or failing earlier.
    3. A copy of your System Status. In your WordPress admin, go to MailPoet → Help → System Status. That page shows the live connection state to our services and often surfaces the specific failure. A screenshot or copy of what it reports would be really useful.
    4. A copy of your System Info in MailPoet > Help. Please make sure to remove sensitive information before sending it (email addresses, for instance).
    5. Timing. Roughly when the intermittent failures started, and whether they line up with any change on the host side (new IPs, a proxy/CDN in front of outbound traffic, a firewall update).

    Once I can see which call is failing and the exact response, I can check it against our logs from the right angle and give you a definite answer rather than a guess.

    Looking forward to hearing from you!

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.