Overview
Application Scenario
You may want to register multiple projects without exporting project information repeatedly or setting up a local authorization server.
FanRuan provides a public cloud authorization server. You can initiate authorization requests by filling in authentication information, and send the requests to the public cloud authorization server for unified authentication.
Function Description
The registration authenticated via the public cloud has the following features:
1. The registration is not subject to physical information changes.
2. The FineDataLink server must be able to connect to the authorization server via the public network, otherwise public cloud registration cannot be used.
The following external network addresses need to be accessible:
Domain | Port | Description |
---|---|---|
https://register.fanruan.com | 443 | Authorization server for public cloud authentication |
https://cloud.fanruan.com | 443 | Website management center |
3. Your registration is unlikely to fail because of the simple registration process.
4. You can use one authorized account credential you have applied for to register multiple projects. The price varies according to the maximum registration capacity. You can register any FineDataLink project.
Notes
FineDataLink projects send an authorization authentication request to the public cloud authentication server every 2 hours. If authentication fails 12 consecutive times, the project will be marked as Registration Failed, requiring re-registration.
Under System Management > Registration Management, the failure time and reason for each registration failure are displayed in a list, helping you troubleshoot problems, as shown in the following figure.

Registration Procedure
Obtaining the Authorization Document
Use the email address specified in the contract and send the registration information to FineDataLink business personnel (business@fanruan.com). The email format is shown as follows.
After verifying the received email, business personnel will create an account and send the account name and password to you via email.

Needed Information | Requirement | Note | |
---|---|---|---|
Priority contact | Contact FanRuan sales personnel in advance to confirm relevant matters and sign the contract. | / | |
Sender | Use the email address specified in the contract. | Otherwise, the registration will be rejected. | |
Recipient | business@fanruan.com | / | |
Title | Company Name Registration for FineDataLink Official Authorization Document | If you do not mark the company name in the email, the registration will be rejected. | |
Body | Basic Information | Company name: Company Name Project name: Project Name Contract signing date: YYYY/MM/DD | / |
Registration method | Public cloud authentication | / | |
Maximum registration capacity | Number of registrable projects | If this option is not provided, the number defaults to 1. | |
Account | Name of the public cloud account | If you need to specify a public cloud account, include the name in the email. (If the requested account name is already in use, it will not be available.) Otherwise, business personnel will randomly create an account for you. |
Registering the Project
Log in to FineDataLink as the admin, choose System Management > Registration Management, and click Register Now, as shown in the following figure.
Select Public Cloud as Authentication Method, enter the account and password in the email sent by business personnel, and click Submit, as shown in the following figure.
FineDataLink uses RSA by default to encrypt and store public cloud passwords. If you switch the encryption algorithm, passwords will be updated simultaneously.
Registration Failure Troubleshooting
In versions earlier than V4.0.28, the prompt window saying "Authentication failed. Perform authentication again." pops up if the registration fails.
In V4.0.28 and later versions, the prompt for registration failure has been optimized. If the registration fails, a prompt window pops up with the specific failure reason, helping you troubleshoot problems.
Standalone Project
If the registration fails, a prompt window pops up with the specific failure reason. You can click Details for troubleshooting, as shown in the following figure.
You can click Back to return to the Registration Management page. In the Registration Information area, information about the registration failure and the reasons is displayed. You can click View Error Details for troubleshooting, as shown in the following figure.
Cluster Project
If the registration fails, the reasons may vary across different nodes. A prompt window pops up with the specific failure reason for each node. You can click Details for troubleshooting, as shown in the following figure.
You can click Back to return to the Registration Management page. In the Registration Information area, failure reasons for all nodes are displayed in a list. You can click View Error Details for troubleshooting.
Failure Reason
The following table summarizes the reasons for registration failure. You can troubleshoot based on the specific reasons or the troubleshooting steps provided in the error details.

The error message of all other errors not mentioned in the following table is “Incorrect License Format”.
If the registration fails for multiple reasons, only the reason for the initial failure will be displayed.
Error Code | Error Name | Definition |
---|---|---|
10000 | JSON_PARSER_ERROR | The data format is incorrect. |
10001 | PARAM_INPUT_ERROR | The entered parameter is incorrect. |
20000 | DO_NOT_NEED_DEACTIVATE | This unauthorized machine does need to be unbound. (This prompt appears when you attempt to unbind an unauthorized machine.) |
20001 | MYSQL_UPDATE_ERROR | Errors occur during the MySQL database update. |
20002 | REDIS_UPDATE_ERROR | Errors occur during data insertion into the Redis database. |
30000 | LICENSE_EXPIRED | The license has expired. |
30001 | REPORT_VERSION_ERROR | The version is mismatched. |
30002 | ACCOUNT_STATUS_ERROR | The account status is abnormal. |
30003 | LICENSE_IP_ERROR | The IP address is not within the allowed range. |
30004 | LICENSE_DOMAIN_ERROR | The domain is not within the allowed range. |
30005 | LICENSE_APPNAME_ERROR | The app name is not within the allowed range. |
30006 | ACCOUNT_INPUT_ERROR | The account and the password are not authorized. |
30007 | REGISTER_OUT_OF_LIMIT | The maximum number of nodes for which licenses can be assigned has been reached. |
/ | The project server fails to connect to the cloud registration server. | / |
Registration Migration
The maximum registration capacity is specified in the email you received.
1. When the number of servers does not exceed the maximum registration capacity, you can use the original public cloud account to register the project on the new server.
2. If the maximum registration capacity is exceeded, you need to unbind the public cloud account from the original server before using the account to register the project on the new server.
Log in to FineDataLink as the admin, choose System Management > Registration Management > Version Information, click Re-register in Version Registration, and click Unbind to unbind the account from the old server, as shown in the following figure.

Start registration on a new server after the old server has been shut down for more than 24 hours. Otherwise, the old server still occupies a registration slot.
When you use the same public cloud account to register the project on a new server without unbinding it from the old server, the registration will fail with the prompt "The maximum number of nodes for which licenses can be assigned has been reached."