I develop application in XCode which use MailCore 2 library.
Application works, everything is fine
But yesterday in my country github was blocked.
So, I can't build my application.
Logs:
fatal: unable to access 'https://github.com/dinhviethoa/tidy-html5.git/': SSL certificate problem: Invalid certificate chain
fatal: unable to access 'https://github.com/dinhviethoa/libetpan.git/': SSL certificate problem: Invalid certificate chain
fatal: unable to access 'https://github.com/dinhviethoa/ctemplate/': SSL certificate problem: Invalid certificate chain
Why MailCore need github and what to do in this situation?
Related
I'm trying to connect to the PayPal REST API. This is a Nim program that uses httpclient, but there's nothing specific to Nim since this is just a REST API.
The error I get is:
Error: unhandled exception: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed [SslError]
I'm using OpenSSL 1.1.1m on Windows 10.
certificate verify failed
Your environment is not able to verify the SSL/TLS certificate currently used by paypal.com servers.
Update your root certificate authority bundle that's used to trust the signers of TLS certificates; you can download a current one here.
If you don't know where to put it, try openssl version -d
Well, I'm working with Openwisp and when I tried to register a device (router), I got this error.
Error
This is the configuration on the router
Config
Any idea what I might be doing wrong?
CURLE_PEER_FAILED_VERIFICATION (60)
The remote server's SSL certificate or SSH md5 fingerprint was deemed
not OK. This error code has been unified with CURLE_SSL_CACERT since
7.62.0. Its previous value was 51.
If you're in development/testing mode, you can disable SSL verification in openwisp-config by modifying /etc/config/openwisp and setting verify_ssl to 0.
In production you will have to make sure the SSL certificate of the server is valid.
Is there a reason why Facebook doesn't allow LetsEncrypt signed certificates in their "app development" section?
I keep getting this error:
(For the untrained eye, this is me trying to setup a webhook for new messages notifications)
Blurred out the host, but it's a valid host and using chrome or firefox on Linux and Windows doesn't give any errors.
SSLLabs also says the site is perfectly valid.
Running curl https://... on my own host, sure enough I get the same error,
curl: (60) SSL certificate problem: unable to get local issuer 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.
So my question is, why have Facebook (that openly supports LetsEncrypt) decided to use default curl CA bundle to verify the callback-url of an app? If that doesn't allow LetsEncrypt?
It appears to be counterproductive to me.
Is there a way around this?
SSLLabs also says the site is perfectly valid.
It shows a warning in orange, that the certificate chain is incomplete.
Your server should present all necessary intermediate certificates as well, in addition to the certificate issued for your domain. (Which was simply forgotten here by mistake.)
I am currently trying to set up Real-Time Updates to my site through the facebook app interface. When I attempt to test the callback to the callback url of https://messageall.com/facebook/callback/ I am getting an error message of:
Callback verification failed:
SSL certificate problem, verify that the CA cert is OK.
Details:
error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
However from what I can tell the certificate key chain is working fine and verifies when I test via http://www.digicert.com/help/
What could the facebook servers think is wrong with my CA?
Just got my Lync server deployed on Windows Server 2008 R2 and am trying to connect via Lync client on a different machine. When attempting to sign in, the client throws an error saying "Cannot sign in to Lync: There was a problem verifying the certificate from the server.".
Looking deeper, into the client box's event viewer, I see the following error "The certificate received from the remote serer was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The SSL connection request has failed. The attached data contains the server certificate. ....
My organization has an internal CA, which is in charge of issuing all required certificates to the Lync server. My client box has installed the internal CA (root) as a trusted CA provider. To me, this should cause any certificates that issues, including the Lync certificates, to be trusted.
I installed Lync client on the same box that Lync server is hoted, and am able to log in fine. My error only occurs when connecting from a different box.
Can anyone shed some light? Thanks!
I had same issue. To resolve: from client, hit url of CA Authority, some thing like http://CAservername/certsrv this provided option to download a CA Certificate Chain.
Put this into local computer trusted root certs and I was good to go.
As mentioned in the error message ("Cannot sign in to Lync: There was a problem verifying the certificate from the server"), this is clearly a certification error. If you work in a big company (where they have they own internal CA - (Certification Authority)) in most cases they would have used their internal certificate to establish trust relationship. If you just install/export the Root certificate of the CA under "Trusted Root Certificate Authorities” of “Local Computer” account, this error should be resolved.
If your company doesn't have own CA, then find our who issued the certificate for Lynch and install/export the root certificate of that CA to the same location as above, this issue should be resolved.