The following errors were reported by the server

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: www.bmteck.org

I ran this command:
sudo certbot certonly --standalone -d www.bmteck.org

It produced this output:
IMPORTANT NOTES:

My web server is (include version):
No webserver installed yet. I need to fix this issue before installing the webserver

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

My hosting provider, if applicable, is: Google

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):
YES

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

Hi @MarkYacoub

checking your domain - https://check-your-website.server-daten.de/?q=bmteck.org

Why do you want to create a Letsencrypt certificate if there is a new Google-certificate?

	CN=www.bmteck.org
	28.01.2020
	27.04.2020
expires in 88 days	www.bmteck.org - 1 entry

that is used?

Where do you run Certbot? On that 216.239.36.21 - ip?

Why answers the non-www, if you use standalone? And why is your Certbot so old?

1 Like

Hi Juergen

Thanks for your reply
I’m new to this , so please bare with me .
I’m installing an open source software , Oscar Mcmaster , that directed me with a link to certbolt to download that version.Where do I get the newest version ?

This software is being run on clients’ standalone servers not on google

I didn’t understand the very last question

Regards
Mark

Hi @MarkYacoub,

Let’s Encrypt certificates get installed on web servers. Normally Certbot (or another Let’s Encrypt client application) will need to be run directly on the individual web server where the certificate is going to be used.

@JuergenAuer is confused because your site has a valid certificate issued by Google’s certificate authority. In this case, you might not need a Let’s Encrypt certificate at all. If you have a valid certificate from someone else, that’s just as good as a Let’s Encrypt certificate—maybe better if you already have a working software solution to obtain and renew this certificate within your existing environment.

Is it clear to you whether or not you need a Let’s Encrypt certificate, and which server(s) your Let’s Encrypt certificate(s) would be used on?

To expand on these two questions:

certbot --standalone is generally meant for servers that don’t have an existing web server listening on port 80 at all. But it looks like your server does have one, so how did you decide to use --standalone?

Certbot 0.27.0 was released in September 2018, so it’s not a very current version. @JuergenAuer is wondering why you’re using such an old version. (But I think I know the answer to that: it’s probably the version provided by your Ubuntu 18.04 LTS operating system, which rarely updates old software packages unless it’s forced to. In any case, the older Certbot version is probably not very relevant to the specific error message that you get, or to the other questions about whether or why you need to use Certbot and/or Let’s Encrypt in this application.)

Yes … it’s clear now

Thanks a mil to all who helped me out

Hi Schoen

The idea is I am not installing this software on a web server .
I am installing it on a Ubuntu virtual machine that isn’t running any web servers yet.
According to the installation instructions , the web server should be installed after installing the certificate

OK, but right now Google gives a Google-generated 404 in response to HTTP requests to that domain. That in turn means that the domain is not yet pointed at the virtual machine you referred to. If it were, the request should just time out, not be handled by Google!

So before proceeding with your instructions, you need to figure out how to get Google to send incoming requests to your virtual machine instead of handling them with some kind of Google-maintained service.

Awesome … thanks
That helps a greeeeeeeeeeeat deal

Thanks again
Mark