Issue ERROR: Zend_Http_Client_Adapter_Exception: Unable to Connect to ssl://hub.docker.com:443. Error #110: Connection timed out (Socket.php:235)

[hostingprimus]

Server operating system version

AlmaLinux 8.7

Plesk version and microupdate number

18.0.51

Fellow Pleskians,

I've recently updated Plesk from 18.0.50 #2 to 18.0.51 and now my Docker Extension acts kind of weird.
I'm still able to search for Images and I'm also able to download and start them, also my local images are working finde. But I'm not able to search for new images by clicking on the dropdown next to my local running image.
I'm getting a bis gat red "ERROR: Zend_Http_Client_Adapter_Exception: Unable to Connect to ssl://hub.docker.com:443. Error #110: Connection timed out (Socket.php:235)"
I did not update or manually deploy OpenSSL, I've stopped iptables, Plesk Firewall. The result is still Error.

OS: AlmaLinux 8

# traceroute -T -p 443 hub.docker.com (Shows that connection isn't blocked or something)
[...]
23 * ec2-54-165-156-197.compute-1.amazonaws.com (54.165.156.197) 111.265 ms *
24 ec2-54-165-156-197.compute-1.amazonaws.com (54.165.156.197) 110.538 ms * 110.546 ms
25 ec2-54-165-156-197.compute-1.amazonaws.com (54.165.156.197) 110.593 ms 111.824 ms 111.932 ms

# curl -v Docker (also perfectly fine)
* Rebuilt URL to: Docker
* Trying 2600:1f18:2148:bc00:a66d:e75:e647:fefc...
* TCP_NODELAY set
* Trying 54.165.156.197...
* TCP_NODELAY set
* Connected to hub.docker.com (54.165.156.197) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
* TLSv1.3 (OUT), TLS handshake, Client hello (1):

Do some of you encounter the same issue? Did you find a workaround or is it maybe an issue for Plesk?

#

 

[kiubo]

having the exact same issue ... I can not use the admin interface anymore. I have to get new images through docker pull ... have you solved it yet?

 

[Peter Debik]

What's the output of

# iptables --table nat --list
# uname -a

?

 

[kiubo]

# iptables --table nat --list

Chain PREROUTING (policy ACCEPT)

target     prot opt source               destination

DOCKER     all  --  anywhere             anywhere             ADDRTYPE match dst-type LOCAL


Chain INPUT (policy ACCEPT)

target     prot opt source               destination


Chain OUTPUT (policy ACCEPT)

target     prot opt source               destination

DOCKER     all  --  anywhere            !localhost/8          ADDRTYPE match dst-type LOCAL


Chain POSTROUTING (policy ACCEPT)

target     prot opt source               destination

MASQUERADE  all  --  172.17.0.0/16        anywhere

MASQUERADE  tcp  --  172.17.0.3           172.17.0.3           tcp dpt:9300

MASQUERADE  tcp  --  172.17.0.3           172.17.0.3           tcp dpt:9200

MASQUERADE  tcp  --  172.17.0.5           172.17.0.5           tcp dpt:9300

MASQUERADE  tcp  --  172.17.0.5           172.17.0.5           tcp dpt:9200

MASQUERADE  tcp  --  172.17.0.6           172.17.0.6           tcp dpt:9300

MASQUERADE  tcp  --  172.17.0.6           172.17.0.6           tcp dpt:9200


Chain DOCKER (2 references)

target     prot opt source               destination

RETURN     all  --  anywhere             anywhere

DNAT       tcp  --  anywhere             anywhere             tcp dpt:49177 to:172.17.0.3:9300

DNAT       tcp  --  anywhere             anywhere             tcp dpt:49178 to:172.17.0.3:9200

DNAT       tcp  --  anywhere             anywhere             tcp dpt:32774 to:172.17.0.5:9300

DNAT       tcp  --  anywhere             anywhere             tcp dpt:32775 to:172.17.0.5:9200

DNAT       tcp  --  anywhere             anywhere             tcp dpt:32776 to:172.17.0.6:9300

DNAT       tcp  --  anywhere             anywhere             tcp dpt:32777 to:172.17.0.6:9200

and

#  uname -a
Linux host.100websites.ch 5.4.0-90-generic #101-Ubuntu SMP Fri Oct 15 20:00:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

 

[Peter Debik]

Thank you for your fast reply. Unfortunately all seems to be o.k. We'll need to check the issue directly on your server. I am not a Docker expert, but support engineers will for sure figure out what is going on. Unless another user knows what the issue is, that will be best:

To sign-in to support please go to https://support.plesk.com

If you experience login issues, please see this KB article:
https://support.plesk.com/hc/en-us/...rt-plesk-com-and-password-reset-does-not-work

If you bought your license from a reseller, your reseller should provide support for you. If the reseller does not provide support, here is an alternative:
https://support.plesk.com/hc/en-us/articles/12388090147095-How-to-get-support-directly-from-Plesk-

 

[andyxyz]

Same issues here

Docker Catalog at Localhost​

ERROR: Zend_Http_Client_Adapter_Exception: Unable to Connect to ssl://hub.docker.com:443. Error #0: (Socket.php:235)
Search for related Knowledge Base articles

 

[lelan29183]

It has not yet been resolved.

 

[Peter Debik]

Thank you for reporting that it has not been resolved. Could you please open a support ticket as described above?

 

[clgriffin]

I have the same problem. Is there a solution for it?

 

[mow]

# curl -v Docker (also perfectly fine)
* Rebuilt URL to: Docker
* Trying 2600:1f18:2148:bc00:a66d:e75:e647:fefc...
* TCP_NODELAY set
* Trying 54.165.156.197...
* TCP_NODELAY set

Looks like a problem with IPv6.

 

[Anthony]

I can confirm this issue as a bug ID #EXTDOCKER-198. We plan to fix it soon and bring more improvements to the Docker extension.
If you have any ideas/issues, please let me know.