Page Comparison

There seem to be different solutions depending on the root cause and JVM involved - for example, this is a fairly simple solution, which seems to fix the problem for many users:

1. Restore JVM access to local certificate authority trust store on the host system

   • Ubuntu

     Shell script

     Code Block
     language bash
     sudo update-ca-certificates -f

   • Amazon Linux

     Shell script

     Code Block
     language bash
     sudo update-ca-trust check sudo update-ca-trust enable sudo update-ca-trust check

     Shell output

     Code Block
     language bash
     [ec2-user@ip-10-10-2-107 ~]$ sudo update-ca-trust check PEM/JAVA Status: DISABLED. (Legacy setup with static files.) PKCS#11 module Status, see symbolic links reported below: lrwxrwxrwx 1 root root 28 Feb 25 13:57 /etc/alternatives/libnssckbi.so.x86_64 -> /usr/lib64/nss/libnssckbi.so (link resolving to NSS: using legacy static list) (link resolving to p11-kit: using the new source configuration) [ec2-user@ip-10-10-2-107 ~]$ sudo update-ca-trust enable [ec2-user@ip-10-10-2-107 ~]$ sudo update-ca-trust check PEM/JAVA Status: ENABLED. (Legacy filenames are links to files produced by update-ca-trust.) PKCS#11 module Status, see symbolic links reported below: lrwxrwxrwx 1 root root 34 Mar 4 17:34 /etc/alternatives/libnssckbi.so.x86_64 -> /usr/lib64/pkcs11/p11-kit-trust.so (link resolving to NSS: using legacy static list) (link resolving to p11-kit: using the new source configuration)

2. Restart Bamboo