The apache plugin gets its hostnames, if none are manually chosen, from your Apache configuration, not from DNS. You can manually choose a hostname with the -d option. It doesn't necessary needs to be set in the Apache configuration, although we've seen on this Community that some Apache configurations aren't really compatible with the apache plugin, so YMMV.
Thanks. Played with certbot certonly --webroot -w /var/www/example -d www.example.com -d example.com -w /var/www/other -d other.example.net -d another.other.example.net https://certbot.eff.org/docs/using.html#webroot
and got:
- Congratulations! Your certificate and chain have been saved at:
/etc/letsencrypt/live/...
But thanks too
it seems I need to have a look in my Apache config... apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message VirtualHost configuration:...
Yes, Apache will try to run at all cost.
Which is not always a good thing.
It is best to always ensure the config it set correctly (even if apache runs, it may be faulty).
I'm wondering how it even works now, without multiple virtualhosts, if you're running at least two different sites, looking at the two different webroots. Are you using IP based virtualhosts in stead of name based?
@rg305 While I agree it's probably better to heed the Apache warning, it isn't mandatory as you could use IP based vhosts too. Would be even better, no SNI required for TLS for example.
My statement holds either way. I don't think he showed all of the output.
And I would agree that that part isn't too critical in the grand scheme of things.