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: drinkcana.com
It produced this output:
Error while running apache2ctl graceful.
httpd not running, trying to start
Action ‘graceful’ failed.
The Apache error log may have more information.
(98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
(98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
AH00015: Unable to open logs
My web server is (include version):
Apache 2.2.32 (Unix)
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:
Google Cloud Compute Engine
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):
The version of my client is (e.g. output of
certbot --version or
certbot-auto --version if you’re using Certbot): certbot 0.28.0
So I think I know a little of what’s happening. I’m using a Jetware installation which includes a second version of apache (http://jetware.io/appliances/jetware/lamp7-170503/profile )
Certbot is looking in the “standard” Apache folder for the running vhost, but it’s actually running in /jet/etc/apache
So when I shut down the “standard” apache, and restart with the Jetware Apache the Certificates don’t apply anymore.
Is there any way (and is it as simple as) pointing Certbot to look in the different apache directory to do it’s thing?
Or if I want to use certbot, would it be easier to just use the “standard” apache?
PS: I’m partially comfortable with Command line but would classify myself as a n00b because I’m primarily self taught.