Websites & Applications

How to Install WordPress Using WP Toolkit in Plesk

Plesk includes WP Toolkit, a powerful tool that lets you install, manage, and secure WordPress websites with just a few clicks. This guide covers installing WordPress on your domain using WP Toolkit. Installing WordPress (Quick Install) 1. Log in to Plesk. 2. Go to WordPress in the left navigation menu. 3. If you already have a domain added, click Install. 4. WP Toolkit will install the latest version of WordPress with default settings: - Your Plesk login credentials will be used as the WordPress admin credentials. - The database will be created automatically. - SSL will be enabled if available.- Click Install to proceed. - The installation will complete in a few seconds. Click Log in on the installation card to access your WordPress dashboard. Installing WordPress (Custom Install) For more control over the installation: 1. Go to WordPress. 2. Click Install (Custom). 3. Configure the following settings: - Domain: Select the domain where WordPress will be installed. - Installation path: Leave as root (/) or specify a subdirectory (e.g., /blog). - WordPress version: Choose a specific version or use the latest. - Site title: The name of your website. - Admin username: Your WordPress admin username. - Admin password: Set a strong password for the WordPress admin. - Admin email: Your email for WordPress notifications. - Database name: Accept the default or enter a custom name. - Autoupdate settings: Choose whether WordPress, plugins, and themes update automatically. 4. Click Install. Registering an Existing WordPress Installation If WordPress was installed manually or before WP Toolkit was available: 1. Go to WordPress. 2. Click Scan. 3. Plesk will find any WordPress installations and add them to WP Toolkit. Important Notes - WP Toolkit is free and included with the Web Host edition of Plesk. - Installing WordPress on a domain that already has files will overwrite existing content in the document root. - You can install multiple WordPress instances on the same domain using different subdirectories. - Always use custom installation if you want to set your own admin username and password. Troubleshooting "WordPress" option is not visible in the menu: - WP Toolkit may not be installed. Contact your hosting provider. Installation fails: - Ensure the domain has sufficient disk space and a working database. - Check that PHP is enabled for the domain. Cannot access WordPress admin after installation: - Use the Log in button on the WordPress installation card in WP Toolkit. - Clear your browser cache and try again. Related Guides - Update & secure it - Clone the site - Set the PHP version

How to Secure WordPress with Plesk WP Toolkit

WP Toolkit makes it easy to keep your WordPress sites up to date and secure. Outdated WordPress installations are a common target for hackers, so regular updates and security hardening are essential. This guide covers updating and securing WordPress through WP Toolkit. Updating WordPress Manually 1. Log in to Plesk. 2. Go to WordPress. 3. If an update is available, you will see a notification next to the installation (e.g., "Install plugin updates", "Update WordPress"). 4. Click the notification to view available updates. 5. Select the updates you want to install. Keep the Restore Point checkbox selected to create a backup before updating. 6. Click Update. 7. Wait for the update to complete. Your site will be briefly unavailable during the process. Configuring Automatic Updates 1. Go to WordPress and click on your WordPress installation. 2. Click Autoupdate settings. 3. Choose your preferences: - Update WordPress automatically: Select "Yes, but only minor (security) updates" for production sites, or "Yes, all" for staging sites. - Update plugins automatically: Select "Defined individually, but security updates are autoinstalled" for the best balance of security and stability. - Update themes automatically: Same recommendation as plugins. 4. Click OK. Securing Your WordPress Installation 1. Go to WordPress. 2. If security issues are detected, you will see a warning message (e.g., "Fix security" or "Check security"). 3. Click the security message. 4. Review the list of available security measures: - Critical measures: Turn off XML-RPC pingbacks, set secure file permissions, prevent directory listing, and more. - Recommended measures: Additional hardening steps for improved security. 5. Select the measures you want to apply. 6. Click Secure. You can also secure multiple installations at once by clicking Security at the top of the WordPress page. Important Notes - Always create a restore point before updating WordPress core. - Security measures applied by WP Toolkit can sometimes affect plugin functionality. If something breaks, use Revert to undo specific measures. - Automatic updates for plugins and themes can be configured individually — go to the Plugins or Themes tab on the installation card. Troubleshooting Website breaks after an update: - Go to WordPress → click Back up / Restore on the installation card. - Restore the backup that was created before the update. Security measures broke a plugin: - Go to WordPress → click the security status message → select the problematic measure → click Revert. Related Guides - Install WordPress first - Set a supported PHP version - Clone before big changes

