Help Center

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

✉️ Email

How to Access and Use Webmail in Plesk

Webmail lets you access your email from any web browser without needing to set up an email client. Plesk supports Roundcube as the webmail client. This guide explains how to access webmail and use it to manage your emails. Accessing Webmail 1. Open your web browser. 2. Navigate to https://webmail.yourdomain.com 3. Enter your full email address as the username (e.g., info@yourdomain.com). 4. Enter your email password. 5. Click Log in. You can also access webmail from Plesk: 1. Log in to Plesk. 2. Go to Mail. 3. Click the Webmail icon next to the email address. Enabling Roundcube for Your Domain 1. In Plesk, go to Websites & Domains. 2. Click the domain name. 3. Go to Hosting & DNS → Mail Settings. 4. Under Webmail, select Roundcube from the dropdown. 5. Click OK or Apply. Essential Webmail Features (Roundcube) - Reading and sending emails: Click on emails to read them. Click Compose to write a new message. - Folders: Use the folder list in the left sidebar to navigate between Inbox, Sent, Drafts, Trash, and Spam. - Contacts: Manage your address book under the Contacts tab. - Settings: Access preferences, identities, filters, and vacation settings under the Settings gear icon. - Search: Use the search bar to find emails by sender, subject, or content. Important Notes - Always use https:// when accessing webmail to ensure your connection is encrypted. - Webmail credentials are the same as your email account credentials, not your Plesk login. - If webmail is not accessible, check that Roundcube is enabled in your domain Mail Settings. - The Horde webmail client has been deprecated. If your domain still uses Horde, switch to Roundcube. Troubleshooting Webmail page does not load: - Ensure you are using https://webmail.yourdomain.com. - Try clearing your browser cache and cookies. - Verify Roundcube is selected in Websites & Domains → Mail Settings. "Login failed" error in webmail: - Use the full email address as the username. - Verify your password is correct. Reset it in Plesk under Mail if needed. Webmail URL returns an error: - The webmail subdomain may not be configured. Contact your hosting provider. - Try accessing webmail via Plesk: Mail → click the Webmail icon. Related Guides - Set up a desktop or phone client - Create the mailbox - Set up forwarding

🌐 Domains & DNS

How to Check DNS Records with the Plesk DNS Inspector

After changing DNS records in Plesk, you need to verify those changes went live. This guide covers how to check DNS records in Plesk and verify them using command-line tools and online checkers. Viewing DNS records in Plesk 1. Log in to Plesk. 2. Go to Websites & Domains → find your domain. 3. Click Hosting & DNS → DNS Settings. This page shows every record in your domain's zone file — A, AAAA, CNAME, MX, TXT, SRV, NS, and SOA records with their types and values. Checking records with nslookup The nslookup command (Windows, macOS, Linux) queries DNS servers directly: - A record: nslookup yourdomain.com 8.8.8.8 - MX record: nslookup -q=MX yourdomain.com 8.8.8.8 - TXT record: nslookup -q=TXT yourdomain.com 8.8.8.8 - CNAME: nslookup -q=CNAME www.yourdomain.com 8.8.8.8 - SRV: nslookup -q=SRV _autodiscover._tcp.yourdomain.com 8.8.8.8 - DKIM: nslookup -q=TXT default._domainkey.yourdomain.com 8.8.8.8 Checking records with dig (Linux/macOS) dig provides more detail than nslookup: - dig yourdomain.com A @8.8.8.8 - dig yourdomain.com MX @8.8.8.8 - dig yourdomain.com ANY @8.8.8.8 Online DNS checker tools These check records from multiple global locations: - DNSChecker.org — 100+ global servers, supports all record types - whatsmydns.net — global propagation map - MXToolbox — best for email records (MX, SPF, DKIM, DMARC) DNS propagation Changes take effect on your server immediately, but DNS servers worldwide cache records based on TTL: - Typical: a few minutes to a few hours - Maximum: up to 48 hours - Tip: reduce TTL to 300 before planned changes, then increase after propagation Important notes - Plesk shows the zone file, not what the world sees. If nameservers point elsewhere, Plesk records won't be active. - Flush local DNS cache for fresh results: ipconfig /flushdns (Windows), sudo dscacheutil -flushcache (macOS), sudo systemd-resolve --flush-caches (Linux). - Use public DNS (8.8.8.8 or 1.1.1.1) to avoid ISP cached results. Troubleshooting Record shows in Plesk but doesn't resolve externally: - Check your nameservers point to Plesk: nslookup -q=NS yourdomain.com - If nameservers point to an external provider, add records there. - Ensure you clicked Update in Plesk after changes. Record shows old value: - DNS caching — wait for TTL to expire or flush your cache. - Use 8.8.8.8 to bypass ISP cache. nslookup returns "server can't find" error: - The record may not exist. Double-check it in Plesk. - Try a different DNS server. Need help? Open a support ticket. Related Guides - Understand propagation - Manage DNS records - Set up DNSSEC

