Running separate WordPress installs for every small client site or internal tool burns through server memory fast, and updating the same plugins across five dashboards gets old real quick. Switching to a subdomain multisite network (site1.example.com, site2.example.com) fixes that, but doing it on Hostinger comes with a few traps.
The first time I set this up on hPanel, my subdomains immediately choked on ERR_TOO_MANY_REDIRECTS and invalid SSL warnings. Hostinger runs an Nginx reverse proxy in front of Apache (or LiteSpeed depending on your plan tier), so if your wildcard DNS and certificates aren’t set up before you touch the database, you’ll hit a wall fast.

Wildcard DNS Configuration in Hostinger hPanel
A subdomain network needs a catch-all wildcard DNS record. If you skip this, every single time you add a child site in Network Admin, your browser will throw an NXDOMAIN error until you manually add another A record.
Head into your Hostinger hPanel, go to Domains > your domain > DNS / Nameservers, and check your existing primary A record so you have your server’s IPv4 address ready.
Now create a new record:
- Type: A
- Name:
* - Points to: Your server IP (identical to your root
@record) - TTL: 300 (or the default 14400)
If your DNS sits somewhere else, check out our guide to wildcard subdomain DNS in Namecheap first. Once added, test that the wildcard resolves from your terminal:
dig randomteststring123.yourdomain.com +shortIf you get your Hostinger IP back, the wildcard is working. With a low TTL, it should resolve in a couple of minutes.
Activating Multisite in wp-config.php
WordPress hides its network setup screens by default. You have to explicitly tell the core codebase you want multisite enabled before it exposes the tools.
Jump in via SSH or open Files > File Manager in hPanel. Open public_html/wp-config.php and look for this line near the bottom:
/* That's all, stop editing! Happy publishing. */Drop this single line right above that comment:
/* Enable Multisite */
define('WP_ALLOW_MULTISITE', true);Save it. Don’t add any other multisite constants yet. Those come later, once WordPress generates the database tables.
Running the Network Setup Installation
Before touching the network installer, deactivate all your plugins. If anything is active, WordPress flat-out blocks the setup wizard to prevent table conflicts.
- Log into your WP dashboard (
example.com/wp-admin/). - Head to Plugins > Installed Plugins, check all, select Deactivate from bulk actions, and apply it.
- Go to Tools > Network Setup.
Pick Sub-domains. If your site has been live for more than a month, WordPress will complain and suggest sub-directories instead. Ignore it—keep Sub-domains selected.
Check your Network Title and Admin Email, then hit Install. WordPress spins up six new tables in your database:
wp_blogswp_blogmetawp_sitewp_sitemetawp_signupswp_registration_log
Updating .htaccess and wp-config.php for Subdomain Routing
Once the install finishes, WordPress outputs two code snippets: one for wp-config.php and one for .htaccess. These tell your server to route all dynamic subdomain traffic straight through the index controller instead of looking for actual subfolders on disk.
Open public_html/wp-config.php again. Swap out the define('WP_ALLOW_MULTISITE', true); line you added earlier with the full generated block:
define('WP_ALLOW_MULTISITE', true);
define('MULTISITE', true);
define('SUBDOMAIN_INSTALL', true);
define('DOMAIN_CURRENT_SITE', 'yourdomain.com');
define('PATH_CURRENT_SITE', '/');
define('SITE_ID_CURRENT_SITE', 1);
define('BLOG_ID_CURRENT_SITE', 1);Then take a quick backup of public_html/.htaccess and overwrite the standard WordPress block with the multisite rewrite rules from the WordPress Network documentation:
# BEGIN WordPress Multisite
RewriteEngine On
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /
RewriteRule ^index.php$ - [L] # add a trailing slash to /wp-admin
RewriteRule ^wp-admin$ wp-admin/ [R=301,L] RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule ^(wp-(content|admin|includes).*) $1 [L]
RewriteRule ^(.*.php)$ $1 [L]
RewriteRule . index.php [L]
# END WordPress MultisiteSave both files. Log out of WordPress and log right back in. You should now see a My Sites menu in the admin bar with full access to the Network Admin panel.
Handling Wildcard SSL Certificates in Hostinger hPanel
Here’s where things usually break: your main site loads fine on HTTPS, but the second you open child.yourdomain.com, Chrome throws NET::ERR_CERT_COMMON_NAME_INVALID. That’s because Hostinger’s default Let’s Encrypt certificate only covers yourdomain.com and www.yourdomain.com.
You need hPanel to reissue the cert as a wildcard:
- In hPanel, go to Security > SSL.
- Look at the active cert. If it shows Let’s Encrypt (Standard), subdomains aren’t covered.
- Click the three dots next to the certificate and select Reinstall SSL.
- Because your
*DNS record is already resolving, Hostinger’s ACME client will automatically pick it up and issue a multi-domain SAN certificate covering*.yourdomain.com.
If child sites still give you expired or mismatch warnings after this, check our guide on how to fix SSL certificate errors on a subdomain in Hostinger to make sure the Nginx proxy reloaded the cert chain properly.
Creating Your First Child Subdomain Site
With DNS, rewrites, and SSL finally playing nice, you can spin up a site:
- Go to My Sites > Network Admin > Sites.
- Click Add New Site.
- In the Site Address (URL) field, put your subdomain slug (like
apporstaging). - Add a title and admin email, then click Add Site.
Open an incognito window and hit https://app.yourdomain.com. You should see the standard default theme right away. If it loads without styles, double-check your browser console for mixed-content HTTP asset blocks.
Debugging Cookie and Redirect Loops (The Gotcha)
The single most annoying issue on Hostinger multisite setups is getting booted from subdomain.example.com/wp-admin with the error: “Cookies are blocked or not supported by your browser.”
This happens because the root domain sets cookies across .yourdomain.com, while the child subdomain tries to isolate its own auth cookies. They clash, you get stuck in a login redirect loop, and Hostinger’s edge cache happily caches that broken state.
To fix it, open wp-config.php and paste these cookie constants right below your multisite configuration:
define('ADMIN_COOKIE_PATH', '/');
define('COOKIE_DOMAIN', '');
define('COOKIEPATH', '');
define('SITECOOKIEPATH', '');Leaving COOKIE_DOMAIN empty forces WordPress to scope auth cookies strictly to the incoming host header instead of splashing them across the whole parent domain. It solves the login loop instantly without core file modifications.
After saving, flush Hostinger’s server cache. Go to hPanel > Speed > Web Cache and hit Flush Cache so stale auth redirects get dumped from RAM.
Performance Tuning: Redis and WP-Cron for Network Scale
Multisite hammers MySQL way harder than a single site. Every single page hit queries wp_blogs and wp_sitemeta before it even touches post data. On shared or cloud plans, that overhead can easily tack 300ms to 600ms onto your TTFB.
First, get Redis running. Follow our guide to configure Redis object cache in WordPress on Hostinger. Caching site metadata in memory eliminates dozens of duplicate database queries on every sub-site visit.
Second, stop using default WP-Cron. Out of the box, multisite tries to execute cron events across network child sites when visitors hit pages, which spikes CPU usage. Disable it in wp-config.php:
define('DISABLE_WP_CRON', true);Then hook up a real system cron job in hPanel under Advanced > Cron Jobs. Check our tutorial on how to replace WP-Cron with a real system cron job on Hostinger for the exact CLI command to loop through your sub-sites on a 15-minute interval.
Frequently Asked Questions
Can I map custom domains to subdomains later?
Yes. WordPress handles native domain mapping fine without extra plugins now. Go to Network Admin > Sites, edit the site, and update the Site Address (URL) from https://client.yourdomain.com to https://clientdomain.com. Just make sure the client domain has an A record pointing to your Hostinger server IP.
Why do my subdomains return a 404 Not Found error?
Usually, this means Apache or LiteSpeed isn’t reading your .htaccess rewrites. Confirm your .htaccess has the exact multisite block from above and its file permissions are 644. If you’re on an OpenLiteSpeed plan, restart the web server through hPanel so it re-reads the rewrite rules.
Do child sites share the same plugins and themes?
Yes. They share the same code on disk inside wp-content/plugins and wp-content/themes, which saves substantial storage. Each sub-site still has its own isolated options, active configurations, and content tables in the database.
With the core network and SSL running clean, get object caching configured next so your database doesn’t choke as you spin up more sub-sites.

