Joomla is still one of the most widely used CMSs in Uzbekistan: government bodies, schools, colleges and many small businesses run their sites on it. The trouble is that such sites are often launched once and then left untouched for years. An outdated Joomla core with old extensions is the easiest possible target for attackers. So choosing hosting for Joomla is not only about disk space, but about the right PHP environment, a proper database and a working routine for regular updates.
What Joomla needs from your hosting
Each major Joomla release has its own minimum requirements. Joomla 5, for example, needs PHP 8.1 or newer, while Joomla 3 does not fully work on PHP 8. Always check the official "Technical Requirements" page on joomla.org, because the numbers change with every major release. It also matters that your hosting lets you switch between PHP versions, since upgrading an old site usually means raising the PHP version step by step.
You need a current MySQL or MariaDB version and the PHP extensions json, mysqli or pdo_mysql, gd or imagick, zip, intl and mbstring. Without them an install or update can stop halfway. In ISPmanager you can review and enable them in the PHP settings. Default limits are often too tight for Joomla, so a reasonable starting point for a mid-sized site is:
memory_limit = 256M
upload_max_filesize = 32M
post_max_size = 32M
max_execution_time = 120
output_buffering = Off
First settings after installation
Turn on search-friendly URLs first: rename htaccess.txt in the site root to .htaccess and enable "URL Rewriting" in Global Configuration. Links like index.php?option=... become short readable paths.
cd ~/www/example.uz
mv htaccess.txt .htaccess
Then enable "Force HTTPS" for the entire site, but only after an SSL certificate is installed, otherwise the site will stop loading. On sayt.uz hosting the free Let's Encrypt certificate renews automatically, so you only need to switch HTTPS on once. Set error reporting to "None" or "System Default" so visitors never see raw error messages.
Joomla 4 and 5 include Scheduled Tasks for update checks, session cleanup and similar jobs. By default they run when visitors arrive, which is unreliable on a low-traffic site, so a real cron job is better:
*/15 * * * * php /var/www/USER/data/www/example.uz/cli/joomla.php scheduler:run --all
Adjust the path to your actual site folder and test the command over SSH before adding it.
A safe update routine
Consider a private school in Tashkent whose site was built on Joomla 3 in 2019 and never updated. One day foreign spam links appear on the homepage. Even after the cleanup, the real question remains: how do you move the site to a supported version? The answer is always the same: full backup first, then a test, and only then the live site.
- Take a full backup of files and database, for example with Akeeba Backup or the hosting panel's backup tool.
- Restore a copy on a subdomain such as
test.example.uzand update there first. - Update all extensions to the latest release of the current branch, then use the Pre-Update Check to see which are compatible.
- Update the core and check key pages, forms and the admin panel.
- If everything works, repeat the process on the live site.
Major jumps, such as 3 to 4, mostly break on templates and old extensions, and some will need replacements. Joomla 4 and later also ship a CLI that helps during maintenance:
php cli/joomla.php core:check-updates
php cli/joomla.php site:down
php cli/joomla.php cache:clean
php cli/joomla.php site:up
Run php cli/joomla.php list to see the commands available in your version.
Making security a habit
Protect the administrator login, enable two-factor authentication and remove admin accounts nobody uses. Uninstall unused extensions completely rather than just disabling them, because leftover files can still be exploited. Keep permissions sane: 755 for folders, 644 for files, and never 777.
find . -type d -exec chmod 755 {} \;
find . -type f -exec chmod 644 {} \;
If the site is already compromised or you are unsure about doing the upgrade yourself, open a ticket in the sayt.uz cabinet and include the Joomla version and the list of installed extensions so the issue can be analysed faster.