- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
09-10-2018 04:43 AM
Conjur CLI doesn't interact to Conjur Master Appliance while performing basic installation in Docker Container. While running Conjur CLI to authenticate to Conjur master node; throws an SSL certificate (self-signed certificate) verification exception.
Any pointers to resolve this issue
10-19-2018 03:31 AM
Assuming you are using Conjur v5 EE, conjur CLI should work fine with self-signed cert. You can clear the CLI configuration by removing ~/.conjur , and try conjur init again & make sure to answer "yes" to trust the cert
ref: https://docs.conjur.org/Latest/en/Content/Tools/cli.html
11-30-2019 06:28 PM
@Quincy Cheng I am having same error. When I try to do conjur authn login , once I gave it my password it returns an error : error: SSL_connect returned=1 errno=0 state=error: certificate verify failed .
I typed yes to trust the cert , but still same error. The link you posted is unavailable. Any help would be much appreciated.
Thanks,
Nahom
01-09-2020 12:38 AM
Any info about this problem?
I have the same problem.
root@0adc9053fc56:/# conjur init --url https://192.168.53.11 --account admin
SHA1 Fingerprint=4A:45:1F:56:9D:8B:DF:A6:9C:B6:7D:45:63:4D:CB:20:FB:F0:4C:B4
Please verify this certificate on the appliance using command:
openssl x509 -fingerprint -noout -in ~conjur/etc/ssl/conjur.pem
Trust this certificate (yes/no): yes
Wrote certificate to /root/conjur-admin.pem
Wrote configuration to /root/.conjurrc
root@0adc9053fc56:/# conjur authn login admin
Please enter admin's password (it will not be echoed):
error: SSL_connect returned=1 errno=0 state=error: certificate verify failed
01-09-2020 12:45 AM
@Nahom Berhe
Ok, I have a solution to this.
Probably you are providing different URL than you have in certificate.
01-09-2020 08:12 AM
01-09-2020 12:16 PM
Hi @Marcin Dzieciol ,
So you gave it a different URL than the IP address specified above?
I have been at this for a while now. Can you please tell me which certificate are you talking about? Did you install certificates in your machines?
01-09-2020 12:18 PM
Hi @Ajay Pentela ,
How do you mean by execute outside the container? isnt the CLi installed in the container first and then you can execute it?
01-09-2020 03:14 PM
during the master configuration, you have to declare hostname that you'll use in communication with master.
docker exec <container-name> evoke configure master --accept-eula --hostname <host-name> --admin-password <password> <account-name>
--hostname
after executing this line, chef script will generate a certificate with a common name similar to hostname value. If you've declared FQDN (for example, cojnur.example.com) you have to use this FQDN in conjur-cli client. If you use ip address or something other, it won't work.
07-23-2020 07:25 PM
I am running into the same cert Issue, Was anyone able to resolve this issue ?
07-23-2020 11:47 PM
Did you read answers above ?
In the first half of this year I've installed few appliances and I didn't have any issues related with this post. I've answered to this topic above.
03-06-2022 07:00 PM
Thank you, just now going through Conjur Fundamentals Labs and this was an issue for me, but your answer helped point me in the right direction and I was able to get logged in. had to init with the actual name in the original cert that was created vs what was in the lab doc.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

