Table of Contents | ||||||
---|---|---|---|---|---|---|
|
Problem - Getting display but with no wording/text in the Client front end
Solution
If you are not using the default English language. Make sure you had make a copy of the lang/english.php to the language you are using. For example, if you are using Chinese then copy lang/english.php → lang/chinese.php
Problem - Getting An error occurred while trying to connect to the hosting server. Please contact support. message on Client Area
Solution
This error occurs when there is no matching server in Module's Admin interface server listing (Figure 1) to the server that the hosting package it is using (WHMCS → Setup → Products/Services → Servers) Figure 1
...
Problem - Remote server with system(), fileperms(), posix_getpwuid(), fileowner(), filegroup() disabled in PHP
Solution
These functions are only needed for the cronjob and with One Step Installer. If you had used the one step installer, then it should have copied your /usr/local/lib/php.ini into /var/www/
...
Problem - Remote server passes the connection test but blank rules
Solution
If the remote server's Web Address is set to use https, try set it back to http.
Problem - Module stopped connecting to remote server
Solution
There are numerous factors on why the connection stop working. Here are a few things to check.
...
Problem - Remote server passes the connection test but blank rules
Solution
If the remote server's Web Address is set to use https, try set it back to http.
Problem - Cronjob not running properly on the remote server
Solution
If the cronjob is running properly, the ownership for CSFUnblockRemote.php and CSFSettings.php in /var/www/html/ should be set to the $fileOwner and $fileGroup in CSFSettings.php.
...
Problem - Dealing with Multiple PHP server environments
Solution
The module auto installer will install the cronjob using the native PHP (/usr/bin/php). There are few things you need to watch out for when you have multiple PHP installed on a system
...
Problem - IP isn't being removed from IPtables even though the IP removal was success via module
Solution
Try running the following command on the remote server's shell
...