Login/Register

Troubleshooting Guide

The Installatron Repair Utility is designed to fix most problems that can occur with Installatron Plugin. This utility can be executed any time difficulties are experienced. There is no harm in executing the utility; it's always the first thing to try.



Installatron Plugin Linux/Unix/FreeBSD

To perform a repair on Linux/Unix/FreeBSD, run these four commands as the root user:

rm -fr /usr/local/installatron/lib /usr/local/installatron/etc/php.ini
curl -O https://data.installatron.com/installatron-plugin.sh
chmod +x installatron-plugin.sh
./installatron-plugin.sh -f --quick
Tip: To run repair in interactive mode, remove -f from the last command.

Installatron Plugin Windows

To perform a repair on Windows, re-run the installatron-plugin.exe wizard.



Installatron Server Linux/Unix/FreeBSD

To perform a repair on Linux/Unix/FreeBSD, run these four commands as the root user:

rm -fr /usr/local/installatron/lib /usr/local/installatron/etc/php.ini
curl -O https://data.installatron.com/installatron-server.sh
chmod +x installatron-server.sh
./installatron-server.sh -f --quick
Tip: To run repair in interactive mode, remove -f from the last command.

Installatron Server Windows

To perform a repair on Windows, re-run the installatron-server.exe wizard.

If problems persist...

Known Issues


Installatron Errors


Task Errors


Application Errors




Frequently Asked Questions

Installatron displays a 401 error (cPanel only)

SOLUTION

Double check that the "Installatron" feature is enabled within WHM's Feature List tool for the feature lists where it should be enabled.

Within WHM's Feature List tool, the first entry ("Installatron") refers to the Installatron system itself and must be enabled to activate Installatron, and the second entry ("Installatron Widget") activates the dashboard section that lists top apps and installed apps right on the main cPanel menu.

Tasks never progress beyond "Waiting..."

SOLUTION

Try clearing the task queue by executing this command as root:

rm -fr /var/installatron/tasks/*

Tasks never complete or terminate prematurely

CAUSE

A crontab process may be active that is designed to terminate PHP processes that are executing "too long".

SOLUTION

Disable the offending crontab process, or replace it with a crontab process that grants immunity to Installatron-created processes.

The below bash code, when executed as a crontab process every so often, will only kill PHP processes that have been executing longer than 600 seconds and show up in the output of "ps -eo command" as containing "/usr/bin/php". This will work without modification on most fastcgi environments. Feel free to modify this code to match your environment.

ps -eo uid,pid,lstart,command |
    tail -n+2 |
    while read PROC_UID PROC_PID PROC_LSTART_WDAY PROC_LSTART_MONTH PROC_LSTART_DAY PROC_LSTART_TIME PROC_LSTART_YEAR PROC_COMMAND; do
        SECONDS=$[$(date +%s) - $(date -d"$PROC_LSTART_WDAY $PROC_LSTART_MONTH $PROC_LSTART_DAY $PROC_LSTART_TIME $PROC_LSTART_YEAR" +%s)]
        if [[ "$PROC_COMMAND" == */usr/bin/php* ]]; then
	        if [ $PROC_UID -gt 0 -a $SECONDS -gt 600 ]; then
    	        echo $PROC_PID
        	fi
        fi
     done |
     xargs kill

Installed applications are missing from My Applications

CAUSE

If installed applications do not appear at the My Applications tab then there is an error within cached data. This can happen if a user is moved to a server with a different configuration than the one the installs were created on. Typically no action is necessary when this occurs; the issue will automatically correct itself the next time the daily Installatron Update process executes.

SOLUTION

Execute these commands:

/usr/local/installatron/repair -f --quick
/usr/local/installatron/installatron --repair --recache
/usr/local/installatron/installatron --send-update-report

SECONDARY SOLUTION (INSTALLATRON PLUGIN ONLY)

For Installatron Plugin only: If the first solution does not remedy the problem, execute these commands:

/usr/local/installatron/repair -f --quick
mv -f /var/installatron/data.db /var/installatron/data.db.bak20170721
rm -f /var/installatron/data.db-*
/usr/local/installatron/installatron --repair --recache
/usr/local/installatron/installatron --send-update-report

The 'Installatron Applications Installer' or 'Installatron Admin' links go to a blank page

INSTALLATRON SERVER SOLUTION

Execute these commands:

/usr/local/installatron/repair -f --quick
/usr/local/installatron/installatron --repair --recache
/usr/local/installatron/installatron --send-update-report

INSTALLATRON PLUGIN SOLUTION

Execute these commands:

/usr/local/installatron/repair -f --quick
mv /var/installatron/data.db /var/installatron/data.db.bak20170721
rm -f /var/installatron/data.db-*
/usr/local/installatron/installatron --repair --recache
/usr/local/installatron/installatron --send-update-report

