Hello, aaPanelers I think its a general aaPanel issue, i am using System :CentOS 8.2.2004(Py3.7.8) with nginx and php7.4 I've tried to add firewall IPs, URLs, rules but with no luck, WordPress can't access the WordPress outbound address, also tried to add define('WP_HTTP_BLOCK_EXTERNAL', false); if(window.hljsLoader && !document.currentScript.parentNode.hasAttribute('data-s9e-livepreview-onupdate')) { window.hljsLoader.highlightBlocks(document.currentScript.parentNode); } to the wp-config.php but without any luck I've tried using ssh to check the system ports and the 80,443 are opened, url -v telnet://api.wordpress.org 443 * Rebuilt URL to: telnet://api.wordpress.org/ * Trying 198.143.164.251... * TCP_NODELAY set ^C if(window.hljsLoader && !document.currentScript.parentNode.hasAttribute('data-s9e-livepreview-onupdate')) { window.hljsLoader.highlightBlocks(document.currentScript.parentNode); } i keep getting messages like: Warning: An unexpected error occurred. Something may be wrong with WordPress.org or this server’s configuration. if(window.hljsLoader && !document.currentScript.parentNode.hasAttribute('data-s9e-livepreview-onupdate')) { window.hljsLoader.highlightBlocks(document.currentScript.parentNode); } Communicating with the WordPress servers is used to check for new versions, and to both install and update WordPress core, themes or plugins. Error Your site is unable to reach WordPress.org at 198.143.164.251, and returned the error: cURL error 60: SSL: no alternative certificate subject name matches target hostname 'api.wordpress.org' if(window.hljsLoader && !document.currentScript.parentNode.hasAttribute('data-s9e-livepreview-onupdate')) { window.hljsLoader.highlightBlocks(document.currentScript.parentNode); } Warning: An unexpected error occurred. Something may be wrong with WordPress.org or this server’s configuration. if(window.hljsLoader && !document.currentScript.parentNode.hasAttribute('data-s9e-livepreview-onupdate')) { window.hljsLoader.highlightBlocks(document.currentScript.parentNode); } i've tried to add the host to /etc/hosts 198.143.164.251 api.wordpress.org also tried to add all the ip ranges to jetpack 122.248.245.244/32 54.217.201.243/32 54.232.116.4/32 192.0.80.0/20 192.0.96.0/20 192.0.112.0/20 195.234.108.0/22 https://www.ipaddressguide.com/cidr if(window.hljsLoader && !document.currentScript.parentNode.hasAttribute('data-s9e-livepreview-onupdate')) { window.hljsLoader.highlightBlocks(document.currentScript.parentNode); } tied to add rules to sysfirewall and WAF, but no luck also added rules to the firewall using ssh [root@cp ~]# firewall-cmd --zone=public --add-service=http success [root@cp ~]# firewall-cmd --zone=public --add-service=https success [root@cp ~]# firewall-cmd --zone=public --permanent --add-service=http success [root@cp ~]# firewall-cmd --zone=public --permanent --add-service=https success [root@cp ~]# firewall-cmd --reload success [root@cp ~]# firewall-cmd --list-all public (active) if(window.hljsLoader && !document.currentScript.parentNode.hasAttribute('data-s9e-livepreview-onupdate')) { window.hljsLoader.highlightBlocks(document.currentScript.parentNode); } This is killing me, I need your help and support please, we are using heavily WordPress, and I think this is one of the restrictions of aaPanel. Wating for the reply Regards

Wordpress Killing connectivity error, outbound error

greenbackend

Hello, aaPanelers

I think its a general aaPanel issue, i am using System :CentOS 8.2.2004(Py3.7.8) with nginx and php7.4
I've tried to add firewall IPs, URLs, rules but with no luck, WordPress can't access the WordPress outbound address,

also tried to add

define('WP_HTTP_BLOCK_EXTERNAL', false);

to the wp-config.php but without any luck

I've tried using ssh to check the system ports and the 80,443 are opened,

url -v telnet://api.wordpress.org 443
* Rebuilt URL to: telnet://api.wordpress.org/
*   Trying 198.143.164.251...
* TCP_NODELAY set
^C

i keep getting messages like:

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

Communicating with the WordPress servers is used to check for new versions, and to both install and update WordPress core, themes or plugins.

Error Your site is unable to reach WordPress.org at 198.143.164.251, and returned the error: cURL error 60: SSL: no alternative certificate subject name matches target hostname 'api.wordpress.org'

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

i've tried to add the host to /etc/hosts
198.143.164.251 api.wordpress.org

also tried to add all the ip ranges to jetpack

122.248.245.244/32
54.217.201.243/32
54.232.116.4/32
192.0.80.0/20
192.0.96.0/20
192.0.112.0/20
195.234.108.0/22

https://www.ipaddressguide.com/cidr

