During Concrete CMS installation, many encounter a 500 error due to incorrect permissions on the application/files directory. This is one of the typical issues we resolve within minutes. Our approach—from hosting selection to final optimization—ensures stable operation from the first run. With over a decade of experience and numerous projects, we know every nuance.
Server Requirements
Concrete CMS runs on PHP 7.4–8.2, MySQL 5.7+ (or MariaDB 10.2+), and PostgreSQL. The web server must be Apache with mod_rewrite or Nginx. For production, write access to application/files is mandatory. We recommend a dedicated server or VPS with 1 GB RAM and a modern processor. Budget hosting often leads to caching and performance issues—a common pain point for our clients. Our setup significantly reduces downtime compared to DIY installations.
Why Choose Composer Installation?
Installing via Composer is the preferred method: it ensures correct dependencies and simplifies core updates. Compare: manual installation takes about an hour, Composer takes 10 minutes. Based on our experience, 90% of clients choose this method.
composer create-project -n concrete5/composer mysite cd mysite # Web installer: open http://yourdomain.com/index.php/install # Or CLI installation: ./vendor/bin/concrete5 c5:install \ --db-server=localhost \ --db-username=myuser \ --db-password=secret \ --db-database=mysite_db \ --site="My Site" \ --admin-email=<your-email> \ --admin-password=StrongPass123 \ --starting-point=elemental_blank Starting points: elemental_blank (clean project) or elemental_full (with demo content). For production, we almost always use elemental_blank.
How to Configure Nginx Correctly?
A typical mistake is pointing the document root to the wrong folder. It must be the public/ directory. A correct configuration:
server { listen 80; server_name mysite.com; root /var/www/mysite/public; index index.php; location / { try_files $uri $uri/ /index.php$is_args$args; } location ~ \.php$ { fastcgi_pass unix:/run/php/php8.1-fpm.sock; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; include fastcgi_params; } location ~* ^/application/ { deny all; } } For Apache, the .htaccess file in the public/ directory is included with the CMS.
Comparison of Installation Methods: Composer vs Manual
| Criteria | Composer | Manual Installation |
|---|---|---|
| Time | ~10 min | ~1 hour |
| Dependencies | Automatic | Manual |
| Updates | Via Composer | Extract archive |
| Errors | Minimal | Frequent permission issues |
Why Does a 500 Error Occur After Installation?
Most often—incorrect permissions on application/files/ or missing ionCube (though not required). Check: chmod -R 777 application/files and ensure PHP runs under the same user as the web server. If the error persists, enable debug mode in application/config/app.php: 'debug' => true. According to our data, 95% of 500 errors are resolved by correcting permissions.
How to Optimize Concrete CMS Performance?
Start with caching: in Dashboard → System & Settings → Cache & Speed enable Full Page Caching. For dynamic sites, use Redis—page generation speed increases up to 3 times. Also configure gzip compression on the server and enable aggressive static caching via CDN. Professional setup pays off from the first month if you save hours of project work.
Environment Configuration (PHP)
Main settings are stored in application/config/app.php and database.php. Example:
// application/config/app.php return [ 'debug' => false, 'url' => 'https://mysite.com', 'charset' => 'UTF-8', 'timezone' => 'Europe/Minsk', 'locale' => 'ru_RU', ]; // application/config/database.php return [ 'default-connection' => 'concrete', 'connections' => [ 'concrete' => [ 'driver' => 'c5_pdo_mysql', 'server' => 'localhost', 'database' => 'mysite_db', 'username' => 'myuser', 'password' => 'secret', 'charset' => 'utf8mb4', ], ], ]; Environment variables can be set via .env (do not commit this file to the repository).
CLI Commands for Administration
After installation, it is helpful to master the basic commands:
# Clear cache ./vendor/bin/concrete5 c5:cache:clear # Install a package ./vendor/bin/concrete5 c5:package:install my-package # Create a user ./vendor/bin/concrete5 c5:user:add admin2 [email protected] Password123 # Rebuild search index ./vendor/bin/concrete5 c5:index:sites Which Security Settings Are Critical?
From our experience: always disable debug mode in production, configure SMTP for emails (otherwise forms won't work), enable Full Page Caching in Dashboard → System & Settings → Cache & Speed. Also set up robots.txt and canonical URLs in the SEO & Statistics section.
What Is Included in the Concrete CMS Setup Service?
We provide:
- Server installation and configuration (Nginx/Apache, hosting selection);
- Database creation and initial content import;
- Caching setup (Redis, Memcached);
- SMTP and external service integration (CAPTCHA, CDN);
- SEO parameter configuration (canonical, robots, sitemap);
- Administration and maintenance instructions.
Our engineers are certified specialists with years of experience in Concrete CMS. We guarantee stable site operation after launch. Contact us to discuss your project or get a consultation right now.
| Parameter | Minimum Requirements | Recommended Requirements |
|---|---|---|
| PHP | 7.4 | 8.1–8.2 |
| MySQL | 5.7 | 8.0 |
| RAM | 512 MB | 1 GB+ |
| CPU | 1 core | 2+ cores |
Additional recommendation: for large projects, use PHP 8.1 or higher—this yields up to 30% performance improvement over 7.4. Set up Redis for caching—page generation speed increases 3 times. If you need professional setup, contact us—we will help avoid typical mistakes.
-
c5:cache:clear—flushes all caches (required after updates). -
c5:package:install—installs packages (themes, blocks). -
c5:user:add—creates a new user (for admins). -
c5:index:sites—rebuilds the search index.
Start with our deployment method—save hours and avoid common pitfalls. Order the service, and we will configure everything for your project.