How to Change PHP Settings in Plesk

Plesk lets you change the PHP version and configuration for each domain individually. This is useful when your website or application requires a specific PHP version, or when you need to adjust settings like memory limit, upload size, or execution time. This guide covers both tasks. Changing the PHP Version for a Domain 1. Log in to Plesk. 2. Go to Websites & Domains. 3. Click the domain name you want to configure. 4. Go to Hosting & DNS → PHP Settings. 5. In the PHP version dropdown, select the desired PHP version (e.g., 8.1, 8.2, 8.3). 6. Click Apply or OK. Common PHP Settings to Adjust On the same PHP Settings page, you can modify configuration directives: - memory_limit: Maximum memory a PHP script can use (e.g., 256M or 512M). Increase if your site shows memory errors. - max_execution_time: Maximum time a PHP script can run (e.g., 300 seconds). Increase for slow operations like large file imports. - upload_max_filesize: Maximum file upload size (e.g., 64M). Increase if you need to upload large files. - post_max_size: Maximum size of POST data (should be larger than upload_max_filesize). - max_input_vars: Maximum number of input variables (increase if forms with many fields are being truncated). - display_errors: Set to Off for production sites to avoid exposing sensitive information. - opcache.enable: Set to On for better PHP performance. - disable_functions: List of disabled PHP functions. Leave empty unless your provider has specific requirements. Changing PHP Settings 1. On the PHP Settings page, find the setting you want to change. 2. Modify the value in the text field. 3. Click Apply to save. Setting a Default PHP Version for All New Domains This option is available to administrators and resellers: 1. Go to Tools & Settings → General Settings (or PHP Settings). 2. Select the default PHP version. 3. Click OK. Important Notes - PHP version changes take effect immediately. If your site shows errors after changing the version, switch back to the previous version. - Some applications (especially older ones) may not be compatible with the latest PHP version. Check compatibility before upgrading. - The available PHP versions depend on what your hosting provider has installed on the server. - PHP settings changes only affect the specific domain, not all domains on the server. Troubleshooting Website shows 500 error after changing PHP version: - Switch back to the previous PHP version immediately. - Check your application compatibility with the new PHP version. Cannot find the PHP version dropdown: - Your hosting provider may restrict PHP version changes. Contact support. Upload size is still too small after changing settings: - Ensure both upload_max_filesize and post_max_size are increased. - Restart the website by toggling PHP handler off and on if changes do not take effect. Related Guides - Change the PHP version - For a WordPress site - Tune it for Laravel

How to Create a Website with Sitejet Builder in Plesk

