How to Set Up a PHP Scheduled Task in Plesk

Plesk scheduled tasks

Use Plesk Scheduled Tasks to run a PHP script, fetch a URL or execute an advanced command automatically

Choose the safest task type for the job. Run a PHP script when the file is in your hosting space, Fetch a URL when the application provides a protected web endpoint, and use Run a command only when its documentation requires one. Test once with Run Now before trusting the schedule.

TYPEPHP, URL or commandMatch the application
TESTRun Now firstCatch errors early
WATCHControl frequencyAvoid overlapping runs

Which scheduled-task type should I choose?

TypeUse it forYou provide
Run a PHP scriptA PHP maintenance, import or application task stored in the subscriptionThe script path and PHP version or handler offered by Plesk
Fetch a URLA documented web endpoint designed to be called on a scheduleThe complete HTTPS URL, ideally protected against public abuse
Run a commandAn application command that genuinely requires shell executionThe full executable path and correctly quoted arguments

How do I create the task?

  1. 1
    Open Scheduled Tasks

    Open Plesk from your hosting service, select the appropriate domain or subscription and open Scheduled Tasks.

  2. 2
    Choose Add Task

    Select PHP script, URL or command based on the application instructions. Do not translate one type into another without a reason.

  3. 3
    Set timing and notifications

    Choose a realistic interval and an email notification option. Avoid running a long task again before its earlier run can finish.

  4. 4
    Use Run Now

    Save, run a single test and examine the result. Confirm the intended database, file or application change occurred.

Make scheduled work predictable

Use full paths

A scheduled task may not have the same working directory or environment as a script you run manually.

Protect secrets

Do not place passwords or API keys directly in a command where they may appear in logs or account screens.

Log useful output

Record completion time and errors without writing customer data or credentials into a public file.

Start less frequently

Test with a conservative schedule. Increase frequency only when the task finishes reliably and the application needs it.

Scheduled-task questions

What time zone does the schedule use?

It normally uses the server time zone shown by Plesk. Check the scheduled-task screen when an exact local time matters.

Why does the task work in my browser but fail on schedule?

The scheduled environment may use a different PHP version, path, user context or working directory. Compare those details and review its error output.

How often should a task run?

Follow the application’s documentation. More frequent is not automatically better and can cause overlaps or unnecessary load.

Automate safely

Create the task, run it once and confirm the result

A successful Run Now test and useful error notifications are more important than an aggressive schedule.

How to Upload a Website with FileZilla FTP

Upload a website with FileZilla

Connect FileZilla to your assigned UKC hosting server, then upload the website into the domain’s httpdocs folder

Use the FTP username and password shown under Plesk Web Hosting Access, not your Client Area password. Prefer explicit FTP over TLS when offered, keep passive mode enabled and confirm you are working inside the correct domain before replacing files.

REMOTE FOLDERhttpdocsPublic website files go here
CREDENTIALSPlesk system userNot your account login
SECURITYUse TLSAvoid unencrypted FTP where possible

What do you need before uploading?

Hosting server

Use the assigned server shown in the hosting welcome email or Client Area, such as ukc10.uk, ukc11.uk, ukc12.uk or ukc13.uk.

FTP system user

In Plesk open Websites & Domains, Hosting & DNS, then Hosting or Web Hosting Access to view or reset it.

A local website copy

Know which folder on your computer contains the home page and all required images, stylesheets and scripts.

A backup

Back up the current remote files before overwriting a working site. Keep the copy outside httpdocs.

How do you connect and upload with FileZilla?

  1. 1
    Install the official FileZilla Client

    Download the client from the FileZilla Project. Do not install an unrelated copy from an advert or download portal.

  2. 2
    Create a Site Manager entry

    Enter the assigned server as Host, choose FTP with explicit TLS when available, and use Normal logon.

  3. 3
    Enter the Plesk FTP login

    Use the system user and its password. Port 21 is the usual FTP and explicit-TLS port.

  4. 4
    Open httpdocs

    After connecting, use the remote pane to open the correct domain’s httpdocs folder.

  5. 5
    Upload the complete site

    Drag the website files from the local pane to the remote pane. Keep folders and file names intact.

  6. 6
    Check failed transfers

    Open FileZilla’s failed and queued transfer tabs and retry only after correcting the cause.

What should you test after uploading?

Home page file

Make sure httpdocs contains the intended index file and no unwanted default index page takes priority.

HTTPS and links

Open the site securely, follow important links and check that images and styles load.

Case-sensitive names

Linux treats Image.jpg and image.jpg as different files. Correct the HTML or file name when an asset is missing.

Application requirements

A PHP or database-driven site can need a database import, configuration file and suitable PHP settings in addition to files.

Common FileZilla problems

Why do I see 530 Login incorrect?

The FTP username or password is wrong. Re-enter the Plesk system user, remove copied spaces and reset only the FTP password if needed.

Why can FileZilla not find the server?

Check the assigned hostname and local internet connection. Use the exact UKC server name rather than an old example from another account.

Why is the old website still visible?

