- Plesk Onyx for Windows
Note: This article has the reference to the issue with the fix available:
- #PPPM-8984 "Plesk Scheduler fetch URL not working properly after disabled TLS 1.0 (as PPP-37655)"
- Plesk Obsidian Release Candidate 1.0 04 June 2019
TLS 1.0 is disabled on a Plesk for Windows server.
According to SSL Server Test, the domain example.com has a valid certificate and only TLS 1.2 or above are supported.
A scheduled task of the type "Fetch a URL" created in Subscriptions > example.com > Scheduled Tasks fails to run with the following error:
PLESK_ERROR: Exception calling "GetResponse" with "0" argument(s): "The underlying connection was closed: An unexpected error occurred on a receive"
PLESK_ERROR: WARNING: Unable to fetch url: https://example.com
WARNING: Exception calling "GetResponse" with "0" argument(s): "The request was aborted: Could not create SSL/TLS secure channel."
Plesk bug PPPM-8984 which is planned to be fixed in one of the future Plesk updates.
Until the bug is fixed, the following workaround can be used:
Note: This solution is intended for use by server administrators. In case there is no administrative RDP access to the server, contact the server administrator or server provider.