Sitejet Builder is a free drag-and-drop website builder integrated into Plesk. It lets you create professional, responsive websites without any coding knowledge. You can choose from a library of templates, customize the design, and publish your site directly from Plesk. This guide covers creating and publishing a website with Sitejet Builder. Creating a New Website with Sitejet Builder 1. Log in to Plesk. 2. Go to Websites & Domains. 3. Click Add Domain. 4. Under "Choose a way of creating a website", select Sitejet Builder. 5. Enter your domain name and webspace settings as usual. 6. Click Add Domain. 7. The Sitejet Builder template gallery will open. 8. Browse templates and click on one to preview it, or use the AI Website Generator (if available) to create a site from a brief description. 9. Click Use template to start editing. Editing Your Website Sitejet Builder provides a visual editor where you can: - Add and edit text: Click on any text element to edit the content. - Add images: Drag and drop images from your computer or use the built-in stock photo library. - Add pages: Create new pages from the page management menu. - Customize design: Change fonts, colours, spacing, and layout using the style settings. - Add forms: Create contact forms and other interactive elements. - Configure SEO: Set page titles, meta descriptions, and keywords for search engines. Publishing Your Website 1. When you are happy with your design, click Publish. 2. Your website will go live on the domain. Important: Publishing a Sitejet Builder website will replace all files in the document root. If you already have a website, back it up first. Using Sitejet Builder on an Existing Domain 1. Go to Websites & Domains. 2. Click the domain name. 3. On the domain card, click the Get Started tab. 4. Click Create Website. 5. Select a template and start editing. Important Notes - Sitejet Builder is free and included with Plesk 18.0.55 and later. - Your domain should be properly resolving to the server before publishing. - Always back up existing website files before publishing a Sitejet website. - Sitejet websites are responsive by default — they work on desktop, tablet, and mobile. Troubleshooting Sitejet Builder option is not available: - Your subscription may not have the "Access to Sitejet Builder" permission. Contact your hosting provider. Changes not appearing after publishing: - Clear your browser cache (Ctrl+F5) and reload the page. - If using Cloudflare or a CDN, purge the cache. Cannot access the editor: - Try a different browser (Chrome or Firefox recommended). - Disable browser extensions that may interfere with the editor. Related Guides - Prefer WordPress instead - Clone the result - Set the document root

How to Install a Laravel Application in Plesk

Plesk's Laravel Toolkit makes it easy to deploy and manage Laravel applications directly from your hosting panel — no command line needed for most tasks. Prerequisites - The Laravel Toolkit extension must be installed on the server. If you don't see the Laravel option, contact your hosting provider. - A domain or subdomain set up in Plesk to host your application. Option 1: Install a fresh Laravel skeleton 1. Log in to Plesk. 2. Go to Websites & Domains and find your domain. 3. Click Create Website > Laravel. 4. Select Install Skeleton and click Install Application. 5. Wait for the installation to complete — your Laravel app is now live. Option 2: Deploy from a Git repository 1. Follow steps 1–3 above. 2. Select Install from remote repository. 3. Paste your Git repository URL. 4. If the repository is private, add the displayed public key to your repository deploy keys. 5. Click Install Application. Option 3: Upload existing files and scan 1. Upload your Laravel project files to the domain directory via File Manager or FTP. 2. Go to Websites & Domains > your domain > Hosting & DNS tab > Hosting. 3. Change Document root to your app public directory (e.g. /httpdocs/public) and click Save. 4. Go back to the Dashboard tab, click Create Website > Laravel, click Cancel, then click Scan. Setting up a database 1. From the Laravel dashboard, click Manage domain. 2. Click Databases > Add Database and create your database. 3. Go back to the domain card and click Laravel. 4. Click Edit next to "Environment variables (.env)" and add your database credentials. 5. Go to the Artisan tab and run the migrate command. Running commands The Laravel Toolkit lets you run Artisan, Composer, and npm commands directly from Plesk — no SSH required. Switch to the relevant tab and select or type your command. Troubleshooting - Laravel option missing: The Laravel Toolkit extension is not installed. Contact your hosting provider. - 500 error after deployment: Check your .env file for correct database credentials and run artisan config:cache. - Permission errors: Make sure the storage and bootstrap/cache directories are writable. Related Guides - Set up Node.js - Install Python - Set the PHP version

How to Set Up a Node.js Application in Plesk

