• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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 cURL issue with Wordpress after Centos 7.5 upgrade

Brujo

Silver Pleskian
Plesk Guru
‪CentOS Linux 7.5.1804 (Core)‬
Product Plesk Onyx Version 17.8.11 Update #7

Well since I upgrade one of the testserver to Centos 7.5 I face several curl errors within wordpress like Plugin Installation, updates of several Plugins like wordfence, AIO Event Calender and so on....
most of them produce now an error like
Code:
cURL error 6: Could not resolve host: xyz.com; Name or service not known

I do not have seen yet the Curl error 77 like in this thread Issue - cURL error 77 Updating WordPress plugins & Unable to update Wordpress plugins: Download failed. cURL error 77

and I restarted psa service as Peter mentioned here Input - Plesk 17, 17.5, 17.8 on CentOS 7.5 --> Yes, it works.

Update: might help others too...
after switching on the Wordpress Domain the php version from 7.2.x > 7.1.x the issue is gone and switched back to 7.2.x and still no issue
 
Last edited:
Back
Top