Published on: October 11, 2014 by Vipin R.N
An error is thrown while trying to run cpanel wordpress auto install through cPanel → WordPress Auto Installer (Site Software addon available for WHM/cPanel servers)
“There is already public_html install of this addon”
WordPress Auto Installer
This is a cPanel packaged module for installing and managing WordPress installations. The advantage of installing such scripts through Auto installers are that, they can be managed or upgraded (when latest versions are available) or removed with a click. Users need not be aware of the back-end operations while doing all this. Other popular script install applications with cPanel are Softaculous and Fantastico De Luxe. Hundreds of applications can be managed through this.
The user was trying to install WordPress on his main domain (mydomains.com). He has already installed WordPress on one of his addon domains (mdomain.com) using the Auto Installer.
There should be no WordPress installation in the main domain’s document root, which is public_html.
Any Script installers like Site Software cPanel, Softaculous, Fantastico De Luxe uses certain files for storing the information on installing scripts. By referring this file, it determines whether a domain or its document root contains a script which is already installed. Following are the information on such files :
|Script Installer||Path of the script information file|
|Fantastico De Luxe||/home/user/.fantasticodata/installed_in_root.php|
|cPanel Site Software Addon||/home/user/.cpaddons/filename.yaml *|
* Actual filename varies based on applications,
There were no WordPress files in this user’s public_html directory so its not the case anyway.
Next thing to be checked is the File where Site Software Addon stores information on the scripts installed.
Unlike Softaculous or Fantasctio De Luxe, Site Software Addon (WordPress Auto Installer here) leaves a dedicated YAML file for each script.
There was only a file in /home/user/.cpaddons directory, it was labeled as cPanel::Blogs::WordPress.0.yaml which was related with the WordPress install on the addon domain brazilianjiujitsu.lv. However its
worth to check this file :
_default_charset_latin1: DEFAULT CHARSET=latin1
. . . .
Parameters to watch
Its confirmed that this file is not conflicting the WordPress installation on the main domain mydomains.com. As mentioned before there were no WordPress files in that addon domain.
So what would be causing it ?
The reason looked super silly when I came to know what caused it. But it costed me around 1 hour to realize that
Those YAML files are bound with a hierarchy, which means the existing file name cPanel::Blogs::WordPress.0.yaml should belong to the script information of the main domain maindomain.com, whereas it actually stored the information for its addon domain mdomains.com.In general, *.0.yaml belongs to the main domain and the rest for addon domains in the order of the scripts installed.
I’ve renamed the existing file cPanel::Blogs::WordPress.0.yaml to cPanel::Blogs::WordPress.1.yaml. After this I’ve installed WordPress in the main domain without any issues. A new file cPanel::Blogs::WordPress.0.yaml was created with the information on the main domain.
Category : cPanel, Howtos, Troubleshooting