Plesk makes hosting Node.js applications straightforward with its built-in Node.js extension. You can configure, install dependencies, and manage your app entirely from the web interface. Prerequisites - The Node.js extension must be installed on the server. If you do not see the Node.js option, contact your hosting provider. - Your application files ready to upload (including package.json). Step 1: Upload your application files 1. Log in to Plesk. 2. Go to Websites & Domains and find your domain. 3. Click Files and create a directory for your app (e.g. myapp). 4. Upload your application files into that directory using File Manager, FTP, or the Git extension. Step 2: Configure the application 1. Go to Websites & Domains and click Create Website > Node.js on your domain card. 2. Node.js Version: Select the version your app requires. 3. Package Manager: Choose npm or Yarn (Plesk auto-detects, but you can override). 4. Document Root: Set to the directory containing your static files (e.g. myapp/public). 5. Application Root: Set to the directory containing your app files (e.g. myapp). 6. Application Startup File: Enter the filename that starts your app (e.g. app.js or server.js). 7. Application Mode: Set to Development while testing, switch to Production when ready. 8. Add any Custom Environment Variables your app needs. Step 3: Start the application 1. Go to Websites & Domains > your domain > Node.js. 2. Click Enable Node.js. 3. Click NPM Install (or Yarn Install) to install your dependencies from package.json. 4. Click the Application URL to verify your app is running. Running scripts You can run scripts defined in your package.json by clicking Run Script, entering the script name, and clicking OK. Stopping the application Go to Websites & Domains > your domain > Node.js and click Disable Node.js. Your settings are preserved and you can re-enable at any time. Important notes - Plesk uses Phusion Passenger to serve Node.js apps. Your startup file must listen on process.env.PORT. - The NPM Install button only appears when a package.json file exists in the application root. - Each domain can only have one Node.js application root. Subdomains need separate configurations. Troubleshooting - App shows Apache default page: Make sure the Document Root is set correctly and Node.js is enabled. - 502 or startup errors: Check the application logs via the Logs tab on your domain card. - Missing NPM Install button: Ensure package.json exists in the Application Root directory. Related Guides - Install Laravel - Install Python - Set the document root

How to Change the Document Root for Your Domain in Plesk

The document root is the directory where Plesk serves your website files from. By default it is set to httpdocs, but you may need to change it — for example, if your framework uses a public subdirectory or you want to point to a different folder. How to change the document root 1. Log in to Plesk. 2. Go to Websites & Domains. 3. Find the domain you want to modify and click Hosting & DNS tab > Hosting. (In some Plesk views, this is labelled Hosting Settings.) 4. Find the Document root field. It shows the current directory (usually httpdocs). 5. Change the value to your desired directory path. For example: - httpdocs/public — for Laravel, Symfony, or other frameworks - httpdocs/web — for some CMS platforms - A completely different folder name you have created 6. Click OK or Save to apply the change. Important notes - The path is relative to your webspace root directory, not an absolute server path. - The directory must already exist. If it does not, create it first using File Manager or FTP. - Changing the document root does not move your files — it only changes where Plesk looks for them. You need to make sure your website files are in the new directory. - This change takes effect immediately. Your site may go offline briefly if the new directory is empty or missing key files. - SSL certificates are not affected by document root changes. Common use cases - Laravel / Symfony: Set document root to httpdocs/public so only the public folder is web-accessible. - Subdirectory install: Point to a subfolder like httpdocs/blog if you installed a CMS in a subdirectory. - Separating app and public files: Keep your application code above the document root for better security. Troubleshooting - 403 Forbidden after change: The new directory exists but has no index.html or index.php file. Upload your files or check the path. - Site shows wrong content: Double-check the directory path. A typo will point to the wrong folder or a non-existent one. - Cannot find Hosting Settings: On some Plesk views, go to the Hosting & DNS tab first, then click Hosting. Related Guides - Clone the site - Set the PHP version - For a WordPress install

How to Clone Your Website in Plesk

