It appears GoDaddy no longer supports multi-domain
php.ini files. Instead, one has to put an
ini file at the root level of each hosted domain.
For the primary domain, the
ini file would go in
For AddOn Domains, the
ini file would go in
~/public_html/[AddOn Domain]/. For instance, if the domain for the AddOn Domain was “example.com”, the file path would be
As for what the
ini file should be named, that’s a whole other thing that depends on the version of PHP you’re running and the server OS. I usually start off trying
.user.ini and go from there.
For any plan over Economy, GoDaddy offers the ability to host multiple sites within a single directory (also known as “AddOn Domains“).
The primary site lives at the root of the hosting directory (
~/public_html/); all non-primary sites live within subdirectories in this same directory (e.g.
Only a single
php.ini file, located in the hosting directory, will be applied. This can create problems, particularly when different sites need different configurations.
One example of this is WordFence. In order to configure the WordFence Web Application Firewall (WAF), WordFence recommends prepending the WAF to the
php.ini, but following the default instructions will do so only for the primary domain.
To prepend the WAF to all domains (including AddOn Domains) we have to use the
HOST directive in the
[HOST=primary_domain.com] auto_prepend_file = '/path/to/primary_domain/wordfence-waf.php' [HOST=addon_domain1.com] auto_prepend_file = '/path/to/addon_domain1/wordfence-waf.php' [HOST=addon_domain2.com] auto_prepend_file = '/path/to/addon_domain2/wordfence-waf.php'
The WAF file paths can be obtained via the default configuration instructions for each WordPress site being hosted. (Be sure to confirm these paths before adding them to the
php.ini or you’ll get, at best, a
500 Internal Server Error on all sites. Doh!)
Once you’ve updated the
php.ini, log into the primary domain’s cPanel account, kill all PHP processes, then output
phpinfo() for each site and confirm the
auto_prepend_file value matches the path for the primary site (
'/path/to/primary_domain/wordfence-waf.php' in my example above).
Note: If you do this for any AddOn Domains, you need to do it for all of them.