WebSome interesting references about generating self-signed certificates can be found here, here, and here. Once the certificate is generated, you can start Orthanc using the … WebJun 22, 2024 · 2 Answers. Sorted by: 3. The problem was basically that I was using the .crt instead of the .pem when I generated the TLS secret. By changing the secret I got curl to detect it as a valid certificate. New command: kubectl create secret tls ingress-tls --key certificate.key --cert certificate.pem. Thanks to @Michael-sqlbot!
HTTPS encryption with Orthanc — Orthanc Book …
WebJun 21, 2024 · Curl probably relies on openssl to do the validations. The validations (may) include the proper flags for use (e.g. ssl server), CN name, date, chain validation, … WebJul 28, 2024 · : [Errno 14] curl#60 - "SSL certificate problem: unable to get local issuer certificate" Trying other mirror. It was impossible to connect to the CentOS servers. – harsha rachith csulb cybersecurity reddit
curl: (60) SSL certificate problem: when uploading behind proxy
WebFeb 26, 2024 · It displays the following error: curl: (60) SSL certificate problem: self signed certificate in certificate chain More details here: … WebMay 21, 2024 · 3 Importing ca-certificate chain (.crt) - RHEL7 Copy the cert to /etc/pki/ca-trust/source/ and run update-ca-trust extract If you had an existing PKI to deploy this with like Red Hat Certificate System, use that instead. Share Improve this answer Follow answered May 21, 2024 at 21:42 John Mahowald 31.1k 2 17 33 still the same issue : ( – … WebIf your cert specifies domain name (s), you must use that name or one of those names as the host part of your URL; if you don't have your DNS or hosts file set up to resolve that domain name correctly to the host address, you can use curl option --resolve (also on the man page) to override. Share Improve this answer Follow csulb cybersecurity program