Plesk lets you copy your website files to another domain or subdomain on the same server. This is useful for creating staging environments, testing changes, or duplicating a site before a redesign. Method 1: Website Copying (all websites) This copies website files only — databases are not included and must be copied separately if needed. 1. Log in to Plesk. 2. First, create the destination domain or subdomain where you want the copy to go. Go to Websites & Domains and click Add Domain or Add Subdomain. 3. Go back to Websites & Domains and find the source domain (the site you want to copy). 4. On the domain Dashboard tab, click Website Copying. 5. Under Site name, select the destination domain or subdomain you created. 6. Choose what to do with existing files on the destination: - Do not remove files — keeps existing files, overwrites duplicates - Remove all files — clears the destination first 7. Click OK to start the copy. Method 2: WordPress Clone (WordPress sites only) If your site runs on WordPress and WP Toolkit is available, cloning copies everything — files, database, and settings. 1. Log in to Plesk. 2. Go to WordPress in the left menu (or click WP Toolkit on your domain card). 3. Find the WordPress installation you want to clone and click Clone. 4. Choose the target: - Create subdomain: Plesk creates a new subdomain automatically (default prefix is "staging"). - Use existing domain or subdomain: Select from the dropdown list. 5. (Optional) Change the database name for the clone. 6. Click Start. 7. When complete, the cloned site appears in your WordPress installations list. Important notes - Website Copying does not copy databases. If your site uses a database, export it manually via Databases and import it on the destination. - WordPress Clone handles databases automatically — no extra steps needed. - When cloning to an existing domain, any files on the destination may be overwritten. - After cloning a WordPress site, update the site URL in the clone settings if the domain name differs. Copying to an external server via FTP 1. Go to Websites & Domains > your domain > Website Copying. 2. Select FTP storage. 3. Enter the FTP hostname, port (default 21), directory, username, and password. 4. Click OK to start the transfer. Troubleshooting - Website Copying option missing: This feature may not be available in all Plesk editions. Contact your hosting provider. - Clone shows errors: Make sure the destination domain has enough disk space and is not already in use by another application. - Database not copied: If you used Website Copying (not WP Clone), you must copy the database separately via phpMyAdmin or the Databases tool. Related Guides - Set the document root - Install WordPress - Update & secure it

How to Install a Python Application in Plesk

Plesk can host Python web applications such as Flask and Django using Phusion Passenger as the application server. Setup requires some server-side configuration, but once done your app runs directly from the Plesk interface. Prerequisites - Phusion Passenger and Python must be installed on the server. If the Python option is not available, contact your hosting provider. - Your application files ready with a requirements.txt listing all dependencies. - SSH access may be required for installing Python packages. Step 1: Upload your application 1. Log in to Plesk. 2. Go to Websites & Domains and find your domain. 3. Upload your Python app files to the domain directory using File Manager, FTP, or the Git extension. 4. Make sure requirements.txt is in the application root directory. Step 2: Configure the Python application 1. Go to Websites & Domains and click the Python icon on your domain card. 2. Click Enable Python. 3. Set the Python Version to match the version your app was built with. 4. Set the Application Root to the directory containing your app files (e.g. /httpdocs). 5. Set the Application Startup File: - For Flask: app.py (or whatever file contains your Flask app) - For Django: passenger_wsgi.py (see Step 3) 6. Set Application Mode to Production when your app is ready to go live. Step 3: Create passenger_wsgi.py (Django only) Django applications need a bridge file for Phusion Passenger. Create a file called passenger_wsgi.py in your application root with the following content: import sys, os sys.path.append(os.getcwd()) from myproject.wsgi import application Replace myproject with your actual Django project folder name. Step 4: Install dependencies 1. In the Python application settings, click Run Pip Install. Plesk creates a virtual environment and installs everything from requirements.txt. 2. Alternatively, SSH into your server and run: cd /var/www/vhosts/yourdomain.com/httpdocs && pip install -r requirements.txt Step 5: Run database migrations (Django) In the Python settings, use Run Script with: - Script name: manage.py - Arguments: migrate Repeat with collectstatic to gather static files. Step 6: Restart and verify 1. Click Restart Application in the Python settings. 2. Visit your domain in a browser to verify the app is running. Troubleshooting - Phusion Passenger error page: Check the Logs tab on your domain card for Python traceback errors. - Module not found errors: Run Pip Install again or verify your requirements.txt is complete. - Static files not loading (Django): Make sure you ran collectstatic and your STATIC_ROOT is configured in settings. - App not restarting: Create a tmp directory in your app root and run touch tmp/restart.txt via SSH to force a restart. Related Guides - Install Laravel - Set up Node.js - Check PHP version

How to Change the PHP Version for a Domain in Plesk

