31
Kloxo-MR Tips and Tricks / Re: Alternative to Kloxo-MR
« on: 2017-12-18, 08:55:20 »hm.. VestaCP e.g.
It also has an open source code
How is it compare to Kloxo-MR? You're currently using it?
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
hm.. VestaCP e.g.
It also has an open source code
Go to https://curl.haxx.se/docs/caextract.html and download cacert.pem
rename it to ca-bundle.crt
replace /etc/pki/tls/certs/ca-bundle.crt
7] Please refer to https://curl.haxx.se/libcurl/c/libcurl-errors.html for error code: 77
[Sun Dec 17 04:12:21 PST 2017] Can not connect to https://acme-v01.api.letsencrypt.org/directory to get nonce.
[Sun Dec 17 04:12:21 PST 2017] Can not get domain new authz.
[Sun Dec 17 04:12:21 PST 2017] Please add '--debug' or '--log' to check more details.
[Sun Dec 17 04:12:21 PST 2017] See: https://github.com/Neilpang/acme.sh/wiki/How-to-debug-acme.sh
Should I downgrade it and if so, how do I downgrade?
sh /script/fixssl; sh /script/fixweb; sh /script/restart-web -y
sh /script/fixdns;sh /script/restart-all;
sh /script/fixdnsaddstatsrecord
curl -v https://mydomain.com
* About to connect() to mydomain.com port 443 (#0)
* Trying 133.244.221.21... connected
* Connected to mydomin.com (133.244.221.21) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* NSS error -8018
* Closing connection #0
* Problem with the SSL CA cert (path? access rights?)
curl: (77) Problem with the SSL CA cert (path? access rights?)
curl -v https://example.com
* About to connect() to example.com port 443 (#0)
* Trying 133.244.221.21... connected
* Connected to example.com (133.244.221.21) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* NSS error -8018
* Closing connection #0
* Problem with the SSL CA cert (path? access rights?)
curl: (77) Problem with the SSL CA cert (path? access rights?)
listen 443 ssl http2;
listen [::]:433 ssl http2;
listen 8433;
listen [::]:8433;
listen 8443;
listen [::]:8443;
orlisten 8443 ssl http2;
listen [::]:8443 ssl http2;
listen 443 ssl http2;
listen [::]:433 ssl http2;
listen 8433;
listen [::]:8433;
listen 8443 ssl http2;
pretty sure that error whould be a problem with your SSL Certificate itself. So would need to have your we host check your SSL Certification.
Pretty sure this an issue that only your web host can take core of for you. ie SSL Cert is not setup correctly, cURL/OpenSSL issue, etc.