tied to add rules to sysfirewall and WAF, but no luck
also added rules to the firewall using ssh

[root@cp ~]# firewall-cmd --zone=public --add-service=http
success
[root@cp ~]#  firewall-cmd --zone=public --add-service=https
success
[root@cp ~]# firewall-cmd --zone=public --permanent --add-service=http
success
[root@cp ~]# firewall-cmd --zone=public --permanent --add-service=https
success
[root@cp ~]# firewall-cmd --reload
success
[root@cp ~]#  firewall-cmd --list-all
public (active)

This is killing me, I need your help and support please, we are using heavily WordPress, and I think this is one of the restrictions of aaPanel.

Wating for the reply

Regards

greenbackend

@aaPanel_Jose any updates my friend?

greenbackend

try open this page after installing wordpress /wp-admin/plugin-install.php
you will see the error

aaPanel_Jose

greenbackend
Thank you for your feedback, we have paid attention to this issue and will try our best

greenbackend

aaPanel_Jose any updates? we can show you this issue via team viewer? anydisk? or send you the vps details and aapanel

greenbackend

ok, just let me know if there is any update to this issue

greenbackend

tried with CentOS 7.9.2009(Py3.7.8)　
and got the same error

aaPanel_Jose

greenbackend
Sorry because of the busy schedule recently, we will arrange the test as soon as possible

Stealth

aaPanel_Jose
Yes, this is cURL problem again, like we say for Jose:
https://prnt.sc/w3jf9r

greenbackend

ok please, let me know

greenbackend

send you a brand server, you could test the settings on it and install wordpress

greenbackend

Stealth this problem is strange, its been a month and no one could solve it
https://example.com/wp-admin/plugin-install.php

greenbackend

for example once i open this page
https://example.com/wp-admin/plugin-install.php
i got the following error
https://api.wordpress.org/plugins/info/1.2/
?action=query_plugins
&request%5Bpage%5D=1
&request%5Bper_page%5D=36
&request%5Blocale%5D=ar
&request%5Bbrowse%5D=featured
&request%5Bwp_version%5D=5.5

404 Not Found

greenbackend

does the curl used by wordpress different from the curl in command line?

[root@cp ~]# curl -v http://api.wordpress.org/core/version-check/1.7/

Trying 198.143.164.251...
TCP_NODELAY set
Connected to api.wordpress.org (198.143.164.251) port 80 (#0)

GET /core/version-check/1.7/ HTTP/1.1
Host: api.wordpress.org
User-Agent: curl/7.61.1
Accept: /

< HTTP/1.1 200 OK
< Server: nginx
< Date: Mon, 21 Dec 2020 14:44:02 GMT
< Content-Type: application/json; charset=UTF-8
< Transfer-Encoding: chunked
< Connection: keep-alive
< Vary: Accept-Encoding
< X-Update-Channel: stable
< Access-Control-Allow-Origin: *
< X-Frame-Options: SAMEORIGIN
<

Connection #0 to host api.wordpress.org left intact
{"offers":[{"response":"upgrade","download":"http:\/\/downloads.wordpress.org\/release\/wordpress-5.6.zip","locale":"en_US","packages":{"full":"http:\/\/downloads.wordpress.org\/release\/wordpress-5.6.zip","no_content":"http:\/\/downloads.wordpress.org\/release\/wordpress-5.6-no-content.zip","new_bundled":"http:\/\/downloads.wordpress.org\/release\/wordpress-5.6-new-bundled.zip","partial":false,"rollback":false},"current":"5.6","version":"5.6","php_version":"5.6.20","mysql_version":"5.0","new_bundled":"5.6","partial_version":false}],"translations":[]}

[root@cp ~]# php -r "echo file_get_contents('http://api.wordpress.org/core/version-check/1.7/');"
{"offers":[{"response":"upgrade","download":"http:\/\/downloads.wordpress.org\/release\/wordpress-5.6.zip","locale":"en_US","packages":{"full":"http:\/\/downloads.wordpress.org\/release\/wordpress-5.6.zip","no_content":"http:\/\/downloads.wordpress.org\/release\/wordpress-5.6-no-content.zip","new_bundled":"http:\/\/downloads.wordpress.org\/release\/wordpress-5.6-new-bundled.zip","partial":false,"rollback":false},"current":"5.6","version":"5.6","php_version":"5.6.20","mysql_version":"5.0","new_bundled":"5.6","partial_version":false}],"translations":[]}[root@cp ~]#

aaP_pufei889

It took me a considerable amount of time to identify the root cause of the issue and resolve it. Despite seeking assistance from some of the most advanced AI systems worldwide, I was unable to find a solution. Below is the correct resolution method:
The path to the DNS configuration file in Linux is /etc/resolv.conf. Add two lines to it.
nameserver 8.8.8.8 nameserver 8.8.4.4