-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting
If error message 'Invalid license type (personal license can't use license code)' is displayed when issuing new license, it means personal and anonymous licenses are mixed together. In other words, if client's profile is selected from the list (personal license needs to be issued), license code should be empty because it's only used to verify anonymous licenses. Alternatively, if license code is entered (anonymous license needs to be issued), client's profile should not be selected.
If error message 'Invalid domain' is displayed when issuing new license, most likely licensed domain is entered wrong way. For example, it can't be IP-based (like http://1.1.1.1), include scheme (like http://www.clientdomain.com), or slash ( / ) symbol at the end (like http://clientdomain.com/path). In other words, it should be entered like clientdomain.com or clientdomain.com/path.
In order to prevent any possible piracy, installation domain is locked to person who installed protected script on specific domain first. For example, if client A deploys a script protected by Auto Faveo Licenser on domain.com, client B will see error message when trying to install his copy of script on the same domain (because it's natural that client B should never have access to client's A domain).
However, in some very rare circumstances, there might be a situation when client B needs to replace existing installation on client's A domain with his own script. In case that happens, simply delete old installation using the Licenses » View Licenses tab, so client B can deploy his copy of script on "locked" domain.
Once the maximum number of allowed installations for individual license is reached, new installations are blocked. If client needs to perform more more installations, the limit can be increased using the Licenses » View Licenses tab, or one of old installations should be deleted using the same tab. Deleting installation record in database is enough; even if user doesn't remove old files from his system, old installation will stop working within next automated license verification.
By default, Auto Faveo Licenser locks each installation to specific IP address used to perform installation. If IP address gets changed, license verification fails (so even if someone clones all the protected files and databases, this copy will not work). However, there might be a scenario when client's IP gets changed. In case that happens, update installation IP address using the Installations » View Installations tab, and this installation will continue working as usually.
If error message 'Invalid record details, duplicated data, or database error' is displayed when adding new or updating existing record, it means this record is already stored in database. For example, it may happen when adding a new product that uses the same SKU as another product, adding a new client with email address already used by another client, adding a new license of the same product to the same client again, and so on. In other words, this error prevents you from adding duplicated data to you database; therefore, double-check record details and fix them accordingly.
Since Auto Faveo Licenser allows issuing anonymous licenses, it's perfectly normal that no client's data is displayed for this type of licenses (because there isn't any). However, anonymous licenses always contain unique license code in client's field.
This only might happen when invalid product ID is hardcoded into script on user's machine, or script is trying to check a license which doesn't exist. In both cases, it's solely developer's mistake, which can be fixed by re-configuring script properly.
9 times out of 10, this error is caused by incorrect licensing engine configuration and/or parameters passed to licensing engine. For example, if script is being installed at https://www.clientdomain.com, but installation URL is entered as www.clientdomain.com (no URL scheme) or https://www.clientdomain/ (unnecessary / at the end), response verification will fail. This super-strict verification ensures that unauthorized installations are as difficult to perform as possible; therefore, any protected script should include additional check of data entered by user (such as installation URL) to ensure that each parameter fully meets requirements of each licensing function called (as per documentation).
Another common issue of invalid response is inaccurate time on your server (where Auto PHP Licenser is installed) and/or user's machine (where protected script is installed). It doesn't matter which timezone is used, but operating system time must always be accurate. For example, if actual time in your timezone is 2021-03-24 14:01, but computer has time set to 2021-03-24 15:01, license signature check might fail; therefore, make sure system time is accurate.
Here is the easiest way to find the cause this issue step-by-step:
-
Disable Banned Hosts in the Software
Settings»Security Settingstab. If that helps, it means host was blocked for some reason. You can find the reason of block and delete blocked host using theBanned Hosts»View Banned Hosts tab. If that doesn't help, continue to the second step, but leave Banned Hosts disabled during debugging. -
Run Demo Script (Full) bundled with Auto Faveo Licenser to install license on your machine. Do not modify any parameters, so demo script connects right to our demo server. If Demo Script (Full) (without any single modification) fails, it means there is a problem with your system. It might be an incorrect timezone, invalid network settings, etc., so check your system settings first. If Demo Script (Full) succeeds, proceed to the third step.
-
Run Demo Script (Full) again, but this time modify configuration file to use your licensing server and product. That is to say, only modify root URL of licensing server and product ID (if needed). Do not make any other single modification. If Demo Script (Full) fails, it means there might be a problem with your licensing server setup, so please contact us with login details of your licensing server, and we will check it for you. If Demo Script (Full) succeeds, proceed to the final step.
-
Check and fix your custom script (which you integrated licensing module into). All the previous tests indicate that your licensing server operates without any errors and system is properly configured. Hence, the only reason why license installation/verification fails in your custom script is incorrect setup of script itself. Since its developers responsibility to follow the documentation and ensure that any additional data (submitted by user and passed to licensing engine) strictly meets licensing engine requirements, developer needs to carefully debug his script in order to find and fix his own mistake at this point.
If error message %PRODUCT_TITLE% installation on domain %ROOT_URL% and/or IP address %IP_ADDRESS% not found is displayed during license verification, it means user's domain and/or IP address doesn't match domain and/or IP used to install protected script. This might happen if user copied protected script to another system (location) and/or his IP address was changed. It's an important security measurement to block unauthorized installations.
If user's IP address was changed, it can be updated using the Installations » View Installations tab. New user's IP will usually be displayed as failed report in the Reports » View License Reports tab. It's also possible for user to automatically update his licensed IP inside protected script (only if author enabled this functionality, which is available in licensing engine itself). Once IP address is updated, installation will start working immediately.
If no license verification callbacks from specific installation (license) are displayed in Reports tab, there might be a few different reasons. For example, it's possible user simply deleted script from his server. Another very common reason: script isn't used at the moment. Script performs initial verifications during installation and first use, but what happens later?
Let's say script is configured to perform license verification every 7 days, and gets installed on 2021-03-24. Naturally, another verification will be performed on 2021-03-31. However, if user doesn't launch script after 2021-03-30, no callback will be made. In other words, even if script is installed (bot not used) for months, no callbacks will be available to reduce application resources usage. However, license verification will be triggered the same second script gets used again (even if user does so years later).
In order to reduce resources usage on your server, automated license verification is performed every X days/weeks/months (as defined by you inside script configuration). For example, if script is configured to verify license every 7 days, last license verification was performed on 2021-03-23 and license was deactivated on 2021-03-24, script will stop working within next license check on 2021-03-30.
If Auto Faveo Licenser is configured to automatically delete all files and MySQL data when illegal license or possible cracking attempt is detected, but some files still remain, it means there's a problem with your files structure. According to documentation, directory /SCRIPT (can be renamed into anything you like) should always be placed in the root directory of your application. Put simply, if your application is installed at /your/application/here, Auto Faveo Licenser files should be located at /your/application/here/SCRIPT for auto-delete function to work properly.