• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Resolved upstream timed out (110: Connection timed out) while connecting to upstream

Only when I go to plugin installation page I still get timeouts . Do have api.wordpress.org added to /etc/hosts and as mentioned Plesk firewall replaced by TransIP firewall which block no outgoing traffic.

An unexpected error occurred. Something may be wrong with WordPress.org or this server’s configuration. If you continue to have problems, please try the support forums.
and error in log

[28-Sep-2023 13:06:09] WARNING: [pool staging.snaakontwerp.nl] child 21763 said into stderr: "PHP message: PHP Warning: An unexpected error occurred. Something may be wrong with WordPress.org or this server&#8217;s configuration. If you continue to have problems, please try the <a href="Forums | WordPress.org">support forums</a>. (WordPress could not establish a secure connection to WordPress.org. Please contact your server administrator.) in /var/www/vhosts/snaakontwerp.nl/staging.snaakontwerp.nl/wp-includes/update.php on line 211"
 
similar error repeated connecting to WordPress api as I have to install a plug-in from the dashboard I also have in WP Toolkit:
[2023-09-29 04:11:06.090] 73516:6516322b0cf36 ERR [extension/wp-toolkit] Unable to retrieve data by "https: //api.wordpress.org/plugins/info/1.1/?action=query_plugins&request[page]=1&request[per_page]=40&request[search]=*Query+Monitor*&request[fields][description]=0&request[fields][short_description]=1"

is also shown in `tail -20 /var/log/plesk/panel.log` so despite the fact that I updated name server:
cat /etc/resolv.conf
# Generated by NetworkManager
search nl
#nameserver 195.8.195.8
#nameserver 2a01:7c8:7000:195:0:8:195:8
#nameserver 2a01:7c8:7000:195:0:135:195:135
nameserver 8.8.8.8

and added api.wordpress.org to hosts file

cat /etc/hosts
127.0.0.1 localhost.localdomain localhost localhost4 localhost4.localdomain4
::1 localhost.localdomain localhost localhost6 localhost6.localdomain6

10.0.2.15 dazzling-davinci.149-210-210-150.plesk.page dazzling-davinci
66.155.40.202 api.wordpress.org

xx.xx.xxxx.180 xxxbeheer.nl xxxbeheer

turned off Plesk Firewall and have only transip.nl firewall turned on I still cannot ping the api
ping api.wordpress.org
PING api.wordpress.org (66.155.40.202) 56(84) bytes of data.
^C
--- api.wordpress.org ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 9251ms

and locally I can

ping api.wordpress.org
PING api.wordpress.org (198.143.164.251): 56 data bytes
64 bytes from 198.143.164.251: icmp_seq=0 ttl=46 time=319.839 ms
64 bytes from 198.143.164.251: icmp_seq=1 ttl=46 time=245.749 ms
64 bytes from 198.143.164.251: icmp_seq=2 ttl=46 time=257.396 ms
^C
--- api.wordpress.org ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 245.749/274.328/319.839/32.531 ms

But what could block the access if I do not use Mod Security, Plesk Firewall and only TransIP firewall for incoming ports?
 
I checked ports

time nmap portquiz.net
Starting Nmap 7.70 ( Nmap: the Network Mapper - Free Security Scanner ) at 2023-09-29 04:27 CEST
Nmap scan report for portquiz.net (35.180.139.74)
Host is up (0.015s latency).
rDNS record for 35.180.139.74: ec2-35-180-139-74.eu-west-3.compute.amazonaws.com
Not shown: 977 filtered ports
PORT STATE SERVICE
22/tcp closed ssh
23/tcp closed telnet
32/tcp closed unknown
53/tcp closed domain
80/tcp closed http
135/tcp closed msrpc
139/tcp open netbios-ssn
143/tcp closed imap
256/tcp closed fw1-secureremote
443/tcp closed https
445/tcp closed microsoft-ds
554/tcp closed rtsp
993/tcp open imaps
995/tcp closed pop3s
1025/tcp closed NFS-or-IIS
1720/tcp closed h323q931
2160/tcp closed apc-2160
2393/tcp closed ms-olap1
3306/tcp closed mysql
3389/tcp closed ms-wbt-server
5225/tcp closed hp-server
5988/tcp closed wbem-http
12000/tcp closed cce4x

Nmap done: 1 IP address (1 host up) scanned in 22.91 seconds

real 0m22.927s
user 0m0.124s
sys 0m0.177s

based on thread How to detect if a network is blocking outgoing ports? to check for closed outgoing ports. Port 443 for https and 80 for http are closed outgoing ports. Do need these open.. or at least for api.wordpress.org
 
Back
Top