Configuration issues
This topic has step by step solutions to common configuration issues.
Attempt to configure FLS by the following code leads to "JetBrains License Service is now running" and causes no change of configuration data.
./bin/license-server.sh configure \
--<property> <value>./bin/license-server.sh configure \
--<property> <value>.\bin\license-server.bat configure ^
--<property> <value>There are some configurations that require stopped FLS.
Change to the FLS installation directory using the command line.
Stop FLS using the following command:
./bin/license-server.sh stopTry to execute configuration command once again
Start FLS using the following command:
./bin/license-server.sh start
Change to the FLS installation directory using the command line.
Stop FLS using the following command:
./bin/license-server.sh stopTry to execute configuration command once again
Start FLS using the following command:
./bin/license-server.sh start
Stop FLS using the JetBrains License Service.
Services Microsoft Management Console (MMC) (Control Panel > Administrative Tools > Services > JetBrains License Service)
Try to execute configuration command once again
Start FLS using the JetBrains License Service.
[APP-WRAPPER] Failed to configure JetBrains License Service:
java.util.concurrent.ExecutionException:
com.jetbrains.bundle.exceptions.BadConfigurationException: The property <parameter> is unknown
and
could not be set by configure commandAttempt to configure FLS by
.\bin\license-server.bat configure ^
--<property> <value>for Windows leads to "The property <property> is unknown and could not be set by configure command" and causes no change of configuration data.
Stop FLS using the JetBrains License Service.
Services Microsoft Management Console (MMC) (Control Panel > Administrative Tools > Services > JetBrains License Service)
Change to the FLS installation directory using the command line.
Try to execute configuration command as follows:
.\apps\license-server\bin\license-server.bat configure ^ --<property> <value>Start FLS using the JetBrains License Service.
If this doesn't help try to upgrade to recent version of FLS available at the download page.
Connection fails despite proxy is configured for FLS connections.
FLS attempts to contact JetBrains via HTTPS (port 443) protocol directly without using system proxy. If usage of proxy is required for external connections in the environment where FLS is installed there is a need to explicitly configure proxy settings for FLS software as described in proxy configuration instruction.
Proxy configuration is available from build #8732. If the FLS is older, upgrade the installation to the latest build available on the Installation page.
If the version is correct, check if proxy is used by license server. To make it visit /check-connection (for more detailed information, see Connection). If there is no information about proxy, restart FLS by running following command from the installation directory:
./bin/license-server.sh restartAfter that try to visit /check-connection again to check if there is "Available proxies" information. If the proxy information is shown in "Available proxies" section but connection to JetBrains resources fails contact IT department of your organisation to make sure that the proxy is transparent and that it allows the server to reach JetBrains resources with all data passed as is including certificates provided by JetBrains resources. JetBrains resources which should be available for the server are www.jetbrains.com and account.jetbrains.com HTTPS (443 port).
If the version is correct, check if proxy is used by license server. To make it visit /check-connection (for more detailed information, see Connection). If there is no information about proxy, restart FLS by running following command from the installation directory:
./bin/license-server.sh restartAfter that try to visit /check-connection again to check if there is "Available proxies" information. If the proxy information is shown in "Available proxies" section but connection to JetBrains resources fails contact IT department of your organisation to make sure that the proxy is transparent and that it allows the server to reach JetBrains resources with all data passed as is including certificates provided by JetBrains resources. JetBrains resources which should be available for the server are www.jetbrains.com and account.jetbrains.com HTTPS (443 port).
If the version is correct, check if proxy is used by license server. To make it visit /check-connection (for more detailed information, see Connection). If there is no information about proxy, restart FLS using the JetBrains License Service.
After that try to visit /check-connection again to check if there is "Available proxies" information. If the proxy information is shown in "Available proxies" section but connection to JetBrains resources fails contact IT department of your organisation to make sure that the proxy is transparent and that it allows the server to reach JetBrains resources with all data passed as is including certificates provided by JetBrains resources. JetBrains resources which should be available for the server are www.jetbrains.com and account.jetbrains.com HTTPS (443 port).
FLS can't contact JetBrains because it doesn't follow redirects provided by proxy.
Due to security reason it is required for FLS to be able to specify connection point itself. If connection is made via proxy, proxy is required to be transparent and requires to allow the server to reach JetBrains resources with all data passed as is including certificates provided by JetBrains resources.
The following configuration might be considered as possible solution:
FLS software is installed on the computer with access to the Internet but without access to internal computers of your organisation.
Developers' machines can connect computer with license server but can't connect to the Internet.
Described configuration also known as DMZ (Demilitarized Zone) will work to let license server contact JetBrains and to keep developers' computers offline at the same time. If this configuration is not possible, you can use an offline activation code.