He Dirk.
ucr search --brief apache2/ssl:
apache2/ssl/ca: <empty
apache2/ssl/certificate: <empty
apache2/ssl/certificatechain: <empty
apache2/ssl/ciphersuite: <empty
apache2/ssl/compression: <empty
apache2/ssl/honorcipherorder: <empty
apache2/ssl/key: <empty
apache2/ssl/tlsv11: <empty
apache2/ssl/tlsv12: <empty
saml/apache2/ssl/ca: <empty
saml/apache2/ssl/certificate: <empty
saml/apache2/ssl/certificatechain: <empty
saml/apache2/ssl/key: <empty
curl -v https://yourserver.yourcompany.com:
* Rebuilt URL to: https://........../
* Trying ..........
* TCP_NODELAY set
* connect to ..... port 443 failed: Verbinding is geweigerd
* Trying ...........
* TCP_NODELAY set
* Connected to ......... (............) port 443(#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
* CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: /etc/ssl/certs
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (OUT), TLS alert, Server hello (2):
* SSL certificate problem: self signed certificate
* Curl_http_done: called premature == 1
* stopped the pause stream!
* Closing connection 0
curl: (60) SSL certificate problem: self signed certificate
More details here: https://curl.haxx.se/docs/sslcerts.html
curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
bundle file isn't adequate, you can specify an alternate file
using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
the bundle, the certificate verification probably failed due to a
problem with the certificate (it might be expired, or the name might
not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
the -k (or --insecure) option.
