DNS name does not have enough labels

[Tucho]

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: marslogic.xyz

I ran this command: sudo certbot certonly --csr request.csr --no-bootstrap

It produced this output: Starting new HTTPS connection (1): acme-v02.api.letsencrypt.org
An unexpected error occurred:
The request message was malformed :: Error creating new order :: DNS name does not have enough labels

My web server is (include version):

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

My hosting provider, if applicable, is: Digital Ocean

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

[jared.m]

My first question would be to see that CSR itself. My guess is that it’s malformed in some way. This error comes about if you do something like try to issue for examplecom instead of example.com. CSRs don’t have any sentitive information, it’s really just an unsigned copy of the public certificate.

My second question would be to ask if there’s a reason you’re using Certbot this way. CSR mode fills a really specific need that, if it doesn’t factor into your setup, usually causes more trouble than anything else.