Help Center
Search for the articles here or browse the categories below.
Browse by topic
Find guides, tutorials, and answers organised by category.
Getting Started
New to Allanux Web? Start here.
Browse
Web Hosting
Cloud hosting plans, Plesk and website management.
Browse
WordPress Hosting
Managed WordPress plans, caching and CDN.
Browse
Domains
Register, manage and point your domain name.
Browse
Email Hosting
Professional email, webmail and device setup.
Browse
Website Design & Development
Our website packages and how projects run.
Browse
Website Migrations
Move your site to Allanux Web for free.
Browse
Billing & Account
Invoices, renewals, upgrades and account details.
Browse
Reseller Hosting
Sell hosting under your own brand with WHMCS.
Browse
SSL & Security
Free SSL and keeping your website safe.
Browse
Troubleshooting & Support
Fix common issues and reach our team.
Browse
Allanux Web Platform · My Dashboard
Manage your client area — services, invoices, domains and more.
Browse
Allanux Web Platform · Reseller Hosting
Manage your client area — services, invoices, domains and more.
Browse
Allanux Web Platform · Account Management
Manage your client area — services, invoices, domains and more.
Browse
Allanux Web Platform · Getting Started
Manage your client area — services, invoices, domains and more.
Browse
Allanux Web Platform · Affiliates
Manage your client area — services, invoices, domains and more.
Browse
WordPress
Install, secure, update and troubleshoot WordPress.
Browse
Plesk End Users · Getting Started
Manage websites, domains, email and apps in Plesk.
Browse
Plesk End Users · Domains & DNS
Manage websites, domains, email and apps in Plesk.
Browse
Plesk End Users · Mail
Manage websites, domains, email and apps in Plesk.
Browse
Plesk End Users · Websites & Applications
Manage websites, domains, email and apps in Plesk.
Browse
Plesk End Users · SSL & Security
Manage websites, domains, email and apps in Plesk.
Browse
Plesk End Users · Backups
Manage websites, domains, email and apps in Plesk.
Browse
Plesk End Users · Databases
Manage websites, domains, email and apps in Plesk.
Browse
Plesk End Users · File Management
Manage websites, domains, email and apps in Plesk.
Browse
Plesk Resellers · Getting Started
Manage client accounts, plans, branding and resources in Plesk.
Browse
Plesk Resellers · Customer Management
Manage client accounts, plans, branding and resources in Plesk.
Browse
Plesk Resellers · Service Plans
Manage client accounts, plans, branding and resources in Plesk.
Browse
Plesk Resellers · Domains & Subscriptions
Manage client accounts, plans, branding and resources in Plesk.
Browse
Plesk Resellers · Reseller Reports
Manage client accounts, plans, branding and resources in Plesk.
Browse
Plesk Resellers · Branding
Manage client accounts, plans, branding and resources in Plesk.
Browse
Plesk Resellers · SSL for Clients
Manage client accounts, plans, branding and resources in Plesk.
Browse
Plesk Resellers · Advanced Settings
Manage client accounts, plans, branding and resources in Plesk.
Browse
Popular articles
What other people are reading right now.
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
🚀 Plesk End Users · Websites & ApplicationsHow 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
💾 Plesk End Users · BackupsHow to Exclude Specific Files or Folders from Plesk Backups
Not everything on your hosting account needs to be in every backup. Large media folders, cache directories, or temporary files can bloat your backup size and slow the process down. Plesk lets you exclude specific files and folders so your backups stay lean and fast. How to exclude files from a domain backup 1. Log in to your Plesk control panel. 2. Go to Websites & Domains > Backup Manager. 3. Click Back Up to start a new backup. 4. Choose your backup type (full or incremental). 5. Tick the "Exclude specific files from the backup" checkbox. 6. Enter the paths of files or folders you want to exclude in the text box that appears. Enter one path per line. 7. Click OK to start the backup. Path format and examples All paths must be relative to your subscription root — not absolute server paths. Here are common examples: - Exclude a single file: httpdocs/images/old-photo.jpg - Exclude an entire folder and its contents: httpdocs/cache - Exclude all files inside a folder (but keep the empty folder): httpdocs/tmp/* - Exclude files by extension: httpdocs/uploads/*.log What to consider excluding - Cache folders — for example, httpdocs/wp-content/cache for WordPress sites. These regenerate automatically and don't need to be backed up. - Log files — Plesk often has a built-in option to exclude logs. Tick "Exclude log files" separately if available. - Large media archives — if you have gigabytes of video or image files that are already stored and backed up elsewhere, there's no need to include them again. - Temporary and staging files — anything in /tmp or development folders you don't need to preserve. Important notes - The wildcard * matches files within a single directory level only. It won't recurse into subfolders automatically. - Excluded files won't be available for restore from that particular backup. Make sure anything you exclude is either expendable or backed up through another method. - If you regularly exclude the same paths, Plesk remembers your exclusion settings for future backups of that domain. You won't need to re-enter them each time. - Excluding large folders can significantly reduce both backup time and storage usage on the server.
💾 Plesk End Users · BackupsHow to Restore a Database from a Plesk Backup
If your database got corrupted, accidentally modified, or you need to roll back to an earlier version, Plesk lets you restore a single database from a backup without affecting the rest of your account. Method 1: Restore from a subscription backup If you have a full subscription backup that includes databases, you can pull out just the database you need: 1. Log in to your Plesk panel. 2. Go to Websites & Domains > Backup Manager. 3. Click the backup that contains the database version you want. 4. Under What do you want to restore?, select Selected objects. 5. In the Type of object to restore dropdown, choose Database. 6. From the Available list, click the database you want to restore. It will move to the Selected column. 7. Under Restore, choose what to bring back: - Configuration only — restores the database structure and user accounts, but not the actual data. - Configuration and content — restores everything including all tables and data. 8. If the backup is password-protected, enter the password. 9. Click Restore. Method 2: Restore from a database dump (SQL file) If you exported a database dump earlier (an .sql file), you can import it back: 1. Go to Websites & Domains > Databases. 2. Click on the database you want to restore into. 3. Click Import Dump. 4. Choose the .sql file from your computer or select one already uploaded to the server. 5. Click OK. The dump file must match the database type — you can't import a MySQL dump into a PostgreSQL database. Important things to know - Restoring a database overwrites the current one. All existing tables and data in that database will be replaced with the backup version. Any changes made after the backup was created will be lost. - Database users are restored too. When restoring with configuration, the associated database user accounts are included. - One object type at a time. If you also need to restore files, you'll need to run a separate restore for those. - Check your site after restoring. Make sure your application (WordPress, Joomla, etc.) connects properly. If the database username or password changed, update your site's configuration file. How to export a database dump for safekeeping It's good practice to export a quick dump before making database changes: 1. Go to Websites & Domains > Databases. 2. Click the database name. 3. Click Export Dump. 4. The .sql file will be saved to your server. You can then download it from File Manager.
📁 Plesk End Users · File ManagementHow to Rename Files and Directories in Plesk
Renaming files and directories in Plesk File Manager is quick and straightforward. This guide walks you through the process. How to rename a file 1. Log in to Plesk. 2. Go to Websites & Domains and click File Manager for your domain. 3. Navigate to the folder containing the file you want to rename. 4. Hover over the file name to reveal additional options. Click the small dropdown arrow (or right-click menu icon) that appears next to the file. 5. Select Rename. 6. Type the new file name in the text field. 7. Click OK. The file is renamed immediately. How to rename a directory The process is identical to renaming a file: 1. In File Manager, find the directory you want to rename. 2. Hover over the directory name and click the dropdown arrow. 3. Select Rename. 4. Enter the new directory name. 5. Click OK. Important notes - File extensions matter. If you rename style.css to style.txt, the file will no longer function as a CSS stylesheet. Always keep the correct extension. - Renaming httpdocs or system directories will break your website. Only rename files and folders that you created or manage yourself. - Avoid spaces and special characters in file names. Use hyphens (-) or underscores (_) instead. Spaces in file names can cause issues with URLs and scripts. - Case sensitivity: Linux servers treat File.html and file.html as different files. Be consistent with your naming conventions. - Hidden files (starting with a dot, like .htaccess) are shown in File Manager by default. Be careful not to accidentally rename these — they control important server behaviour. Troubleshooting - Rename option not appearing: Make sure you’re hovering over the file/folder name, not clicking the checkbox. The dropdown icon appears on hover. - “Permission denied” error: The file may be owned by a different system user or have restrictive permissions. Contact your hosting provider for assistance. - Website broken after renaming: If you renamed a file that your website references (like a config file, image, or script), update the references in your code to match the new file name. Or rename it back to the original. - Links stopped working: Renaming a directory changes its URL. If you had yourdomain.com/old-folder/ and renamed it to new-folder, update any links pointing to the old URL.
🗄️ Plesk End Users · DatabasesHow to Allow Remote Database Connections in Plesk
By default, databases in Plesk only accept connections from the server itself (localhost). If you need to connect from an external application, a local development tool like MySQL Workbench, or another server, you'll need to enable remote access. Step 1: enable remote access for the database user 1. Log in to your Plesk control panel. 2. Go to Websites & Domains > Databases. 3. Click the User Management tab. 4. Click the name of the database user you want to grant remote access to. 5. Under Access control, choose one of these options: - Allow local connections only — default, no remote access - Allow remote connections from any host — lets anyone connect (use with caution) - Allow remote connections from — restricts access to specific IP addresses or hostnames (recommended) 6. Click OK to save. Step 2: connect from your remote application Use these connection details in your external application or tool: - Host: your domain name or server IP address - Port: 3306 (default MySQL/MariaDB port) - Username: the database user you configured above - Password: the database user's password - Database: the name of your database Important notes - Security first: avoid "Allow remote connections from any host" whenever possible. Specify the exact IP address of the server or computer that needs access. - Firewall: port 3306 must be open on your server's firewall. If connections time out, ask your hosting provider to check the firewall rules. - Encrypted connections: remote MySQL connections are unencrypted by default. For sensitive data, configure SSL for your database connections. - This setting is per-user — each database user has their own access control settings. - If you no longer need remote access, switch back to Allow local connections only to reduce your attack surface. Testing the connection From your local computer (if you have MySQL client installed), run: mysql -u your_db_user -p -h yourdomain.com Or use a GUI tool like MySQL Workbench, DBeaver, or HeidiSQL — enter the connection details above and click Test Connection. Troubleshooting - Connection refused? The server firewall is likely blocking port 3306. Contact your hosting provider to open it. - Access denied? Make sure the remote access setting is correct for that specific user, and double-check the password. - Connection times out? This usually means port 3306 is blocked. Try a different network to rule out your local firewall. - Access control option not showing? Your hosting plan may not include the Remote access for database users permission. Contact your hosting provider.