• 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
  • Please beaware of a breaking change in the REST API on the next Plesk release (18.0.62).
    Starting from Plesk Obsidian 18.0.62, requests to REST API containing the Content-Type header with a media-type directive other than “application/json” will result in the HTTP “415 Unsupported Media Type” client error response code. Read more here

Resolved Protocol https not supported or disabled in libcurl

jorge ceballos

Regular Pleskian
Hi everybody,

Some days ago migrated from my old up to date EC2 instance to a new one due to be running out of space.
Used migration tool to do this which worked great.
The new instance is -supposedly - identical to the old one except by the HD size; it is up to date, have Atomic's ASL and WP toolkit.

Yesterday while updating one of my own sites and trying to install a new WP Plugin, came across a Warning sign stating "there's an unexpected mistake and there may be something wrong with wordpress.org or this server" - mine is in Spanish, so I don't really know how it shows in English.
Searched a bit further and in joomla sites, while trying to update other plugins it states "Protocol https not supported or disabled in libcurl".

Tried everything I could think of, including uninstalling ASL completely to no avail (although it always worked fine in the old instance) .

BTW Let's Encrypt works fine and new WP instances are created without a glitch but new plugins cannot be installed online - only through upload

My server:
SO ‪CentOS Linux 7.5.1804 (Core)‬
Producto Plesk Onyx Versión 17.8.11 Actualización #15

PHP 7.2.8

Some insights of the installed curl in the server:

curl --version | grep Protocols
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtsp scp sftp smtp smtps telnet tftp

which curl
/bin/curl

Any idea?
Please advice

Edit:
Updated Curl:

#curl --version
curl 7.61.0 (x86_64-redhat-linux-gnu) libcurl/7.61.0 NSS/3.36 zlib/1.2.7 libpsl/0.7.0 (+libicu/50.1.2) libssh2/1.8.0 nghttp2/1.31.1
Release-Date: 2018-07-11
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtsp scp sftp smb smbs smtp smtps telnet tftp
Features: AsynchDNS IPv6 Largefile GSS-API Kerberos SPNEGO NTLM NTLM_WB SSL libz HTTP2 UnixSockets HTTPS-proxy PSL Metalink

Still not connecting:

curl -vvv api.wordpress.org
* Rebuilt URL to: api.wordpress.org/
* Trying 66.155.40.202...
* TCP_NODELAY set
* connect to 66.155.40.202 port 80 failed: Connection timed out
* Failed to connect to api.wordpress.org port 80: Connection timed out
* Closing connection 0
curl: (7) Failed to connect to api.wordpress.org port 80: Connection timed out
 
Last edited:
Hi,

api.wordpress.org resolves to 198.143.164.251
Somehow your name resolution points to the wrong ip. Check your hosts file. Maybe your old system had it routed differently.

Cheers,
Tom
 
Last edited:
WOW ! Amazing, that solved it.
Thanks Tom !!

Added api.wordpress.org (with the right IP) to /etc/hosts and immediately resolved to the right site and wordpress' add plugins worked fine,
Cleaned /etc/hosts file and the server keeps resolving to the right address and everything is back to normal.
Weird but true.

Thanks again

Jorge
 
i have

mail:~# curl --version
curl 7.29.0 (x86_64-redhat-linux-gnu) libcurl/7.29.0 NSS/3.34 zlib/1.2.7 libidn/1.28 libssh2/1.4.3
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtsp scp sftp smtp smtps telnet tftp

Protocol https not supported or disabled in libcurl

if i start a planed task...

Plesk 17.8.30
 
Back
Top