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

Question Scheduler giving error - WARNING: Unable to fetch url:(API URL) WARNING: Exception calling "GetResponse" with "0" argument(s): "The remote server ret

naimisar

New Pleskian
Server operating system version
Microsoft Windows Server 2022
Plesk version and microupdate number
Plesk Obsidian 18.0.65 Update #2
Hi Team,
I am getting following error while my scheduler run. Same setup was working fine previously but now giving error.

WARNING: Unable to fetch url: (API URL)
WARNING: Exception calling "GetResponse" with "0" argument(s): "The remote server returned an error: (500) Internal

API working fine while i am execute individual.

Thanks and regards,
naimisar
 
Hello, @naimisar. What you can try is increasing the execution time by navigating to the %plesk_dir%Additional\Scheduler folder and opening fetch_url.ps1. Add webRequest.timeout variable with value of 60000 in the Try block to the script:

...
Try {
[System.Net.ServicePointManager]::ServerCertificateValidationCallback = {$true}
$webRequest = [net.WebRequest]::Create($url)
$webRequest.timeout = 60000;
...

I hope that helps.
 
Back
Top