How to Install Acelle Mail on cPanel: Complete Guide
Before you start
Acelle Mail can be deployed on a cPanel account when the host gives you the PHP version, extensions, database access, document-root control and scheduled jobs required by the application. Because Acelle is a Laravel-based PHP application, correct public-directory and writable-directory handling matters. A cPanel installation is convenient, but hosting limits can become a bottleneck for queue workers or large campaigns.
Important: installation instructions can change between software releases. Use the version bundled with your license and compare the vendor's current requirements before copying commands into production. Where this article uses an adapted Caddy or Docker pattern, it is clearly labeled rather than presented as vendor certification.
What you need
- cPanel hosting with a compatible PHP version.
- MySQL/MariaDB access.
- File Manager or SFTP.
- PHP extension selector or host support.
- Cron Jobs access.
- SSL/AutoSSL.
- A valid Acelle Mail license/package.
- SMTP/SES credentials.
Architecture
Domain → cPanel/Apache → PHP → Acelle Mail → MySQL/queue → SMTP/SESKeeping these layers separate makes troubleshooting easier. If the web dashboard works but campaigns do not send, the problem may be in cron, the queue, the delivery server or the provider rather than in the web server. Conversely, a 502 or 500 error normally belongs to the web/PHP layer.
Step-by-step installation
1. Create the domain/subdomain
Create mail.example.com and confirm DNS. Decide where the application's public web root will live.
2. Select PHP
Use MultiPHP Manager or Select PHP Version. Enable the modules required by the current Acelle package. If the host does not expose a required extension, ask support before proceeding.
3. Create MySQL database
Create a database and user in cPanel and grant full privileges to that database. Copy the exact prefixed names.
4. Upload the application
Upload the Acelle package and extract it. Follow the installation guide included with your licensed package for the correct document-root/public-directory arrangement.
5. Set permissions
Laravel-style storage and cache directories must be writable by the PHP process. Avoid making the entire project directory 777.
6. Run the installer
Open the HTTPS installation URL and complete the system checks, database configuration and admin setup.
7. Configure cron/queue
Use cPanel Cron Jobs for the scheduled tasks specified by your Acelle version. If the application requires long-running Supervisor workers and your cPanel host does not provide them, that is a sign that a VPS is a better environment.
8. Enable SSL
Use AutoSSL or the provider's certificate manager and configure the application URL for HTTPS.
9. Configure sending
Add Amazon SES, SMTP or another supported sending server. Verify sender authentication and test the connection.
10. Test resources
Run a small campaign, watch queue/cron processing and review cPanel resource usage. Shared hosting limits can affect PHP execution time, CPU and memory.
Post-install configuration
Once the installer finishes, resist the temptation to immediately import a large list and launch a campaign. First configure the sending layer, domain authentication, bounce handling and unsubscribe behavior. Your application can be perfectly healthy while the email infrastructure is not ready for production.
1. Configure the sending service
Use a delivery service or MTA that is appropriate for your sending volume and compliance requirements. Record the exact SMTP/API endpoint, credentials, region and encryption settings. Never publish credentials in screenshots, tutorials, public repositories or support tickets.
2. Authenticate the sending domain
Publish the SPF, DKIM and DMARC records required by your chosen delivery service. If the provider gives you DKIM CNAME records, use those exact values. Avoid creating multiple conflicting SPF records. Start DMARC in a monitoring mode when you are still mapping legitimate senders, then tighten the policy once authentication is verified.
3. Configure bounces and complaints
A campaign system should not keep treating permanently failing addresses as healthy subscribers. Configure the application's bounce/complaint workflow and monitor the resulting logs. If your provider exposes feedback-loop events, connect them where the application supports it.
4. Test with a small list
Send a controlled test to addresses you own at more than one mailbox provider. Check authentication results, rendering, unsubscribe behavior, tracking, bounce handling and queue processing. Only after the end-to-end workflow passes should you increase campaign volume.
Common mistakes to avoid
- Installing a PHP version without checking the application's current compatibility requirements.
- Using the database root account inside the application.
- Making the entire application directory world-writable.
- Putting passwords or AWS credentials into a public repository.
- Assuming a successful login means scheduled jobs are working.
- Sending a large campaign before SPF/DKIM/DMARC and bounce handling are verified.
- Treating the application as the email delivery server when it actually relies on an external SMTP/API provider.
- Skipping backups before upgrades.
Troubleshooting
Storage/cache permission error
Check the writable directories required by your Acelle version and ownership of those directories.
Blank page/500
Check cPanel error logs, PHP version and required extensions.
Cron runs but queue remains
Check whether the task is a scheduler or a long-running worker. Some hosts cannot provide the latter reliably.
URL redirects incorrectly
Check the configured application URL, SSL and cPanel domain mapping.
Large imports fail
Review PHP upload limits, execution time, memory and host process limits.
Security checklist
- Use SSH keys where possible and disable unnecessary remote access.
- Keep the operating system, PHP runtime and application patched.
- Use a dedicated database account.
- Keep MySQL private unless remote access is explicitly required.
- Use HTTPS for the administration interface.
- Protect application configuration and secret files.
- Back up the database and uploaded/application data.
- Test restoring a backup rather than assuming it is usable.
- Monitor disk, RAM, CPU, queue depth and application logs.
When should you choose this installation method?
cPanel is a good Acelle choice when you want managed server administration and a graphical control panel. It is best for smaller installations or users who do not want to maintain Linux manually. If the application needs persistent workers, Redis or higher resource limits, a VPS or Docker deployment is usually easier to operate.
Final checklist
- ☐ DNS resolves to the server
- ☐ Supported PHP/runtime is installed
- ☐ Database and dedicated user created
- ☐ Application installer completed
- ☐ Correct file permissions applied
- ☐ HTTPS works
- ☐ Cron/worker jobs execute
- ☐ Sending service connected
- ☐ SPF/DKIM/DMARC verified
- ☐ Bounce/complaint processing tested
- ☐ Unsubscribe tested
- ☐ Backup created and restore plan documented
- ☐ Small end-to-end test campaign completed
Related installation guides
- How to Install Acelle Mail on Ubuntu VPS
- How to Install Acelle Mail on Caddy
- How to Install Acelle Mail on Docker
- Browse all self-hosted email software installation guides
- About Abhishek Sharma
Sources & references
This guide uses the following vendor or platform documentation. Where a deployment method is an adaptation rather than vendor documentation, that distinction is stated in the article.