• Hello,

    I am experiencing a connectivity issue with WordPress.org infrastructure from only one specific server IP.

    Server environment:

    • AlmaLinux 8.10
    • Plesk

    Problem:
    The server cannot connect to:

    • api.wordpress.org
    • wordpress.org
    • downloads.wordpress.org

    As a result, the WordPress Plugins page shows:

    “An unexpected error occurred. Something may be wrong with WordPress.org or this server’s configuration.”

    Tests performed:

    1. Direct connection from primary server IP:
    1. Direct connection to WordPress.org IPs:
    • 198.143.164.251 -> timeout
    • 198.143.164.252 -> timeout
    1. Firewall investigation:
    • firewalld temporarily disabled
    • same timeout result
    • no CSF installed
    • OUTPUT policy ACCEPT
    1. Connectivity to other websites:
    • google.com -> OK
    • github.com -> OK
    • cloudflare.com -> OK
    • wordpress.com -> OK
    1. Important finding:
      The same server has additional public IP addresses.

    Using another IP on the SAME server:

    curl –interface [secondary IP] -I https://api.wordpress.org

    Result:

    HTTP/2 302

    This means:

    • Same server
    • Same operating system
    • Same gateway
    • Same firewall
    • Same network interface

    Only one specific public IP cannot reach WordPress.org infrastructure.

    Could you please verify whether this IP address or its network is being filtered by WordPress.org infrastructure?

    The affected IP address can be provided privately to moderators or infrastructure staff if required.

    Thank you.

    • This topic was modified 3 days, 23 hours ago by owerer.
Viewing 5 replies - 1 through 5 (of 5 total)
  • Moderator threadi

    (@threadi)

    Try a traceroute from your hosting to wordpress.org. This should help you pinpoint exactly where the problem lies.

    Thread Starter owerer

    (@owerer)

    I ran a traceroute from the affected server.

    The route reaches Cogent in the US and continues up to ORD (Chicago), then stops responding after hop 19.

    More importantly, I tested from another public IP on the same server:

    • Primary IP: cannot connect to api.wordpress.org (timeout)
    • Secondary IP on the same server: connects successfully and receives HTTP/2 302 from api.wordpress.org

    The server, OS, firewall, gateway and network interface are identical. Only the source public IP changes.

    This is why I suspect the issue may be related to the affected IP address or its network range rather than the server configuration itself.

    • This reply was modified 3 days, 20 hours ago by owerer.
    Moderator threadi

    (@threadi)

    To me, that sounds like a routing issue, rather than something on wordpress.org rejecting the request. I’d recommend reporting it in the #meta channel on Slack – or waiting to see if it resolves itself (sometimes it’s just a matter of a few hours).

    Thread Starter owerer

    (@owerer)

    Thank you for your help.

    My hosting provider has completed additional network tests and believes that the affected network range (178.251.238.0/24) appears to be blocked or filtered somewhere on the WordPress.org side.

    The issue only affects addresses from this subnet. Other public IP addresses on the same server can access api.wordpress.org normally and receive HTTP/2 302 responses.

    Thread Starter owerer

    (@owerer)

    I look forward to your response. Thank you.

Viewing 5 replies - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.