welcome to Chilly Orange Support
Author: Matt / Created: March 28, 2014 / in Databased – Database Application Platform
In this article we’ll go over some of the more common issues people seem to have with setting up Databased on their server.
Please note that this article assumes you’re running an Linux/Apache server. If you’re running a Windows server, we’d suggest using the search function to find some past tickets relating to getting the software to run in a Windows environment.
Before looking at some common issues, please walk through the following steps and make sure everything is setup properly.
Step 1: make sure you’re using an Linux/Apache server.
The easiest way to do this, is simply contacting your hosting provider and ask them what software your server is using. Another way is by creating a PHP file (save as .php) on your server and insert the following code: <?php phpinfo();?>. Next, navigate your browser to this file and have a look at the information appearing on your screen. This will give you a detailed overview of the software your server is running.
Step 2: make sure you have ROOT access to your MySQL server
Again, the easiest would be to simply contact your hosting provider and ask them. If you are using a shared hosting environment, usually you won’t be able to access your MySQL server as ROOT and Databased can not be used.
Step 3: make sure you have uploaded all the files
If you’re using an FTP tool to upload all the files, double check all files have been uploaded. In particular, make sure the file “.htaccess” is present in the root folder of your application. Since this file is a hidden file, sometimes FTP tools won’t see the file and therefor won’t upload it.
Step 4: make sure your application is configured properly
Please follow the instructions in the documentation regarding the configuration of your software. An online version of the documentation can be found here. Please pay special attention to:
Make sure the base_url variable is set correctly, including a trailing “/” and the end
Make sure the variable “index_page” is set to an empty string “”
Make sure the variable “encryption_key” is set (this can be set any string, but it should not be empty)
Make sure you provide the root username and corresponding root password! If you’re not sure about these details, please contact your hosting provider.
ISSUE: 404 error when loading the login page
If you’re receiving a 404 error when trying to bring up the login page, this is usually caused by:
- a missing “.htaccess” file in the root folder of your application,
- mod_rewrite not being enabled on Apache
- using a Windows server rather then Linux/Apache
Please start by double checking that the “.htaccess” file is located in the root folder of your application and make sure the contents of this file match the contents of the “.htaccess” file provided with the software.
To check if mod_rewite is enabled, create a PHP file (save as .php) on your server and enter the following contents into the file: <?php phpinfo();?>. After saving the file, navigate your browser to this file (open up http://yourdomain.com/myphpfile.php) and have a look at the information on your screen. Perform a quick page search for “mod_rewrite”, if this search does not provide any results, this would indicate mod_rewrite is not enabled. To fix this, please contact your server administrator and ask him to enabled mod_rewrite. If you have access to WHM and have EasyApache installed, mod_rewite will automatically be installed when compiling Apache using EasyApache.
If you’re comfortable with the command line on your Linux server, you can enable mod_rewrite through the command line as well. Simlpy enter the command “a2enmod rewrite” and hit enter. Next, restart the Apache server by entering “service apache2 restart“. After this, you can reload the PHP file you’ve created before and check to make sure mod_rewrite is now enabled.
ISSUE: Internal server error
If you are seeing an Internal server error when trying to load the login page, this likely to be caused by:
- a faulty or corrupt “.htaccess” file in your application root folder
- using Windows/IIS rather then Linux/Apache
To solve this issue, please have a look at the contents of your “.htaccess” file and make the contents are identical to the contents of the “.htaccess” file provided with the software.
If you’re using Windows/IIS, you can delete the “.htaccess” file and use the provided “web.config” file instead. Please note that Databases does not officially support Windows/IIS and we can’t guarantee it will work flawlessly . That said, it appears the provided “web.config” file often works ok.
ISSUE: No input file specified when loading the login page
In some situations, users report a “No input file specified” error when trying to load the application. This is somehow related to the server configuration, and usually can easily be solved by following the instructions below.
If you’re experience this error when trying to load the login page, please edit your “.htaccess” file and replace it’s contents with the content below:
RewriteCond $1 !^(index\.php|swf|assets|custom|less|images|css|js|bootstrap|fonts|robots\.txt)
RewriteRule ^(.*)$ index.php?/$1 [L]
ISSUE: Database error when trying to load the login page
To fix this, please double check that your username (in most cases this should be root!!) and password are correct. If you have WHM access to your server, you can easily reset your root password. Log into WHM and use the search bar in the top left corner to search for “MySQL”, this should show you one or more items, one of which should read something like “reset MySQL root password”. You can use this function to reset the root password. Once reset, enter the password into the database.php configuration file and try reloading the login page.
ISSUE: No databases are showing up in Databased
When installing Databased on your server, the application won’t actually create any databases for you to work with (it will only create the application database which will always remain hidden). After setting up the software, you can either create new databases from scratch to work with, or you can enable existing databases allowing you to manage these databases through the application.
If you are not able to see any databases inside the application, this could mean one of two things:
- There are no existing databases on your server, or
- You have entered a non-root user in “/application/config/database.php” and you don’t have sufficient permissions with this user to access all databases on this server
Start off by checking whether or not there are existing databases located on your server. You can do this by using phpMyAdmin (or any other SQL tool allowing you to manage your MySQL server) to check if there are in fact no existing databases on your server. You can also use server admin panels like WHM/cPanel or Plesk to access your server and check if there are any existing databases. If you can confirm there are indeed no existing databases, everything is as it should be and you can simply proceed by creating a new database from scratch inside Databased.
If it turns out there are one or more databases located on your server, this is a strong indication that that MySQL user you have entered into “/application/config/database.php” is not the root user. If the username is anything other then “root“, this is likely your problem and you’ll need to enter the correct root user and corresponding password.