Joomla Hosting Problems in 2026 and How to Fix Them (Joomla 5 & 6)
Most Joomla “hosting problems” come down to five things: the PHP version, PHP limits, file permissions, a slow or overloaded server, and missing backups. Here is how to spot each one and fix it, with the requirements for Joomla 5 and 6. 1. PHP and database version too old Joomla PHP Database Joomla 5 8.1
Abhilash SahooFounder & CEO, Infyways- Published
- Updated
- Reading time
- 2 min read
On this page 8 sections
Most Joomla "hosting problems" come down to five things: the PHP version, PHP limits, file permissions, a slow or overloaded server, and missing backups. Here is how to spot each one and fix it, with the requirements for Joomla 5 and 6.
1. PHP and database version too old
| Joomla | PHP | Database |
|---|---|---|
| Joomla 5 | 8.1 or newer (8.2/8.3 recommended) | MySQL 8.0.13+, MariaDB 10.4+, PostgreSQL 12+ |
| Joomla 6 | 8.3 or newer (8.4 recommended) | MySQL 8.0.13+, MariaDB 10.6+ recommended, PostgreSQL 14+ |
Symptoms: the update to the next major is never offered, or a white screen after an update. Change PHP in cPanel → Select PHP Version or MultiPHP Manager. Current figures are in the Joomla technical requirements.
2. PHP limits too low
Failed extension installs, stalled updates and "Allowed memory size exhausted" errors usually mean memory_limit, upload_max_filesize or max_execution_time is too low. Recommended values and where to change them: Joomla PHP.ini settings.
3. File permissions and ownership
Folders should be 755 and files 644, owned by the account PHP runs as. "Unable to write" or "could not open archive" errors during install point here. System → System Information → Folder Permissions shows which folders are not writable. Never set 777.
4. Slow server
Check Time To First Byte in PageSpeed Insights. If the server takes more than about 600 ms before sending anything, caching and image fixes will not be enough; enable OPcache, use PHP-FPM and HTTP/2 or HTTP/3, and move off overloaded shared hosting if needed. Site-side fixes are in how to speed up Joomla and caching in Joomla.
5. Rewrite and .htaccess errors
A 500 error after enabling URL rewriting means the server does not allow your .htaccess rules or mod_rewrite is off. See the Joomla .htaccess guide and Joomla 500 error on mod_rewrite.
6. No backups or no off-site copy
Host backups are often kept on the same server and for only a few days. Keep your own copies off the server with Akeeba Backup; see how to back up Joomla.
What to look for in Joomla hosting
- PHP 8.3+ available, with OPcache, and an easy PHP version switcher
- MySQL 8 or MariaDB 10.6+
- SSH or at least SFTP access, and cron jobs
- Daily backups you can download
- HTTP/2 or HTTP/3 and free SSL
Hosting changes made the site slow, broken or hacked? Our Joomla support and maintenance team can audit the server and the site.
Frequently asked questions
Filed under Joomla
