Problem
You see an error indicating that the license server is unreachable. In the Server Manager, the licenses may additionally show a grace period because the license check fails.
Note: This applies only to environments using the online license server. License files already issued are not affected. However, new offline licenses cannot be issued while the server is undergoing maintenance.
Cause
The license server (license.passwordsafe.de) undergoes periodic scheduled maintenance, during which it is temporarily unreachable. Connectivity issues can also be caused by a local problem:
- A firewall or proxy blocks outbound traffic to the license server.
- The certificate chain of the license server cannot be validated because the Amazon Root CA 1 certificate (or another CA certificate of the chain) is missing under Trusted Root Certification Authorities in the computer certificate store of the application server. This can happen, for example, if the automatic root certificate update is disabled by Group Policy. A page that loads without errors in the browser does not rule this out.
Resolution
-
Verify the network connection. Open PowerShell on the application server on which the Server Manager runs and run:
Test-NetConnection -ComputerName license.passwordsafe.de -Port 443If the test fails, make sure your internet connection is working and that your firewall or proxy allows outbound traffic to
license.passwordsafe.deon port 443. If the Server Manager uses a proxy, also check the system-wide proxy settings withnetsh winhttp show proxyand make sure the account under which the Server Manager runs is allowed to connect. - Open
https://license.passwordsafe.de/kisin Edge or Chrome on the application server. If the page does not load, the problem is in the network or caused by ongoing maintenance. If a certificate warning appears, note the exact error code (for exampleERR_CERT_AUTHORITY_INVALID) and continue with the next step. Firefox uses its own certificate store and is not suitable for this test. - Check the certification path: In the browser, click the padlock, open the certificate and switch to the Certification Path tab. The chain must lead up to Amazon Root CA 1 and be marked as trusted.
- Check the root certificate: Open
certlm.mscon the application server and check whether Amazon Root CA 1 exists under Trusted Root Certification Authorities → Certificates. If it is missing, import it, together with any missing intermediate CA certificate, into the computer certificate store. The certificates are available in the Amazon Trust Services Repository. If the Group Policy Automatic Root Certificates Update is disabled in your environment, distribute the root certificate manually. - Check the license server connection in the Server Manager again.
For current information about maintenance, see our Community Posts. If the problem persists after these checks, create a support ticket and include the result of the PowerShell test, the output of netsh winhttp show proxy, and a screenshot of the certification path.