Different websites and applications may require different PHP versions. Plesk lets you switch the PHP version for each domain individually, so you can run a modern site on PHP 8.3 while keeping an older application on PHP 7.4 on the same server. This guide covers changing the PHP version and handler type for a single domain. Step 1: change the PHP version 1. Log in to your Plesk control panel. 2. Go to Websites & Domains. 3. Find the domain you want to configure, then click the PHP link (on the domain card, next to the current PHP version number). 4. Make sure PHP support is enabled (checkbox should be ticked). 5. Select the desired PHP version from the dropdown menu (e.g., 8.1, 8.2, 8.3). 6. Select the handler type — we recommend FPM application served by nginx for best performance. 7. Click OK. Step 2: verify the change 1. Go back to Websites & Domains. 2. Check the domain card — the PHP version number should now show the new version next to the PHP icon. 3. Visit your website to make sure it loads correctly. For a more detailed check, click the PHP link again and then click View the phpinfo() page at the bottom. This shows all PHP configuration details for the domain. Understanding PHP handler types The handler type controls how PHP processes requests. Here is a quick comparison: - FPM application served by nginx — best performance, lowest memory use, recommended for most sites - FPM application served by Apache — good performance, uses Apache to serve PHP - FastCGI application — good balance of performance and compatibility - Apache module — highest memory use, simplest setup, not recommended for shared hosting Important notes - PHP version changes take effect almost immediately. If your site shows errors, switch back to the previous version right away. - The available PHP versions depend on what your hosting provider has installed on the server. If a version you need is missing, contact support. - PHP 7.x has reached end of life and no longer receives security updates. Upgrade to PHP 8.x if your application supports it. - WordPress currently requires at least PHP 7.4, but PHP 8.2 or higher is recommended for best performance and security. - Each domain and subdomain can use a different PHP version. Subdomains inherit settings from their parent domain unless you change them separately. Troubleshooting - Website shows a 500 error after changing PHP version? Switch back to the previous version immediately. Your application or plugins may not be compatible with the new version. - White screen of death? Same as above — revert the PHP version and check your application compatibility requirements. - Desired PHP version not in the dropdown? Your hosting provider has not installed that version. Open a support ticket to request it. - Cannot find the PHP link on the domain card? You may be in Service Provider view. Switch to Power User view, or go to Websites & Domains > the domain > Hosting & DNS > PHP Settings. - Changes not taking effect? Clear your website cache (if using a caching plugin or CDN) and try again. PHP handler changes may take a minute to propagate. Related Guides - Adjust PHP settings - For WordPress - For a Node.js app

How to Create Additional FTP Accounts in Plesk

If you need to give someone else FTP access to your website — like a developer working on a specific section, or a collaborator who needs to upload files to a particular folder — you can create additional FTP accounts in Plesk. Each account can be restricted to its own directory, so users only access what they need. Step 1: add a new FTP account 1. Log in to your Plesk control panel. 2. Go to Websites & Domains. 3. Find your domain, then click FTP Access (under "Files & Databases"). 4. Click Add an FTP Account. 5. Fill in the details: - FTP account name — this will be the username the person uses to connect - Home directory — click the folder icon to browse and select the directory this user should access. Leaving it blank grants access to the entire domain root (not recommended) - Password — set a strong password, or click Generate to create one automatically 6. Click OK. Step 2: share the FTP login details Give the user these details to connect via their FTP client (FileZilla, Cyberduck, etc.): - Host: your domain name or server IP address - Port: 21 - Username: the FTP account name you just created - Password: the password you set - Protocol: require FTPS (FTP over TLS) — standard FTP is insecure and may be blocked Managing existing FTP accounts To modify an FTP account (change password, home directory, etc.): 1. Go to Websites & Domains > FTP Access. 2. Click the account name in the list. 3. Make your changes and click OK. To remove an FTP account: 1. Go to Websites & Domains > FTP Access. 2. Select the checkbox next to the account you want to remove. 3. Click Remove, then confirm. Important notes - The main FTP account (the one tied to your subscription) cannot be deleted — only additional accounts can be removed. - Always restrict home directories to the smallest folder needed. Giving access to / (the entire domain root) means the user can see and modify everything, including config files. - Plesk requires FTPS (FTP over TLS) for additional FTP accounts on Linux. Standard unencrypted FTP may be blocked by the server. - If you get a "nonexistent physical directories" error after creating an account, make sure the home directory you selected actually exists in the File Manager. - FTP accounts are per-domain — an account created under one domain cannot access files on another domain. Troubleshooting - Connection refused? Make sure your FTP client is using port 21 and FTPS protocol (not SFTP — that is SSH, a different thing entirely). - User can see all files despite setting a home directory? Double-check the home directory path. It should point to a specific subfolder, not the domain root. - Login fails after creating the account? Wait a few minutes for the account to propagate. If it still fails, reset the password and try again. - No "FTP Access" link showing? You may be in Service Provider view. Switch to Power User view, or look under Domains > your domain > FTP Access. Related Guides - Point them at a document root - Upload files

