How to continue installing Certbot

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):
Ubuntu 2204

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

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

I was installing Certbot and stopped at the moment of informing the webroot and would like to resume the installation. If you have any tips on what information I should enter when the webroot is requested, I would appreciate it.
That's it in principle. I want to resume the installation.

One option to consider is using Cloudflare's Origin CA Certificate. You get one from Cloudflare and you can set the expiration period for a long time.

You would not even have to bother installing Certbot and getting a Let's Encrypt cert. There are some limitations such as what ports are allowed but if you are just doing common things it might work very well you.



I don't know if I understood correctly. "common things". I actually want to create a portal for services and consultancy, where professionals can register and publish the services they offer or the consultancy they can provide. So I decided to create a VPS to test the idea, which is why I considered installing the certificate. Now if your suggestion works well. Why not give it a try?
Thanks for the tip.

Translated with DeepL Translate: The world's most accurate translator (free version)

1 Like

Oh, sorry. By "common things" I meant like a typical website, api, blog or similar that operates on HTTPS with port 443 or any other port supported by Cloudflare (link here)

Something uncommon are services that use non-standard ports like 8400 for HTTPS and similar apps.

Mail system ports are not supported by Cloudflare CDN so if you plan to run your own email service you need to adjust your strategy. And, a Let's Encrypt cert could help. But, that likely involves a different method than getting a cert for use in a website.


The webroot is the path served by your web server for that particular domain name.

Do you know your way around that web server?


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