🏠 Your Account & Dashboard

Getting Started With Allanux Web Dashboard

Your Allanux Web dashboard is where you manage everything: your hosting, domains, invoices and support tickets. This guide covers what you will find there and how to get started. Log in to your dashboard 1. Go to allanuxweb.com/clientarea.php. 2. Enter the email address and password you used when you signed up. 3. Click Login. If you have forgotten your password, use the Forgot Password link on that page and we will email you a reset link. What you will find in the dashboard - Services — your hosting packages, with the option to upgrade, view resource usage or open the control panel. - Domains — every domain registered with us, where you manage renewals, nameservers and contact details. - Billing — your invoices, payment history and saved payment methods. - Support — open a ticket and track replies from our team. Opening your control panel Your websites and email are managed in Plesk rather than the dashboard itself. From Services, choose your hosting package and click through to the control panel — you will be logged in automatically, without needing a separate password. Keep your details current Invoices, renewal reminders and password resets all go to the email address on your account, so it is worth keeping it up to date. Your email address is also your login. Related Guides - Log in to your dashboard - Log in to Plesk - Install WordPress with WP Toolkit

🎨 Reseller: Branding & Server

How to View Plesk Reseller Traffic Reports

Monitoring traffic across all your customers helps you identify heavy users, plan capacity, and ensure fair resource distribution. This guide covers accessing traffic reports as a reseller. Viewing Traffic Reports 1. Log in to Plesk. 2. Go to Home. 3. The dashboard shows your total traffic usage for the current billing period. Viewing Per-Customer Traffic 1. Go to Customers. 2. The traffic column shows each customer current monthly usage. 3. Click a customer name → Websites & Domains → Statistics for detailed breakdown. Important Notes - Traffic statistics are updated once per day (usually at midnight server time). - Traffic includes HTTP, FTP, SMTP, POP3, and IMAP bandwidth. Troubleshooting Traffic report is empty: - Statistics may not have been processed yet. Wait 24 hours. Related Guides - Disk-space reports - Usage summaries - Heavy resource users

✉️ Email

How to Set Up Spam Filtering in Plesk

Plesk includes SpamAssassin, a server-side spam filter that scans incoming emails and scores them based on spam characteristics. You can configure spam filtering per email address to control how spam is handled. This guide covers setting up and fine-tuning spam filtering. Enabling Spam Filtering for an Email Address 1. Log in to Plesk. 2. Go to Mail. 3. Click the email address you want to protect. 4. Go to the Spam Filter tab. 5. Select Switch on spam filtering for this email address. 6. Choose how spam is handled: - Mark spam messages by adding text to subject: Adds a label (e.g., *****SPAM*****) to the subject line. You can then set up rules in your email client to sort these messages. - Delete all spam messages: Automatically deletes emails identified as spam. Use with caution — legitimate emails may be deleted. - Move spam to the Spam folder: Moves spam to a Spam IMAP folder. Messages in this folder are automatically deleted after 30 days. Review regularly to catch false positives. 7. Click OK. Adjusting Spam Filter Sensitivity 1. On the Spam Filter tab, click Show Advanced Settings. 2. In the Spam filter sensitivity field, set a value: - Default (7): Balanced for most situations. - Lower values (4-6): More aggressive — catches more spam but may produce more false positives. - Higher values (8-10): Less aggressive — fewer false positives but more spam may get through. 3. Click OK. Whitelisting and Blacklisting To allow specific senders through or block specific domains: 1. On the Spam Filter tab, find the White list and Black list fields. Whitelist (trusted senders): - Enter email addresses or domains (e.g., contact@trusted.com or *@trusted.com). - Emails from these senders will not be marked as spam. Blacklist (blocked senders): - Enter email addresses or domains you want to block (e.g., spammer@bad.com or *@spamdomain.com). Training the Spam Filter If you use the Move spam to the Spam folder option with IMAP access: - Move spam messages from Inbox to the Spam folder to help the filter learn. - Move legitimate messages from Spam back to Inbox to reduce false positives. - Over time, the filter becomes more accurate for your email patterns. Important Notes - The "Move spam to Spam folder" option only works with IMAP connections, not POP3. - Messages in the Spam folder are automatically deleted after 30 days. Review this folder regularly. - If SpamAssassin is not enabled on the server, contact your hosting provider. Troubleshooting Legitimate emails are being marked as spam: - Add the sender to the White list. - Increase the spam filter sensitivity value. Spam is still getting through: - Decrease the spam filter sensitivity value. - Add the spam source to the Black list. Spam filter option is not available: - SpamAssassin may not be enabled on your server. Contact your hosting provider. Related Guides - Add custom email filters - Set an auto-reply - Create the mailbox