How to Manage Cron Jobs in Plesk

Scheduled tasks (also called cron jobs) let you run scripts or commands automatically at set times — for example, running a WordPress cron script every hour, generating a daily backup, or sending automated email reports. Plesk provides a built-in task scheduler so you can set this up without command-line access. Step 1: create a new scheduled task 1. Log in to your Plesk control panel. 2. Go to Websites & Domains. 3. Find your domain, then click Scheduled Tasks (under "Dev Tools" or "More"). 4. Click Add Task. 5. Choose the task type: - Run a command — execute a shell command or script (e.g., a backup script) - Fetch a URL — visit a URL on a schedule (no need for curl or wget, just enter the URL) - Run a PHP script — execute a PHP file directly, with a PHP version selector 6. Enter the command, URL, or script path depending on the type you selected. 7. Set the schedule: - Choose a preset (every hour, every day, every week, every month) or - Select Cron style to enter a custom schedule using cron syntax (e.g., */5 * * * * for every 5 minutes) 8. Make sure Active is ticked. 9. Click OK or Run Now to test the task immediately. Common cron schedule examples - Every 5 minutes: */5 * * * * - Once per hour: 0 * * * * - Once per day at midnight: 0 0 * * * - Once per day at 3:15 AM: 15 3 * * * - Once per week on Monday at 6 AM: 0 6 * * 1 - Once per month on the 1st at midnight: 0 0 1 * * The format is: minute hour day-of-month month day-of-week. Use a tool like crontab.guru to build and test expressions if you are not familiar with cron syntax. Managing scheduled tasks All your tasks are listed on the Scheduled Tasks page. From there you can: - Edit — click the task name to modify its settings - Enable/disable — click the toggle icon next to the task - Run now — click the play icon to execute the task immediately (useful for testing) - Remove — select the checkbox and click Remove Important notes - Run a PHP script is the easiest option for WordPress cron. Just enter the path to your script relative to the domain root (e.g., httpdocs/wp-cron.php) and select the PHP version. - Fetch a URL is ideal for triggering webhooks or visiting endpoints on a schedule. Plesk handles the HTTP request — no need to write curl commands. - Avoid scheduling resource-intensive tasks at peak hours. Off-peak times (early morning) are better for backups and heavy scripts. - If a task fails, Plesk will show the error output. Check this to diagnose issues. - By default, scheduled tasks run in a chrooted environment on Linux — this means the task can only access files within the domain directory, which is a security feature. - The system user context for the task is set automatically based on your subscription. Troubleshooting - Task runs but does not seem to work? Click Run Now and check the output. If there is an error, it will appear in the task details. - Cannot find "Scheduled Tasks" for my domain? In Power User view, look under Websites & Domains > your domain > Scheduled Tasks. In Service Provider view, go to Domains > your domain > Scheduled Tasks. - Task times out? Some hosting providers limit cron execution time. If your script takes too long, contact support to check if there is a time limit. - PHP script path not working? Make sure the path starts from the domain root, not from the server root. For example, use httpdocs/myscript.php, not /var/www/vhosts/domain/httpdocs/myscript.php. Related Guides - Set the document root - For DB tasks