Unable to connect to any licensing server

Firewall configurations that whitelist addresses must allow outgoing port 80 connections to these addresses.

dal01.installatron.com (North America - Dallas)
dal02.installatron.com (North America - Dallas)

Based on a server's geographic location, or for added redundancy, additionally allowing connections to these addresses is recommended. When multiple addresses are available the closest geographically will always be tried first.

nue01.installatron.com (Europe - Nuremberg)
sng01.installatron.com (Asia - Singapore)
syd01.installatron.com (Oceania - Sydney)

It's also possible to create an internal mirror for your company following the FAQ here: How do I create an Installatron Fast Update server?

Unable to download the remote file `https://data.installatron.com/manifest.md5'.

CAUSE

The SSL connection to data.installatron.com could not be established. To verify, test with this command:

curl -v https://data.installatron.com/manifest.md5

SOLUTION 1

If the server is older, the server root certificates may be out of date.

SOLUTION 2

If you're unable to get the server to accept this certificate, add a --no-check-certificate argument to the original command.

FileSystem::mkdir(/path/to/installed/application/directory)

CAUSE

This type of error can sometimes occur when an account is out of available disk space. However, in most cases a more graceful error is displayed.

SOLUTION

Check that the web hosting account has enough available disk space. If additional space is required, contact your service provider directly to add additional disk space.

2011-09-19T04:57:55-04:00 FAILURE [2] http://yoursite.com/installdir/anyfile.php

CAUSE

A .htaccess file is likely interfering with a HTTP request.

SOLUTION

Check the installation directory and parent directories (public_html) for a .htaccess file that could interfere with requests to the aforementioned URL. You either can fix the .htaccess file or temporarily rename it and try again.

You have exceeded the maximum allowed databases

A few variations of these errors exist. The errors are returned from the control panel software verbatim.

CAUSE

This happens when the control panel software is unable to create a database on behalf of Installatron. Most likely this means the account has no databases remaining.

SOLUTION

An existing database can be selected for the install by choosing the "Let me manage the database settings" option on the Database step, or most likely additional databases can be purchased.

Unable to get list of databases. There is a communication problem with the control panel API.

A few variations of these errors exist. The errors are returned from the control panel software verbatim.

CAUSE

This happens when Installatron is unable to retrieve a list of user's database via the control panel's plugin API.

GENERAL SOLUTION

Typically logging out of the control panel and re-trying the task will solve the problem.

DIRECTADMIN SOLUTION

Try changing the "Fetch/HTTP driver" in Administration > Settings. It may be that the default driver is not suitable for your server setup. A CURL binary should be selected whenever possible.

If the the control panel uses https:// then it may be that the CURL options lack functional OpenSSL support. This can be tested for CURL binaries with:

curl -v -k 'https://127.0.0.1:2222'

Installatron displays an "encoded", blank, or non-loading page

Error: All loaders have failed

Error: PHP is not installed

CAUSE

By default Installatron uses a system PHP instance. In the vast majority of cases this works flawlessly. However, in rare cases this instance may not be compatible with Installatron.

When this occurs, compiling a dedicated PHP instance just for Installatron is the most reliable solution.

SOLUTION

Try installing a dedicated PHP instance just for Installatron. The PHP instance used by website owners will not be modified.

mkdir -p /usr/local/installatron
cd /usr/local/installatron
curl -O http://php.net/distributions/php-5.5.37.tar.gz
tar xzf php-5.5.37.tar.gz
cd php-5.5.37
./configure --prefix=/usr/local/installatron/php --disable-libxml --disable-dom --disable-simplexml --disable-xml --disable-xmlreader --disable-xmlwriter --enable-posix --enable-mbstring --enable-ftp --enable-sockets --without-pear --without-iconv --with-zlib --with-gd --with-jpeg-dir --with-png-dir --with-mysql=mysqlnd --with-mysqli=mysqlnd --with-pdo-mysql=mysqlnd --with-gettext
make
make install
cd ..
rm -fr php-5.5.37 php-5.5.37.tar.gz /usr/local/installatron/bin/php

Next, follow the steps at the top of this page to execute a "repair" of Installatron.

That's it! Installatron should now be working.

Error: mysql database connection failed: No such file or directory.

CAUSE

There is a problem communicating with MySQL.

SOLUTION

If databases are actually being created, try specifying a MySQL socket value in /usr/local/installatron/etc/php.ini. For example:

mysql.default_socket = /var/lib/mysql/mysql.sock

Technical Error: DBD::mysql::st execute failed: There is no such grant defined…

CAUSE

The cPanel API failed to create a database for Installatron Plugin.

SOLUTION

Check if either of the below values exist in /etc/my.cnf:

skip-name-resolve 
skip-host-cache

If either value exists, comment the value out, restart mysql, and then try the action within Installatron Plugin again. If the problem is still not solved, check if the user has their own my.cnf file within their home directory.

open3: exec of file - failed at /usr/local/cpanel/bin/register_cpanelplugin line 33

CAUSE

The RPM package "file" is missing.

SOLUTION

Install the missing RPM package:

yum install file

Then re-execute the Installatron Repair Utility at the top of this page.

Installatron doesn't work with PHP7 and PHP7.1

CAUSE

Installatron's core does not yet support PHP 7.x internally. This has been a long term ongoing project and will be released as a major update when it's ready.

Note that the application's that are installed by Installatron each support PHP 7.x on an application-by-application basis.

SOLUTION

Use this workaround for now.

Alternatively, if you already have a secondary PHP (<7.0) instance that you would prefer Installatron to use, rather than install a dedicated PHP5.5 instance, you can symlink this to the PHP binary:

/usr/local/installatron/bin/php
And then run:
/usr/local/installatron/repair -f --quick

A test of the selected domain has failed

CAUSE

Load your website into a couple of web browsers (eg. Firefox and Chrome) and consider the following;

Does your website say that your webhosting account is suspended?

Does your website say that your website isn't "redirecting properly"?

SOLUTION

Contact your webhosting provider or server administrator and ask about unsuspending your account.

Redirecting problems are usually caused by redirection-loops, where a redirection points back to itself or a redirection points to somewhere that points back to the original page. Redirections are sometimes set up through a "Redirection" tool in your webhosting control panel or manually using files named ".htaccess" in your account's files. The redirection problem will need to be fixed before Installatron can do anything further with the application.

A test of the selected domain has failed (continued)

CAUSE

First, see the previous entry to check that the domain is working correctly.

While Installatron doesn't require domains to resolve prior to use, Installatron does check for any domain misconfiguration that would prevent the installed application from functioning, including IP mismatches and firewall problems.

SOLUTION

Check your /var/installatron/logs/fetch* log files for information on why the tests failed.

The test can be disabled server-wide by running this as root:

echo "domaincheck=no" >> /usr/local/installatron/etc/settings.ini

However, we don't recommend disabling the test. It's better to determine why the domain isn't working.

INSTALLATRON SERVER API SOLUTION

To enable interaction with non-resolving domains, including the "url-ip" argument with Installatron Server API queries, which will inform Installatron Server where it should resolve the domain.

A test of the selected domain has failed (HTTP error: 0) -- [http code=0; timeout=7]

BACK STORY

Installatron tests your domain before it proceeds with any application-related task (install, update, clone, etc). It tests the domain by creating a file called "[i]deleteme.????.php[/i]" (where [i]????[/i] is a series of random characters) in the application's directory and then runs the script over HTTP using the domain. For example, the file might be created here:

~/public_html/deleteme.chakd2oh.php

And it will be run by loading something like:

http://www.yourdomain.com/deleteme.chakd2oh.php

CAUSE

If Installatron doesn't receive the expected answer from the [i]deleteme.????.php[/i] script then you will receive this error and the task will be aborted. The actual path, URL, and filename will be included in the error message.

A [i][http code=0; timeout=7][/i] at the very end of the error message means that when Installatron tried to run the [i]deleteme.????.php[/i] script it wasn't able to make a connection with your server -- and to be clear here; Installatron is making the call from the same server that it's trying to make the call to. It's a HTTP call that it should be able to make.

The likely cause is that your server's [b]own IP address[/b] or [b]domain[/b] (or even [b]127.0.0.1[/b] or [b]localhost[/b]) is blacklisted by the server itself or by the MySQL server.

SOLUTION

Ask your webhosting provider or server administrator if one of these addresses might be blacklisted.

ADDDB API failure

CAUSE

Installatron is unable to communicate with the webhosting control panel's plugin API, or the plugin API is unable to communicate with the MySQL/database server.

SOLUTION

Contact your webhosting provider or server administrator and ask them to look into it for you. The /var/installatron/logs/panel_log log might be of use to them. And if the server is using MariaDB they should check that it is enabled as a feature in the control panel.

ADDUSER API failure

CAUSE

Installatron is unable to communicate with the webhosting control panel's plugin API, or the plugin API is unable to communicate with the MySQL/database server.

SOLUTION

Contact your webhosting provider or server administrator and ask them to look into it for you. The /var/installatron/logs/panel_log log might be of use to them. And if the server is using MariaDB they should check that it is enabled as a feature in the control panel.

On some cPanel/WHM configurations this error can be caused by usernames that are considered too long.

Compression failed -- Import

BACK STORY

Installatron is trying to create an archive comprising the application's files and database but the compression process has failed.

CAUSE

If your webhosting account is low on disk space then this is likely due to the process running out of disk space during compression. The process generally disk space the equivalent of the current application size (files+database) plus an additional 30% overhead and it requires this space at both the Source account and Destination accounts.
(eg. if the combined disk space+database is currently 12MB, you need 16MB free space on both source and destination accounts--or 32MB if it's the same account--in order to perform this task)

If enough disk space is available then the compression process might be timing out, which could happen if the application is especially large. When a process takes longer than a server time-limit the server will simply kill the process.

SOLUTION

Check your disk usage and limit from your webhosting control panel. If disk space is low then you might be able to free some space by uninstalling applications that you don't need (be careful not to uninstall something you use!), otherwise you will need to speak to your webhosting provider about increasing your disk space quota.

There are three PHP values that might also be involved in a time-out:

Values of 360 are good starting points for all three.
If your webhosting control panel allows you to edit your PHP configuration then you can possibly change these values from there, otherwise you'll need to ask your webhosting provider to change those values for you. And the MySQL value might be something that only your provider can change.
Ideally, you'll change these values on both the Source and Destination servers, but change them where you can and see if that helps.

Successfully detected the source installed application's database information, but the information isn't working.

BACK STORY

During a local or remote [i]Import[/i], Installatron here has found the application's configuration file and has been able to parse the application's database information from the config, but when it then attempted to connect to the server's MySQL database server using those newly-extracted details it wasn't able to connect.

CAUSE

If the final part of the error contains the phrase "No such file or directory", please ask your webhosting provider or server administrator to run this fix.

If the final part of the error contains the phrase "Access denied" then it it's possible that your server's [b]own IP address[/b] or [b]domain[/b] (or even [b]127.0.0.1[/b] or [b]localhost[/b]) is blacklisted by the server itself or by the MySQL server.

SOLUTION

Ask your webhosting provider or server administrator if one of these addresses might be blacklisted.


[http code=301] -- CMS Made Simple

CAUSE

This is likely to be caused by a known problem between the web server "LiteSpeed" and the PHP extension "Phar".

Phar is used to install CMSMS but LiteSpeed, at the time of writing, causes an infinite redirection loop (the '301' error is a usually harmless redirection notice meaning "Moved Permanently") when using PHP's 'phar' extension. More can be found about this bug here: https://bugs.php.net/bug.php?id=71465

SOLUTION

Contact your webhosting provider or server administrator and suggest that they disable the CMSMS installer from Installatron's [i]Access Control[/i] tool in administration.

[http code=401]

CAUSE

The HTTP error code '401' means "Unauthorized".

This usually means that there is some sort of extra level of security wrapped around your website that Installatron can't get through, usually in the form of a login popup but it could also be a blacklisted IP address or domain.

You have probably forgotten the security is there because you are already logged in or your IP/domain isn't banned.

SOLUTION

Disable the security; perform the Installatron task; re-instate the security.

If you don't know where the security is coming from: check your webhosting control panel for a 'password protection' tool (this might be among the other tools, alongside Installatron, or you might find it inside the 'file manager'/'files' tool); use the 'file manager'/'files' tool to look for files named ".htaccess" (*) starting in the account's home directory and following the path to where the app is installed -- these files have the potential to block access (but they can also perform important tasks so be careful); similarly, look for directories named ".passwds/"; ask your webhosting provider or server administrator for advice.

* note that files and directories beginning with '.' might be hidden until you set '[b][x]show hidden files' somewhere first.

[http code=500] -- ClientExec

CAUSE

ClientExec requires that the PHP 'mbstring' extension is enabled.

You can check this by creating a file named "phpinfo.php" in the directory where you are trying to install the app, and give it this content:

<? phpinfo(); ?>

And you will then be able to see your PHP configuration here:

http://{YOURDOMAIN_COM}/{POSSIBLE_PATH}/phpinfo.php

Search for "mbstring" to confirm that this is the likely cause of the error.

SOLUTION

If your webhosting control panel allows you to customize your PHP configuration then you can possibly fix this from there, otherwise you will need to contact your webhosting provider or server administrator to ask them to add it for you.

[http code=500] -- Drupal

CAUSE

Drupal requires that the PHP 'mbstring' extension is enabled.

You can check this by creating a file named "phpinfo.php" in the directory where you are trying to install the app, and give it this content:

<? phpinfo(); ?>

And you will then be able to see your PHP configuration here:

http://{YOURDOMAIN_COM}/{POSSIBLE_PATH}/phpinfo.php

Search for "mbstring" to confirm that this is the likely cause of the error.

SOLUTION

If your webhosting control panel allows you to customize your PHP configuration then you can possibly fix this from there, otherwise you will need to contact your webhosting provider or server administrator to ask them to add it for you.

[http code=500] -- OrangeHRM

CAUSE

OrangeHRM requires that the PHP 'mysqli' extension is enabled.

You can check this by creating a file named "phpinfo.php" in the directory where you are trying to install the app, and give it this content:

<? phpinfo(); ?>

And you will then be able to see your PHP configuration here:

http://{YOURDOMAIN_COM}/{POSSIBLE_PATH}/phpinfo.php

Search for "mysqli" to confirm that this is the likely cause of the error.

SOLUTION

If your webhosting control panel allows you to customize your PHP configuration then you can possibly fix this from there, otherwise you will need to contact your webhosting provider or server administrator to ask them to add it for you.

[http code=500] -- Oxwall

CAUSE

Oxwall requires that the server's "/tmp" directory exists and is writable.

SOLUTION

Contact your webhosting provider or server administrator and ask them to check that the "/tmp" directory exists and that it is CHMOD 777.

If they don't wish to create this directory or make it writable to everyone then they should disable the Oxwall installer from Installatron administration » Access Control.

[http code=500] -- PrestaShop

CAUSE

PrestaShop requires PHP version 5.4 or newer.

You can check this by creating a file named "phpinfo.php" in the directory where you are trying to install the app, and give it this content:

<? phpinfo(); ?>

And you will then be able to see your PHP configuration here:

http://{YOURDOMAIN_COM}/{POSSIBLE_PATH}/phpinfo.php

You'll find the version at the top-left of the page.

SOLUTION

If your webhosting control panel allows you to customize your PHP configuration then you can possibly fix this from there, otherwise you will need to contact your webhosting provider or server administrator to ask them to upgrade it for you.

[http code=500] -- Pydio

CAUSE

Pydio requires that the PHP 'mcrypt' extension is enabled.

You can check this by creating a file named "phpinfo.php" in the directory where you are trying to install the app, and give it this content:

<? phpinfo(); ?>

And you will then be able to see your PHP configuration here:

http://{YOURDOMAIN_COM}/{POSSIBLE_PATH}/phpinfo.php

Search for "mcrypt" to confirm that this is the likely cause of the error.

SOLUTION

If your webhosting control panel allows you to customize your PHP configuration then you can possibly fix this from there, otherwise you will need to contact your webhosting provider or server administrator to ask them to add it for you.

[http code=500] -- WordPress

CAUSE

Pydio requires that the PHP 'mcrypt' extension is enabled.

You can check this by creating a file named "phpinfo.php" in the directory where you are trying to install the app, and give it this content:

<? phpinfo(); ?>

And you will then be able to see your PHP configuration here:

http://{YOURDOMAIN_COM}/{POSSIBLE_PATH}/phpinfo.php

Search for "mcrypt" to confirm that this is the likely cause of the error.

SOLUTION

If your webhosting control panel allows you to customize your PHP configuration then you can possibly fix this from there, otherwise you will need to contact your webhosting provider or server administrator to ask them to add it for you.

[http code=503]

CAUSE

The HTTP '503' error means "Server Unavailable" and this means that when Installatron tried to call a script in your account it was not able to make a successfully connection to the server (and to be clear here; the call is being make from Installatron running on the same server).

This may have been a momentary internet connection glitch, and if you were to wait a short while and then try again you might find it will now work.

If it continues to produce the same error then a possible cause is that your server's [b]own IP address[/b] or [b]domain[/b] (or even [b]127.0.0.1[/b] or [b]localhost[/b]) is blacklisted by the server itself or by the MySQL server.

Another possibility is that a process is timing out -- that is, it's taking longer than the server allows and so the server kills it. This can have the appearance, to Installatron, of a failed connection.

SOLUTION

Contact your webhosting provider or server administrator and ask them to determine if one of these addresses might be blacklisted.

If blacklisting is not the cause then try setting these PHP values:

max_execution_time=360
default_socket_timeout=360
mysql.connect_timeout=360 (can be set in php.ini or my.cnf)

If your webhosting control panel allows you to customize your PHP configuration then you can possibly change these values from there, otherwise you will need to contact your webhosting provider or server administrator to ask them to increase these values for you.

[http code=507]

CAUSE

The HTTP '507' error means that your Dropbox quota is exceeded.

SOLUTION

Check your Dropbox quota and try again when you have storage available.


A database query has failed -- CMS Made Simple

CAUSE

If the server uses the PHP suhosin extension then this is likely to be caused by a problem involving Phar.

You can check this by creating a file named "phpinfo.php" in the directory where you are trying to install the app, and give it this content:

<? phpinfo(); ?>

And you will then be able to see your PHP configuration here:

http://{YOURDOMAIN_COM}/{POSSIBLE_PATH}/phpinfo.php

Search for "suhosin" to confirm that this is the likely cause of the error.

SOLUTION

Add this line to the relevant php.ini:

suhosin.executor.include.whitelist="phar" (http://php.net/manual/en/book.phar.php)

If your webhosting control panel allows you to customize your PHP configuration then you can possibly fix this from there, otherwise you will need to contact your webhosting provider or server administrator to ask them to change this for you.

A database query has failed -- Drupal

CAUSE

Drupal requires that the PHP 'memory_limit' value is set to at least 64M.

Drupal requires that the PHP 'mbstring' extension is enabled.

Drupal requires that the PHP 'mbstring.http_input' feature is disabled.

You can check this by creating a file named "phpinfo.php" in the directory where you are trying to install the app, and give it this content:

<? phpinfo(); ?>

And you will then be able to see your PHP configuration here:

http://{YOURDOMAIN_COM}/{POSSIBLE_PATH}/phpinfo.php

Search for "memory_limit", "mbstring", and "mbstring.http_input" to confirm that one of these is the likely cause of the error.

SOLUTION

If your webhosting control panel allows you to customize your PHP configuration then you can possibly fix this from there, otherwise you will need to contact your webhosting provider or server administrator to ask them to change them for you.

A database query has failed -- Elgg

CAUSE

Elgg has a minimum requirement of PHP version 5.5.9.

You can check this by creating a file named "phpinfo.php" in the directory where you are trying to install the app, and give it this content:

<? phpinfo(); ?>

And you will then be able to see your PHP configuration here:

http://{YOURDOMAIN_COM}/{POSSIBLE_PATH}/phpinfo.php

You'll find the version at the top-left of the page.

SOLUTION

If your webhosting control panel allows you to select your PHP version then you can possibly fix this from there, otherwise you will need to contact your webhosting provider or server administrator to ask them to change it for you.

A database query has failed -- Group Office

CAUSE

Group Office requires that the PHP 'pdo_mysql' extension is installed.

Group Office requires that the PHP 'mysqli' extension is installed.

You can check this by creating a file named "phpinfo.php" in the directory where you are trying to install the app, and give it this content:

< phpinfo(); ?>

And you will then be able to see your PHP configuration here:

http://{YOURDOMAIN_COM}/{POSSIBLE_PATH}/phpinfo.php

Search for "pdo_mysql" and "mysqli" to confirm that this is the likely cause of the error.

SOLUTION

If your webhosting control panel allows you to select your PHP version then you can possibly fix this from there, otherwise you will need to contact your webhosting provider or server administrator to ask them to add these for you.

A database query has failed -- Live Site

CAUSE

Live Site requires that a PHP version lower than 5.5.

Live Site requires that the PHP 'mbstring' extension is enabled.

You can check this by creating a file named "phpinfo.php" in the directory where you are trying to install the app, and give it this content:

<? phpinfo(); ?>

And you will then be able to see your PHP configuration here:

http://{YOURDOMAIN_COM}/{POSSIBLE_PATH}/phpinfo.php

The PHP version is found at the top-left of the page, and search for "mbstring" to confirm that this is the likely cause of the error.

SOLUTION

If your webhosting control panel allows you to customize your PHP configuration then you can possibly fix this from there, otherwise you will need to contact your webhosting provider or server administrator to ask them to change them for you.

A database query has failed -- Magento

CAUSE

Magento requires that a PHP version lower than 7.0. At the time of writing (see here for the latest information), Magento supports these PHP versions:

5.5.22–5.5.x
5.6.x
7.0.2 
7.0.6–7.0.x

Magento requires these PHP extensions and modules:

curl, gd, intl, [b]mbstring[/b]*, mcrypt, mhash, openssl, pdo_mysql, simplexml, soap, xml, xsl, zip, json**, iconv**
* some webhosting providers will not include this by default
** required only for PHP 7

Magento requires that the PHP 'proc_close()' function is enabled.

Magento requires that the PHP 'php_uname()' function is enabled.

Magento requires that the PHP 'always_populate_raw_post_data' value is set to "-1" to disable it.

Magento requires that the PHP 'max_execution_time' value is set to more than the default 30 -- we recommend 360.

Magento requires that the PHP 'memory_limit' value is set to at least 256M.

Magento requires that the PHP 'sql.safe_mode' value is set to "Off" to disable it.

Magento does not usually install when PHP's 'open_basedir' restrictions are in use.

You can check these extensions, functions, and values by creating a file named "phpinfo.php" in the directory where you are trying to install the app, and give it this content:

<? phpinfo(); ?>

And you will then be able to see your PHP configuration here:

http://{YOURDOMAIN_COM}/{POSSIBLE_PATH}/phpinfo.php

The PHP version is found at the top-left of the page, and search for the other values and extension names to determine if any of them are the likely cause of the error.

Magento requires MySQL 5.6+ (or the MariaDB equivalent). The MySQL version can probably be found in your webhosting control panel (under "server information" or similar) otherwise you will need to ask your webhosting provider.

Magento requires Composer be installed on the server.

Magento requires read/write access to the server's /tmp directory.

SOLUTION

If your webhosting control panel allows you to customize your PHP configuration then you can possibly fix any of the PHP-related problems from there, otherwise for a PHP-related problem will need to contact your webhosting provider or server administrator to ask them to change them for you.

If your MySQL version is not sufficient to run Magento then you will need to ask your webhosting provider or server administrator to update it for you.

Composer errors are something only your webhosting provider or server administrator can check and address.

A database query has failed -- Omeka

CAUSE

Omeka requires that Apache's 'mod_rewrite' module is installed or your server's equivalent.

Omeka requires that the PHP 'pdo_mysql' extension is installed.

You can check this by creating a file named "phpinfo.php" in the directory where you are trying to install the app, and give it this content:

<? phpinfo(); ?>

And you will then be able to see your PHP configuration here:

http://{YOURDOMAIN_COM}/{POSSIBLE_PATH}/phpinfo.php

Search for "mysqli" to confirm that this is the likely cause of the error.

SOLUTION

If 'mysqli' is missing from your PHP configuration and if your webhosting control panel allows you to select your PHP version then you can possibly fix this from there, otherwise you will need to contact your webhosting provider or server administrator to ask them to add it for you.

A 'mod_rewrite' problem is something that only your webhosting provider or server administrator can check and address.

A database query has failed -- OwnCloud

CAUSE

OwnCloud requires that PHP's 'intl.default_locale' setting has a default value. Not all webhosting services will include a default value in in their PHP configurations. This error will be shown at the (incompletely-installed) web page:

Setting locale to en_US.UTF-8/fr_FR.UTF-8/es_ES.UTF-8/de_DE.UTF-8/ru_RU.UTF-8/pt_BR.UTF-8/it_IT.UTF-8/ja_JP.UTF-8/zh_CN.UTF-8 failed
Please install one of these locales on your system and restart your webserver.

You can check this by creating a file named "phpinfo.php" in the directory where you are trying to install the app, and give it this content:

<? phpinfo(); ?>

And you will then be able to see your PHP configuration here:

http://{YOURDOMAIN_COM}/{POSSIBLE_PATH}/phpinfo.php

Search for "intl.default_locale" to confirm that this is the likely cause of the error.

OwnCloud requires that MySQL's binary logging is [i]disabled[/i] or [i]BINLOG_FORMAT = STATEMENT[/i]. This is much less likely to be the cause of an OwnCloud problem but needs to be considered if the above is correct.

SOLUTION

If your webhosting control panel allows you to customize your PHP configuration then you can possibly fix this from there by giving this setting a value of "en_US.UTF-8" (for example), otherwise you will need to contact your webhosting provider or server administrator to ask them to add the value for you.

OwnCloud's MySQL server configuration requirements are detailed here.

A database query has failed -- Oxwall

CAUSE

Oxwall requires that the PHP 'mbstring' extension is installed.

You can check this by creating a file named "phpinfo.php" in the directory where you are trying to install the app, and give it this content:

<? phpinfo(); ?>

And you will then be able to see your PHP configuration here:

http://{YOURDOMAIN_COM}/{POSSIBLE_PATH}/phpinfo.php

Search for "mbstring" to confirm that this is the likely cause of the error.

SOLUTION

If your webhosting control panel allows you to select your PHP version then you can possibly fix this from there, otherwise you will need to contact your webhosting provider or server administrator to ask them to add it for you.

A database query has failed -- PrestaShop

CAUSE

PrestaShop requires that either the PHP 'mysql' or 'mysqli' extension is installed. Or both, but not neither.

You can check this by creating a file named "phpinfo.php" in the directory where you are trying to install the app, and give it this content:

<? phpinfo(); ?>

And you will then be able to see your PHP configuration here:

http://{YOURDOMAIN_COM}/{POSSIBLE_PATH}/phpinfo.php

Search for "mysql" to confirm that this is the likely cause of the error.

SOLUTION

If your webhosting control panel allows you to select your PHP version then you can possibly fix this from there, otherwise you will need to contact your webhosting provider or server administrator to ask them to add them for you.

A database query has failed -- SilverStripe

CAUSE

There is a problem with SilverStripe's Italian translation that prevents it from being installed with that locale selected.

SilverStripe requires these PHP extensions and modules:

dom, gd, fileinfo, hash, iconv, [b]mbstring[/b], mysql or mysqli, session, simplexml, tokenizer, xml 
* some webhosting providers will not include this by default

You can check this by creating a file named "phpinfo.php" in the directory where you are trying to install the app, and give it this content:

<? phpinfo(); ?>

And you will then be able to see your PHP configuration here:

http://{YOURDOMAIN_COM}/{POSSIBLE_PATH}/phpinfo.php

Search for those extensions (especially "mbstring") to confirm that this is the likely cause of the error.

SOLUTION

If your webhosting control panel allows you to select your PHP version then you can possibly fix this from there, otherwise you will need to contact your webhosting provider or server administrator to ask them to add the missing extension for you.

A database query has failed -- WHMCS

CAUSE

The WHMCS administrator password must be at least 5 characters long.

WHMCS requires that the MySQL 'sql_mode' value is not set to strict. This can only be checked by your webhosting provider or server administrator.

Oxwall requires that the PHP 'ioncube' extension is installed.

You can check this by creating a file named "phpinfo.php" in the directory where you are trying to install the app, and give it this content:

<? phpinfo(); ?>

And you will then be able to see your PHP configuration here:

http://{YOURDOMAIN_COM}/{POSSIBLE_PATH}/phpinfo.php

Search for "ioncube" to confirm that this is the likely cause of the error.

SOLUTION

Make sure that the administrator password that you enter for the application is at least 5 characters long.

Ask your webhosting provider or server administrator to edit this file:

/etc/my.cnf

Find the sql_mode= line and change it to:

sql_mode=""

If your webhosting control panel allows you to select your PHP version then you can possibly fix missing extensions from there, otherwise you will need to contact your webhosting provider or server administrator to ask them to add the missing extension for you.

A database query has failed -- WordPress

CAUSE

WordPress requires that either the PHP 'mysql' or 'mysqli' extension is installed. Or both, but not neither.

You can check this by creating a file named "phpinfo.php" in the directory where you are trying to install the app, and give it this content:

<? phpinfo(); ?>

And you will then be able to see your PHP configuration here:

http://{YOURDOMAIN_COM}/{POSSIBLE_PATH}/phpinfo.php

Search for "mysql" to confirm that this is the likely cause of the error.

SOLUTION

If your webhosting control panel allows you to select your PHP version then you can possibly fix this from there, otherwise you will need to contact your webhosting provider or server administrator to ask them to add them for you.


An error has occurred while executing the application API -- Dada Mail

CAUSE

Dada Mail requires that the "Perl DBI" and "DBD-mysql" modules are enabled.

SOLUTION

Look for a way to enable these modules from your webhosting control panel. If you can't find them then ask your webhosting provider or server administrator to add them for you.

An error has occurred while executing the application API -- MODx

CAUSE

MODx requires that PHP's 'date.timezone' parameter has a value.

You can check this by creating a file named "phpinfo.php" in the directory where you are trying to install the app, and give it this content:

<? phpinfo(); ?>

And you will then be able to see your PHP configuration here:

http://{YOURDOMAIN_COM}/{POSSIBLE_PATH}/phpinfo.php

Search for "date.timezone" to confirm that this is the likely cause of the error.

SOLUTION

Look for a way to enable these modules from your webhosting control panel. If you can't find them then ask your webhosting provider or server administrator to add a value for you.

An error has occurred while executing the application API -- phpScheduleIt

CAUSE

phpScheduleIt requires that the PHP 'mysqli' extension is installed.

You can check this by creating a file named "phpinfo.php" in the directory where you are trying to install the app, and give it this content:

<? phpinfo(); ?>

And you will then be able to see your PHP configuration here:

http://{YOURDOMAIN_COM}/{POSSIBLE_PATH}/phpinfo.php

Search for "mysqli" to confirm that this is the likely cause of the error.

SOLUTION

If your webhosting control panel allows you to customize your PHP configuration then you can possibly fix this from there, otherwise you will need to ask your webhosting provider or server administrator to add it for you.

php-pdo-mysql-version-minimum v1 (detected: OFF)

CAUSE

A number of apps require the PDO MYSQL PHP extension, which is not standard on all hosting control panels.

SOLUTION

Add the PDO MYSQL extension to PHP, or disable affected apps within Installatron Admin » Application: Access Control.

Zurmo requires MySQL 'max_sp_recursion_depth' to be set at a value of '100' or higher

CAUSE

Zurmo requires that MySQL's 'max_sp_recursion_depth' parameter has a value of 100 or more.

SOLUTION

Ask your webhosting provider or server administrator to increase the value for you.

Why does Installatron connect to my domain with a URL like http://123.123.123.123/[b]apiwt.php?width=656[/b]?

This process updates the preview image for the application in the user's [i]My Applications[/i] tab, in Installatron.

© 2004 - 2016 Installatron LLC. All rights reserved.