• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Forwarded to devs Issue with scheduled tasks [UserAgent]

Azurel

Silver Pleskian
User name: Azurel

TITLE

Issue with scheduled tasks [UserAgent]

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

All

PROBLEM DESCRIPTION

Today I noticed all my scheduled tasks (plesk) not working.

In /var/log/cron there was no issue. So I run a task in plesk GUI with "run now"-button and get a error, because page request was http-status-code 403.

I block %{HTTP_USER_AGENT} with "curl", because this is used as crawler. Plesk Scheduled Tasks use "curl" as UserAgent too. My Solution was to add server IPv4 and IPv6 as exception for %{REMOTE_ADDR}.

Maybe, you change the UserAgent in something like "plesk-scheduled-tasks-request"?

There are many ready-made bot lists, which also contain "curl" and you don't notice for days or longer that Scheduled Tasks don't work at all. ;)

STEPS TO REPRODUCE

Add
RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} ^curl [NC]
RewriteRule .* - [F]

and start a scheduled tasks in plesk with "run now".

ACTUAL RESULT

Response 403

EXPECTED RESULT

No error

ANY ADDITIONAL INFORMATION

Workaround (add server IPv4 and IPv6 as exception)

RewriteCond %{HTTP_USER_AGENT} ^(curl|XenForo|WordPress) [NC]
RewriteCond %{REMOTE_ADDR} !^123\.1\.2\.3$
RewriteCond %{REMOTE_ADDR} !^2a01:999:999:9999::2$
RewriteRule .* - [F]

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
Last edited:
From developer:

Although I cannot classify this issue as a product bug, the problem is clear. I create PPPM-12363 to address this problem.
 
Back
Top