I get a blank page

📦 Install & Upgrade Help
1

I am trying to install SuiteCRM onto a Centos 6.2 system. I uploaded the unzipped files to a folder in the root of my system. When I go to 192.168.0.250/SuiteCRM I get the opening screen. I click on the next button and get a blank screen. Any ideas what is going on? I am using Chrome 30.0 and I have tried IE 11.

Thanks

2

check the permissions of your instance

3

I changed all the permissions to 755 recursive with the same results.

4

that still to closed, check the owner is correct, and try at least 775 on install, modeules, custom, themes, data, cache etc!

5

Owner is root and I changed the folders except for Cache I couldn’t find that one.

6

set the owner/ group as apache

7

After doing that I got further but didn’t get to create a new DB. I kept getting errors that said it couldn’t make the DB. I was installing this onto our phone server that is running Freepbx and this am I found out that I can no longer access the programming GUI. The connection to the DB is broken. The phone system is working, but I cannot make any changes to it. So until I get that under control I will be suspending the installation. I sell these systems and want to get your CRM installed on them and sell them as a turn key system for a SMB. Is that OK with you guys? Have you had others do the same thing?

Thanks

8

@Elentz

Just my personal uninformed opinion, but if you’re selling services based on SuiteCRM, I’d consider asking for donations from your customers. In other words, I’d let each customer know this software is open source software, and ask each of them if they can make a one time donation of $150 (or whatever) to the project, to support the project and it’s continued software development.

9

@rootlookup
Good point. I will push for that.

Thanks

10

@elentz: As a rule, a blank page usually means an unhandled exception. Could be permission related or otherwise. First step in debugging is to check the webserver log file. For Apache on Linux, this would usually be present in /var/log/apache2/error_log. If it’s not there, look for the ‘ErrorLog’ setting in your Apache config file, which should be in /etc/apache2/httpd.conf.

All the best!
AK