How to get certificate and private key for desktop application using TLS protocol for secure communication

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. |, so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:

I ran this command:

It produced this output:

My web server is (include version):

The operating system my web server runs on is (include version):

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don't know):

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):

1 Like

Welcome to the Let's Encrypt Community, Amruta :slightly_smiling_face:

I'm not exactly sure what you're trying to do here. Is this application supposed to be peer-to-peer?

1 Like

Let's Encrypt provides globally signed DV certs.
Which can be used by all types of systems/applications and are trusted worldwide.

But it seems that what you need is a locally trusted CA cert for a test/lab environment.
If so, you should start by seeking out a public CA system that best fits your needs/environment.

1 Like

I seem to be sharing this link a lot lately:


yes its peer-to-peer communication on windows.
Is it not the platform which provides TLS trusted certificates for peer-to-peer communication?

1 Like

In order to use Let's Encrypt certificates in this scenario, each client would need to be reachable as a unique (sub)domain with public DNS records since Let's Encrypt certificates are domain-validated (DV) certificates.

1 Like

OR perhaps one wildcard cert for all to share!

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.