• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved PHP-FPM CURL and HTTPS = Cannot resolve host

Matt_Hill

New Pleskian
After a few hours CURL doesn't seem to be able to resolve URL's to HTTPS hosts.

Currently using PHP-FPM 5.5.38 and 7.0.17 on different websites, both with the same issue.

  • The site on PHP 5.5.38 is Magento based and can't resolve live.sagepay.com to process payments
  • The site on PHP 7.0.17 is Wordpress based and it can't resolve to update plugins.

When CURL can't resolve the hostname I can do via the terminal over SSH perfectly fine however.

If i reboot the server everything seems fine for the next 12+ hours.

What makes me think it might not be just a Plesk issue is various replies here: http://stackoverflow.com/questions/1341644/curl-and-https-cannot-resolve-host

Some are from people who have started to notice the same thing today / yesterday, however have previously had no issues / config changes for months, like myself.

I've added the following to my PHP configuration: curl_setopt($_h, CURLOPT_IPRESOLVE, CURL_IPRESOLVE_V4 );

This has apparently resolved the issue for some, however too early to confirm if this has worked for myself. The server doesn't have any, IPV6 address, just multiple IPV4 addresses.

I thought it might be worth posting about to see if anyone else has had the same issue in the last day or two

OS: ‪Ubuntu 16.04.2 LTS
Plesk: Onyx 17.0.17 Update #20
 
Hey,

we do have exactly the same error since today/yesterday.


OS: ‪Ubuntu 14.04.5 LTS
Plesk: Onyx 17.0.17 Update #20
 
can't resolve live.sagepay.com to process payments
Try to strace it with something like

# strace -o /tmp/curlissue -fF curl -v live.sagepay.com

and try to find something useful in /tmp/curlissue
Maybe there are some problems with opening libraries from /lib64/, SELinux, specific /root/.curlrc, /etc/nsswitch.conf or something else.
 
This is a (temporary) Ubuntu bug... pls. see as well: => https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1674776

( pls. wait for another security update for "libc-bin" and "libc6", which you should get with the manual command "aptitude upgrade" - On Ubuntu 16.04, the issue is already solved with new ( and old ) security updates. At the moment, I can't confirm it for Ubuntu 14.04, due to a missing test - server with this OS )
 
Last edited by a moderator:
Back
Top