Skip to main content

Unable to Reach the License Server

Every procedure checks your license with the license server before it does any work, and SLAM_register and SLAM_license_status check it too. When that check cannot reach the license server, the procedure stops and the Results pane says why, in a message that starts with:

Unable to reach the license server: ...

The message names the host Speediful tried (api.keygen.sh by default) and is followed by a line starting with Tip: that says what to do. SLAM_register, SLAM_license_status and every other procedure show the same message for the same cause.

Each cause has a different fix, usually made by a different team. Find the message below.

A proxy or firewall refused the connection​

Unable to reach the license server: a proxy or firewall refused the connection to api.keygen.sh (HTTP 403).

A proxy or firewall between the SQL Server machine and the license server blocked the request. This message also appears when the proxy answers with its own "access denied" page instead of passing the request on.

What to do: ask your network administrator to allow api.keygen.sh through the proxy for the SQL Server machine (outbound HTTPS, port 443).

The proxy could not connect to the license server​

Unable to reach the license server: the proxy server could not connect to api.keygen.sh (HTTP 502).

Speediful reached your proxy, but the proxy's own connection to the license server failed. The status can also be 503 or 504. This usually means a firewall stops the proxy itself from reaching the license server.

What to do: ask your network administrator to allow api.keygen.sh through the proxy.

The proxy requires authentication​

Unable to reach the license server: the proxy server requires authentication to connect to api.keygen.sh (HTTP 407).

The proxy accepts only authenticated requests.

What to do:

  • If no proxy username is set, set one with its password. From an elevated command prompt (right-click, Run as administrator), run:

    PS C:\Program Files\Speediful\SLAM> .\speediful_slam.exe configure_proxy
  • If a username is already set, the tip says the proxy rejected it. Run configure_proxy again with the correct username and password.

The proxy settings apply to the whole machine, including the procedures run by SQL Server. Speediful supports proxies that accept a username and password (Basic authentication). A proxy that accepts only Windows authentication (NTLM or Kerberos) needs an exception for api.keygen.sh instead.

Could not connect to the proxy server​

Unable to reach the license server: could not connect to the proxy server proxy.example.com:8080.

A proxy is set, but Speediful could not open a connection to it.

What to do: check that the proxy server name and port set with configure_proxy are correct and that the proxy is running. If your network no longer uses a proxy, remove the setting with speediful_slam.exe remove_proxy from an elevated command prompt.

The license server's certificate is not trusted​

Unable to reach the license server: the license server's certificate for api.keygen.sh is not trusted. This is usually caused by a proxy or firewall that inspects HTTPS traffic with its own certificate.

A proxy or firewall that inspects HTTPS traffic decrypts the connection and presents its own certificate in place of the license server's. Windows does not trust that certificate because the proxy's root CA certificate is not installed on the SQL Server machine.

What to do, either of:

  1. Install the proxy's root CA certificate in the Local Computer Trusted Root Certification Authorities store on the SQL Server machine. It must be the Local Computer store, not your own user's store: procedures run as the SQL Server service account, which does not see certificates installed for your user. Your network or PKI team can supply the certificate.
  2. Ask your network administrator to exclude api.keygen.sh from HTTPS inspection.

If you install the certificate and the error changes to "the license server's response could not be verified", the proxy is also changing the responses. See License server response could not be verified.

The connection timed out​

Unable to reach the license server: the connection to api.keygen.sh timed out.

Nothing answered. A firewall that silently drops traffic is the usual cause.

What to do: ask your network administrator to allow outbound HTTPS (port 443) from the SQL Server machine to api.keygen.sh. If your network requires all traffic to go through a proxy, set the proxy with speediful_slam.exe configure_proxy from an elevated command prompt.

The connection failed​

Unable to reach the license server: the connection to api.keygen.sh failed.

The connection was refused, or the SQL Server machine could not resolve the host name.

What to do: check that the SQL Server machine can resolve api.keygen.sh and reach it over HTTPS (port 443). If your network requires a proxy, set it with speediful_slam.exe configure_proxy from an elevated command prompt.

The license server returned an error​

The license server api.keygen.sh returned an error (HTTP 422): KEY_INVALID: must be a valid key

This is not a connection problem: the license server was reached and refused the request. The code and detail after the status come from the license server.

What to do: check the license key. If the status is 500 or above, the license server is temporarily unavailable; try again in a few minutes. If the error continues, contact Speediful support with the Support reference # from the output.

The procedure raises error 88300 (exit code 1). The message above appears in the Results pane.