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. https://crt.sh/?q=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:
certbot certonly --manual --preferred-challenges=dns -d thanos.babblevoice.com -d sip:thanos.babblevoice.com -d sip:bling.babblevoice.com --duplicate
It produced this output:
Plugins selected: Authenticator manual, Installer None
Starting new HTTPS connection (1): acme-v02.api.letsencrypt.org
Obtaining a new certificate
An unexpected error occurred:
The server will not issue certificates for the identifier :: Error creating new order :: Cannot issue for “sip”: Domain name needs at least one dot
Please see the logfiles in /var/log/letsencrypt for more details.
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):
I am trying to configure FS for use with TLS but I am struggling. SSL/TLS I have a working knowledge - ut not in-depth. I have generated a cert which appears to work - browsers like A WebSocket server running with it.
RFC 5922 has the matching protocol for SIP clients to perform to verify any certificate presented. 7.1. Finding SIP Identities in a Certificate.
URI If the scheme of the URI is not “sip”, then the implementation MUST NOT accept the value as a SIP domain identity.
When I try to add sip: URI to the certbot command it returns that error.