• 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.

Issue Plesk operations with cURL fail

Chris Dempsey

New Pleskian
Plesk Backup Manager is configured to store backups on Amazon S3 and successfully ran daily since the server was created around 2 weeks ago.

Environment details

Plesk Obsidian v18.0.32_build20201221.13 os_Windows 2012/2016/2019
Microsoft Windows 10.0;build-14393;sp0.0;suite272;product3

On login Plesk showed error alerts

Code:
Unable to create remote backup, the local backup will be created. Error: Unable to export backup: Transport error: Extension transport: ext://s3-backup/server/: Error executing "PutObject" on "https://mybucket.s3.us-west-2.amazonaws.com/backups/plesk/system/"; AWS HTTP error: cURL error 6: Could not resolve host: mybucket.s3.us-west-2.amazonaws.com (see http://curl.haxx.se/libcurl/c/libcurl-errors.html)

On viewing Backup Manager the following error alerts are shown

Code:
Warning: Could not display the list of backups in the Amazon S3 Backup storage: Unable to get dumps list: Transport error: Extension transport: ext://s3-backup/server: Error executing "ListObjects" on "https://mybucket.s3.us-west-2.amazonaws.com/?prefix=backups%2Fplesk%2Fsystem%2F&delimiter=%2F&encoding-type=url"; AWS HTTP error: cURL error 6: Could not resolve host: mybucket.s3.us-west-2.amazonaws.com (see http://curl.haxx.se/libcurl/c/libcurl-errors.html). Please check the storage settings.

Code:
Warning: Unable to upload a file to the storage: Error executing "CreateMultipartUpload" on "https://mybucket.s3.us-west-2.amazonaws.com/backups/plesk/system/test-0f818b6a1aa414175c58e2e07d42db8f?uploads"; AWS HTTP error: cURL error 6: Could not resolve host: mybucket.s3.us-west-2.amazonaws.com (see http://curl.haxx.se/libcurl/c/libcurl-errors.html). Make sure you have granted the permission for multipart upload of files.

I notice the host Plesk looks for is: mybucket.s3.us-west-2.amazonaws.com however my bucket is stored in eu-west-2. I am not sure this matters though as I can connect to the bucket with the Key and Secret in FileZilla without specifying the region.

Updating the Remote Storage Settings with the same Key and Secret returns error

Code:
Error: Error executing "HeadObject" on "https://ds-skye.s3.us-west-2.amazonaws.com/backups/plesk/system/"; AWS HTTP error: cURL error 6: Could not resolve host: mybucket.s3.us-west-2.amazonaws.com (see http://curl.haxx.se/libcurl/c/libcurl-errors.html)

The Plesk Dashborard Home page reports another error

Code:
Error: Failed to update the ModSecurity rule set.

To further test cURL from Plesk I updated a Let's Encrypt Certificate, this returned error

Code:
Error: Could not issue a Let's Encrypt SSL/TLS certificate for mydomain.co.uk.


    Failed to connect to the Let's Encrypt server https://acme-v02.api.letsencrypt.org.
    Please try again later or report the issue to support.
    Details
    Could not obtain directory: cURL error 6: Could not resolve host: acme-v02.api.letsencrypt.org (see https://curl.haxx.se/libcurl/c/libcurl-errors.html)

So this looks very much like Plesk cURL is broken or misconfigured.

Next I created a simple php script to test cURL. It fails to fetch content from a text file on a remote server but successfully fetches content from a local domain (the hosts file maps the domain to the local server IP).

Can anyone suggest what the cause might be or how I can investigate further?

There is a similar error linked below but this doesn't help as it's related to Plesk Linux

Thanks,

Chris
 
It looks like your server does not resolve external domain names correctly. Have you checked that the name servers entered in /etc/resolv.conf can be reached? Have you tried to do a manual name resolution like
# dig acme-v02.api.letsencrypt.org +short
# nslookup acme-v02.api.letsencrypt.org
# ping acme-v02.api.letsencrypt.org
 
It's a Windows machine so I don't have DIG but you are correct.

I can reach
Code:
https://ds-skye.s3.us-west-2.amazonaws.com/backups/plesk/system/
from my local machine in the browser but not in a browser on the server over RDP.

It seems
Code:
Windows can't communicate with the device or resource (primary DNS server)
.

I have referred this back to Engineers at the data centre, I'm unsure how to resolve myself.

Thanks Peter
 
Turns out it was a network configuration error.

Unsure what caused it as the machine was stable in that sense since it was built two weeks ago until today.
 
Back
Top