Confirm you uploaded into the correct httpdocs folder, replaced the active index file and are viewing the correct domain over HTTPS. Browser or CDN caching can also delay what you see.

Can I upload without FileZilla?

Yes. Plesk File Manager can upload files or directories through the browser and is often simpler for a small update.

Ready to publish?

Open Plesk and confirm the credentials for the correct website

If the connection fails, send support the domain, server and exact FileZilla error, but never the password.

Plesk – Unable to stat entry ‘/usr/local/psa/handlers/info/’

Re: Mail being bounced even though Mailbox exists, bounce message

Hi. This is the qmail-send program at server.mailserver.com.
I’m afraid I wasn’t able to deliver your message to the following addresses.
This is a permanent error; I’ve given up. Sorry it didn’t work out.”

Take a look in the mail log file:

tail -1500 /usr/local/psa/var/log/maillog

You see errors such as this:

Unable to stat entry '/usr/local/psa/handlers/info'

To resolve you need to remove and rebuil all mail handlers as follows:

1. Stop the mail service

    # /usr/local/psa/admin/sbin/mailmng --stop-service

    OR

    # service qmail stop

2. Backup old handlers in a temporary directory

    # mkdir /usr/local/temp

    # cp -a /usr/local/psa/handlers/before-* /usr/local/temp/

    # cp -a /usr/local/psa/handlers/info /usr/local/temp/

3. Remove the handlers

    # rm -rf /usr/local/psa/handlers/before-*/*

    # rm -rf /usr/local/psa/handlers/info/*

4. Recreate handlers using mchk utility

    # /usr/local/psa/admin/sbin/mchk --with-spam

5. Start mail service:

    # /usr/local/psa/admin/sbin/mailmng --start-service

    OR 

    service qmail start

This may take a little time however it will resolve all errors.

How to Block or Control YandexBot Crawling

Control YandexBot crawling

Use robots.txt first, then a server block only for abusive traffic

Yandex officially supports robots.txt and offers crawl-rate controls in Yandex Webmaster. Add a Yandex rule to a valid root-level robots.txt file and test it. A web-server block is stronger, but it also blocks legitimate access and can be bypassed by software that copies the Yandex user-agent name.

FIRSTUse robots.txtOfficial crawl instruction
VERIFYCheck server logsConfirm the real problem
STRONG BLOCKUse only if necessaryUser agents can be spoofed

How do you know YandexBot is causing the load?

Review access logs

Compare request rate, paths, status codes and user-agent with the period of high resource use.

Find expensive URLs

Search, calendar, filter and parameter pages can create much more work than ordinary articles.

Separate bots from attacks

A user-agent string is not proof of identity. Malicious software can claim to be YandexBot.

Fix the bottleneck

Caching, database queries and unlimited URL combinations may need work even if one crawler exposes them.

How do you block Yandex in robots.txt?

Add this group to the plain-text robots.txt file at the website root:

User-agent: Yandex
Disallow: /

Confirm the public file returns HTTP 200 and plain text. Preserve existing sitemap and crawler rules. Yandex says a valid file can restrict crawling and reduce server load.

  1. 1
    Back up the current file

    Preserve all existing directives and sitemap locations before editing.

  2. 2
    Add the Yandex group

    Use the exact user-agent and disallow lines shown above.

  3. 3
    Test the response

    Open the file without signing in and validate it in Yandex Webmaster where available.

  4. 4
    Monitor requests

    Allow time for the crawler to refetch the file, then compare logs and load.

When should you block at the server?

Use a server block when traffic remains harmful, is impersonating a crawler or must stop immediately. The correct method depends on active Apache and Nginx configuration. A copied legacy Order Deny,Allow snippet may not suit a modern server.

How do you reverse the change?

robots.txt rule

Remove only the Yandex group and confirm the rest of the file still returns HTTP 200.

Server block

Restore the backup, test the site immediately and clear relevant caches.

Search visibility

Allowing crawl again does not guarantee immediate recrawling or indexing.

Long-term control

Block infinite URL spaces and fix expensive pages instead of blocking every crawler that finds them.

Read Yandex’s official robots.txt guidance.

YandexBot questions

Does Yandex ignore robots.txt?

Yandex states that its indexing robot supports robots.txt. A missing, inaccessible or invalid file may be treated as allowing crawl.

Will Disallow remove pages from search?

Not necessarily. Blocking crawl and removing an indexed URL are separate tasks.

Can I block by IP address?

Ranges can change and need verification. Do not maintain an unverified copied list.

Why is the old Apache rule gone?

It used legacy syntax and an imprecise pattern. Modern configurations need a rule suited to the actual server.

Still seeing heavy crawling?

Send UKC the time window and hostname

Include sample log lines with customer information removed.

What is a dedicated server?

If your site becomes too busy for shared hosting or VPS, you may need your own dedicated server.

A dedicated server is a server whose resources are entirely dedicated to your site. None of the server resources are shared with any third parties.

Usually the maintenance of a dedicated server is your responsibility however some hosts offer managed dedicated server solutions – at a price.

You will need a dedicated server if your site becomes very busy and the resource requirements are greater than that provided by a shared hosting service.