Hello , i'm encountering an issue while using the certbot , i'm trying to use it to automatically generate certificates for my python program (that uses sockets and therefore isn't a website) but the certbot requires a website
When you opened this thread in the Help section, you should have been provided with a questionnaire. Maybe you didn't get it somehow (which is weird), or you've decided to delete it. In any case, all the answers to this questionnaire are required:
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. crt.sh | example.com), 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):
3 Likes
hello , sorry , here's it completed:
My domain: None as explained
command i ran : certbot certonly --standalone
my webserver is : a windows machine but isn't a webserver , but rather a program using certificates and TLS to communicate with UDP and sockets
My hosting provider : myself
I can login to a root shell on my machine (yes or no, or I don't know): yes
I'm using a control panel to manage my site (no, or provide the name and version of the control panel): no
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): latest
The Let's Encrypt Certificate Authority only issues domain validated certificates. You cannot use Let's Encrypt certificates without a domain.
Certbot dropped Windows support last month. If you obtain a domain and still would like to use Let's Encrypt certificates, you will need to use an ACME client that supports Windows.
While not relevant in his case due to the previous disqualifications, it is important to always respond to version questions with a number, as latest is a constantly moving target which makes it too ambiguous to be useful.
3 Likes
LetsEncrypt only issues publicly trusted DomainValidation (DV) certificates. You will need a registered domain name to obtain a DV certificate.
There are currently three challenges that can be used to authorize a certificate:
- HTTP-01
- TLS-ALPN-01
- DNS-01
HTTP-01 and TLS-ALPN-01 require the server the domain points to respond to HTTP and TLS requests (respectively).
DNS-01 requires modification to the DNS records.
You will need to obtain, and renew, certificates using those methods. They can then be used by whatever programs or protocols you desire.
Alternatively, you can probably use self-signed certificates (without public trust) for your applications.
4 Likes
Not exactly:
Although some may find "website" and "domain" synonymous, they are not.
A website generally requires a domain [for ease of use].
A domain does not require a website [domains/FQDNs have many more uses].
Although the first two require "web" access to your server, you don't need a website, nor even any web server software installed. The ACME client itself can serve the required HTTP(S) responses.
The third ignores HTTP(S) altogether and focuses only on DNS [no website, no web service, no ACME client responding to web requests].
2 Likes
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.