Dolibarr is an open-source ERP and CRM solution increasingly adopted by businesses looking to efficiently manage their accounting, inventory, customers, and many other aspects of their operations. While its installation is relatively simple, several mistakes can lead to compatibility issues, performance problems, or security vulnerabilities.

In this article, we will review the most common mistakes made during Dolibarr installation and how to avoid them to ensure a successful deployment.

1. Not Checking the Technical Requirements Before Installation

Before installing Dolibarr, it is crucial to ensure that your server environment meets the software's requirements. Installing it on a misconfigured server can cause execution errors, slowdowns, or malfunctions.

Essential Checks Before Installation

• Web server: Apache, Nginx, or IIS
• PHP version: Dolibarr recommends PHP 7.3 or higher
• Database: MySQL 5.6+, MariaDB 10.0+, or PostgreSQL
• Required PHP extensions: gd, curl, json, mbstring, openssl, zip

If these elements are not properly configured, Dolibarr may not function correctly or may encounter critical errors during installation.

2. Installing Dolibarr on an Inadequate Shared Hosting Server

If you opt for a low-cost shared hosting service, make sure it meets Dolibarr's requirements. Some hosting providers limit PHP script execution or impose database restrictions, which can slow down or block the installation process.

Tips for Choosing the Right Hosting

• Choose a VPS or dedicated server for better control over settings
• Check that the hosting provider allows access to logs and PHP configuration
• Ensure the server has sufficient resources (RAM, CPU) to run Dolibarr smoothly

If your company has multiple users and a large database, a dedicated server or a well-configured VPS is highly recommended.

3. Incorrectly Configuring the Database

One of the most common mistakes during Dolibarr installation is misconfiguring the database. An unoptimized database can lead to slow performance, SQL errors, or even data loss.

Best Practices for Database Configuration

• Create a dedicated database for Dolibarr instead of using an existing one shared with other applications
• Use a dedicated MySQL user with the necessary privileges (CREATE, UPDATE, DELETE, etc.)
• Choose the right storage engine (InnoDB is recommended for its transaction management and data integrity)

Ignoring these settings can result in database access errors and compromise Dolibarr’s proper functioning.

4. Forgetting to Delete the Installation Folder After Setup

After installing Dolibarr, the install/ folder remains accessible by default. Leaving this folder on your server creates a major security risk, as a malicious user could reinstall or modify your configuration.

Solution

As soon as the installation is complete and Dolibarr is accessible, immediately delete the /install/ folder from your server.

To further enhance security, it is also recommended to change file permissions for sensitive files and enforce HTTPS access.

5. Not Properly Configuring PHP and Apache/Nginx Settings

Some PHP or web server configuration errors can cause bugs or poor performance.

Common PHP Configuration Mistakes

• Insufficient memory limit: Increase memory_limit to 256M or more
• Short execution time: Modify max_execution_time to 300 seconds to prevent interruptions
• Limited file upload size: Check upload_max_filesize and post_max_size to allow large file uploads

If you are using Apache or Nginx, make sure the .htaccess file or server configuration correctly supports URL rewriting (mod_rewrite) to prevent display errors.

6. Failing to Secure Dolibarr Access

Once Dolibarr is installed, it is essential to strengthen security to prevent hacking attempts or data breaches.

Essential Security Measures

• Use a strong password for the administrator account
• Restrict back-office access by limiting logins to specific IP addresses
• Enable HTTPS to secure data exchanges
• Perform regular backups of the database and files

Neglecting these security measures exposes your Dolibarr installation to cyberattacks and data loss.

7. Ignoring Software Updates and Security Patches

Many users install Dolibarr and then forget to keep the software updated. This can be problematic because security vulnerabilities or unresolved bugs may render your installation unstable.

Why Regular Updates Are Important

• Each new version fixes security flaws and improves performance
• Compatibility with PHP and MySQL evolves, making some versions obsolete
• Some modules and extensions require an updated version of Dolibarr to function correctly

It is recommended to check for updates at least once a quarter and perform a full backup before applying any update.

Conclusion

Installing Dolibarr is relatively simple, but it is essential to avoid common mistakes that could compromise its performance and security. Checking technical requirements, choosing the right hosting, properly configuring the database and web server, securing access, and keeping the software updated are crucial steps to ensure a successful installation.

By following these best practices, you will ensure that your company has a high-performing, secure, and scalable Dolibarr setup, ready to meet your business management needs.