a specifig domain is missing in this list. If I’m going to install it with “#certbot -d domain” the script says at the end, successfully installed, but if you call the https site - there comes a “Its not safe” browserwarning.
@bytecamp That command is for when certbot already has a certificate. @JustDoFitness is before that state in the process of getting a certificate issued: certbot doesn’t recognise all the hostnames which are specified in his Apache’s configuration.
@JustDoFitness How does the Apache configuration of the hostname you’re not seeing in certbot look like? Can you post it?
But he asks about how certbot generates the list presented with the apache or nginx plugin
So if you'd like to help the OP with something he didn't ask (which might actually be a good thing, I know), you might want to explain a little bit more instead of asking things of him/her he doesn't want to do, because he's "fixed" on another problem.
… and the “well-known” place in this specifig config is where exactly?
/etc/apache2/sites-available … and?
Update: I’ve deleted the old apache config file and created a new one (cp/paste from an existing working fqdn) and now it works 50%: it shows https with an “i” - that means: “… the connection is not completely secured”, therefore only “50%” (not 100% sure of the number, just targeted over the thumb (as we in germany say lol))