Frontend Troubleshooting

If you are seeing a white page then you should make sure the templates_c folder is writable and check your Apache error logs, these are generally located in one of the following locations:

• /var/log/httpd/error_log
• /var/log/apache2/error_log

If there are no errors relating to GSP-Panel and you already went through the installer then you may need to enable Frontend Debugging

Common errors:

• Unable to navigate to anything that has a submenu
• When logging in you see an 'admin/index.php' displayed

This happens when your Apache configuration has an “Alias /javascript” line which redirects all javascript requests, this is commonly part of the 'javascript-common' package on Linux.

This can be fixed by doing one of the following:

1. Run 'a2disconf javascript-common' and 'service apache2 reload' as root on your webserver
2. Run 'cd /etc/apache2; grep -R Alias * | grep javascript' to determine what file holds the alias and then comment it out and reload apache2

This happens when MySQL strict mode is enabled, you will need this mode disabled to use GSP-Panel.

Certain system configurations have a problem with password encryption during the install process, the workaround is to set the encryption to plain text and manually set the password in the database. This should only be done on new installs that have this problem.

Login to the database via command line or a tool such as phpMyAdmin, navigate to the GSP-Panel database you created and run the following queries:

UPDATE settings SET value='plain' WHERE `name`='passencrypt';
UPDATE users SET password='yourpassword' WHERE uid=1;

After you login successfully go to the General Settings in GSP-Panel and select “Crypt” for “Password Encryption”, once that is done logout and log back in.

If you are experiencing a slow frontend/web interface make sure your MySQL settings are setup for an IP and not a hostname. You can review your MySQL settings in includes\mysql.conf.php

You may see the following error if your version of ionCube is outdated:

• gsp-panel.php cannot be decoded by this version of the ionCube Loader

If this is the case then you will need to update your ionCube loaders, you can do so by visiting http://www.ioncube.com/loaders.php

Common error messages:

• You do not have a license for [domain] at [directory]
• Invalid IP Address
• Domain Invalid
• Directory Invalid

If you are seeing any of the above error messages when logging into GSP-Panel then you may need to reissue your license. When a license is issued it is assigned the current IP, domain, and directory used to access it at that time, changing any of these will require you to reissue your license.

You can reissue your license by doing the following:

• Log into http://members.gsp-panel.com
• Navigate to “My Services”
• Click “Details” next to your license key that is receiving the error
• Scroll down and click “Reissue License”
• Log back into your panel and everything should be working again

There are several reasons you could be getting connection problems between the master and remote, below are some of the common reasons.

If the frontend displays “Unable to Connect” or a similar message, but you can connect with a game or FTP client, then your web server may be blocking outgoing traffic to the ports your servers run on.

If you are using shared hosting then you will need to contact your provider to open the required ports. Most shared hosting companies block outgoing traffic on unusual ports.

If you run your own web server then you will need to check to see if SELinux is enabled on your server(applies to Linux web servers only). You can check this by running the following command:

"cat /selinux/enforce"

If the response is “1” then you can do one of the following:

• disable SELinux by editing /etc/selinux/config and setting SELINUX to “disabled”
• Enable HTTP outgoing connections by running “setsebool -P httpd_can_network_connect=1”

If the response is “0” then SELinux is disabled, please open a support ticket for us to look into this further.

This indicates that there is a firewall on the remote server hosting the game server or that the server is not running properly.

There are three values stored in the settings table of the database named gameq_timeout, gameq_streamtimeout, and gameq_writewait. You may need to adjust these values depending on your environment, there is no “one size fits all”.

• gameq_timeout - Default: 10 (seconds). Amount of time a server has to respond to a query before assuming the server is offline.
• gameq_streamtimeout - Default: 300000 (microseconds). This setting affects how long the stream_select() waits to listen for response data before allowing the script to continue. Decreasing this value can speed up large lists but increases the amount of CPU usage the script uses.
• gameq_writewait - Default: 300 (microseconds). This setting affects how long the script will pause between writing packets to the server sockets. Lowering this value increases speed but also cpu usage. Setting this value very low (i.e. 0) can help with speeds of very large query lists.