The SSL connection could not be established

Question

I am using a third party library (Splunk c# SDK ) in my ASP.NET core application. I am trying to connect to my localhost Splunk service via this SDK, but I get an exception saying:

System.Net.Http.HttpRequestException: The SSL connection could not be established, see inner exception.

And The inner exception says:

The remote certificate is invalid according to the validation procedure.

This SDK uses HTTP client under the hood, but I don't have access to this object to configure HttpClientHandler.

All my search on google ends up using ServicePointManager to bypass the SSL validation, but this solution doesn't work in Asp.Net core.

ServicePointManager.ServerCertificateValidationCallback = delegate { return true; };

Is there any way to bypass this validation in asp.Net core?

Can't you register the certificate of the localhost service with your machine, so that it becomes valid? — ProgrammingLlama, Oct 23 '18 at 00:37
@John No it is not. The server is Splunk Enterprise, I just download and install it, it hosts the service on localhost:8089 — MVafa, Oct 23 '18 at 05:30
You'll need to find some way to export the SSL certificate it's using, or use your own self-signed certificate. Then you can add it to Windows through `certmgr.msc` — ProgrammingLlama, Oct 23 '18 at 05:53
For `HttpClient`from `Asp.Net Core`, you could try `ServerCertificateCustomValidationCallback `, refer [bypass invalid SSL certificate in .net core](https://stackoverflow.com/questions/38138952/bypass-invalid-ssl-certificate-in-net-core), but it seems you could not pass `HttpClientHandler`, you may check whether `Splunk c# SDK ` could exposes this. — Edward, Oct 24 '18 at 06:21

score 192 · Answer 1 · edited Jan 13 '22 at 17:20

192

Yes, you can Bypass the certificate using below code...

HttpClientHandler clientHandler = new HttpClientHandler();
clientHandler.ServerCertificateCustomValidationCallback = (sender, cert, chain, sslPolicyErrors) => { return true; };

// Pass the handler to httpclient(from you are calling api)
HttpClient client = new HttpClient(clientHandler);

edited Jan 13 '22 at 17:20

Daniel Williams

8,912
15
68
107

answered Jun 05 '19 at 11:58

Rohit Jangid

2,291
1
11
9

33

note that this solution just removes all certificate validation from your code and is thus a security issue! – Daniël Tulp Sep 03 '20 at 07:43
Where in an MVC project should this be placed? – Bbb Apr 11 '22 at 12:02
A less security breaching solution that works in our case : clientHandler.ServerCertificateCustomValidationCallback = (sender, cert, chain, sslPolicyErrors) => cert.Verify() – noontz Feb 01 '23 at 15:47

score 51 · Answer 2 · answered Aug 04 '21 at 12:23

51

As I worked with the identity server (.net core) and a web api (.net core) on my developer machine, I realized, that I need to trust the ssl certification of localhost. That command does the job for me:

dotnet dev-certs https --trust

answered Aug 04 '21 at 12:23

Daniel Michelfelder

528
4
5

2

wow more then 300 score with only one answer :O – Ravi Makwana Oct 13 '22 at 07:58

score 21 · Answer 3 · answered Sep 28 '21 at 18:05

21

If you are adding an IHttpClient and injecting through DI, u can add the configuration on the Startup.cs class.

public void ConfigureServices(IServiceCollection services)
        {
services.AddHttpClient("yourServerName").ConfigurePrimaryHttpMessageHandler(_ => new HttpClientHandler
            {
               ServerCertificateCustomValidationCallback = (sender, cert, chain, sslPolicyErrors) => { return true; }

            });
}

And then call it from your dependency injected class.

public class MyServiceClass 
    {
private readonly IHttpClientFactory _clientFactory;
public MyServiceClass (IConfiguration configuration, IHttpClientFactory clientFactory)
        {
            _clientFactory = clientFactory;
} 

 public async Task<int> DoSomething()
{
var url = "yoururl.com";
var client = _clientFactory.CreateClient("yourServerName");
var result = await client.GetAsync(url);
}

answered Sep 28 '21 at 18:05

Yamil Ortega

293
3
11

Your, code solved my problem, now its working perfectly in .Net 5 Worker. Thank you very much. – agileDev Feb 19 '22 at 13:41
Thank you. Your first piece of code solved the exact SSL issue in my case. Thank you. – suma Apr 26 '22 at 04:36
Thank you. it solved my problem in .Net core 6. I add that code in Program.cs file. – Mahdi Abyaznezhad Aug 13 '22 at 15:21
2

Of course this fixes it; it *disables SSL verification* – Zimano Jan 04 '23 at 14:48

score 9 · Answer 4 · answered Mar 24 '22 at 09:44

9

Installing the .NET Core SDK installs the ASP.NET Core HTTPS development certificate to the local user certificate store. The certificate has been installed, but it's not trusted. To trust the certificate, perform the one-time step to run the dotnet dev-certs tool:

dotnet dev-certs https --trust

for more information visit this link

answered Mar 24 '22 at 09:44

MertHaddad

447
1
7
15

How to remove the development cert once the SDK has been uninstalled? – Aamir Mar 28 '23 at 00:09
This answer solved my problem on the production server! Thanks :) – Iman Nemati Apr 13 '23 at 20:50

score 8 · Answer 5 · answered Jun 13 '19 at 16:19

8

ServicePointManager.ServerCertificateValidationCallback += (sender, certificate, chain, errors) =>
{
    // local dev, just approve all certs
    if (development) return true;
    return errors == SslPolicyErrors.None ;
};

This blog helped me

https://www.khalidabuhakmeh.com/validate-ssl-certificate-with-servicepointmanager

answered Jun 13 '19 at 16:19

Diego Mauricio Guerrero

141
2
4

1

ServicePointManager class is obselete now. https://learn.microsoft.com/en-us/dotnet/api/system.net.servicepointmanager?view=net-6.0 – N_E Sep 10 '22 at 02:54

score 8 · Answer 6 · answered Jun 14 '19 at 06:53

This worked for me,

Create a Splunk.Client.Context by providing custom HttpClientHandler, that will bypass SSL invalid cert errors.

HttpClientHandler handler = new HttpClientHandler();
handler.ServerCertificateCustomValidationCallback = (sender, cert, chain, sslPolicyErrors) => { return true; };

// Create Context 
Context context = new Context(Scheme.Https, "localhost", 8089, default(TimeSpan), handler);

// Create Service
service = new Service(context);

Saamer · Answer 7 · 2021-08-24T11:52:54.470

You get this error because your app isn't able to validate the certificate of the connection, and it's especially common to use this for the API that creates the session/login tokens. You can bypass it in a dangerous way as shown above, but obviously that's not a good solution unless you're just testing.

The best and easiest solution is to use the "modernhttpclient-updated" Nuget package, whose code is shared in this GitHub repo where there's also a lot of documentation.

As soon as you add the Nuget package, pass in a NativeMessageHandler into you HttpClient() as shown and build: var httpClient = new HttpClient(new NativeMessageHandler());

Now you will notice that you got rid of that error and will get a different error message like this Certificate pinning failure: chain error. ---> Javax.Net.Ssl.SSLPeerUnverifiedException: Hostname abcdef.ghij.kl.mn not verified: certificate: sha256/9+L...C4Dw=

To get rid of this new error message, you have to do add the hostname and certificate key from the error to a Pin and add that to the TLSConfig of your NativeMessageHandler as shown:

var pin = new Pin();
pin.Hostname = "abcdef.ghij.kl.mn";
pin.PublicKeys = new string[] { "sha256/9+L...C4Dw=" };
var config = new TLSConfig();
config.Pins = new List<Pin>();
config.Pins.Add(pin);
httpClient = new HttpClient(new NativeMessageHandler(true, config)

Keep in mind that your other (non token generating) API calls may not implement certificate pinning so they may not need this, and frequently they may use a different Hostname. In that case you will need to register them as pins too, or just use a different HttpClient for them!

I've been using HttpWebRequest for a while now on this server without an issue, and just starting to get the Remote Validation error, even though the app has no validation procedure, it's just a HttpWebRequest. Are you saying the library above gives more information than what HttpWebRequest provides? — Dan Chase, Oct 02 '21 at 18:33
Hey @DanChase did you update your backend or front end framework version? That’s probably the reason why you’re seeing it. Also it seems like you are using HTTPWebRequest instead of an HTTPclient. I don’t have experience with the former, and the question also uses an httpclient — Saamer, Oct 03 '21 at 22:41
turned out to be the expired Let's Encrypt Root Certificate that's in the news that caused it, had to remove from the machine. Would have never figured it out, I wish there was some diagnostic with it. I pulled the source on .net mono and looked at the validation, but it didn't really help because it looks like it's just walking up the chain. Removing the expired Root Cert was a hail Mary and it worked. I didn't even see that cert in the chain for the site's cert. Only messed up connecting to itself via FQDN/etc, not to yahoo or google, etc. Scary thing everyone is disabling validation now. — Dan Chase, Oct 05 '21 at 02:10

score 3 · Answer 8 · answered May 13 '22 at 14:58

3

I had to turn off my vpn to get rid off this error

answered May 13 '22 at 14:58

Muhammad Awais

1,608
1
21
21

MohdO · Answer 9 · 2023-05-12T21:41:51.293

This is most likely caused by having your proxy configured incorrectly.

Unfortunately some of the newer Windows workstations are coming with this setup wrong.

Check your system environment variables by running the following script in a Windows command prompt.

Ultimately if your proxy values are configured, but don't have any NO_PROXY settings you are going to encounter issues when trying to reach internal services.

Ultimately I recommend unsetting the HTTP_PROXY and HTTPS_PROXY variables unless you know what they do, and what you need them for.

Also important, check the value of no_proxy and compare it with your co worker to see if there is any differences, sometimes a dot "." can make a difference.

sobchak · Answer 10 · 2023-05-25T08:37:20.417

Windows 10 add Group Policy configuration for elliptical curves under Computer Configuration > Administrative Templates > Network > SSL Configuration Settings. The ECC Curve Order list specifies the order in which elliptical curves are preferred as well as enables supported curves which are not enabled.

Added support for the following elliptical curves:

 BrainpoolP256r1 (RFC 7027) in Windows 10, version 1507 and Windows Server 2016
    BrainpoolP384r1 (RFC 7027) in Windows 10, version 1507 and Windows Server 2016
    BrainpoolP512r1 (RFC 7027) in Windows 10, version 1507 and Windows Server 2016
    Curve25519 (RFC draft-ietf-tls-curve25519) in Windows 10, version 1607 and Windows Server 2016

reboot machine and success

issues

path

score -1 · Answer 11 · answered Jul 30 '23 at 22:33

-1

Kind of agreeing with @Muhammad Awais' answer...

If you're at your wits' end with this problem, I recommend rebooting your computer.

answered Jul 30 '23 at 22:33

Jim G.

15,141
22
103
166

The SSL connection could not be established

11 Answers11

Linked