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.
It produced this output: They were all correct I noticed since I changed my dynamic IP to static after the whole process. My problem I am not able to validate TXT record. Therefore my site is not know. i check ssllabs and get this–>> see the pic.
After this then the one below comes up. Nothing about acme challenge so that my site will be found with the string that verifies it.
it doesn’t give me back the option except 1 keep existing certificate and 2 renew and replace certificate.
I have not idea how to fix this error…>>error:
httpd.bin: Syntax error on line 562 of /opt/bitnami/apache2/conf/httpd.conf:
Syntax error on line 72 of /opt/bitnami/apache2/conf/bitnami/bitnami.conf: Could
not open configuration file
/opt/bitnami/apache2/conf/bitnami/bitnami-apps-v:sse:ehosts.conf: No such file
or directory
I tracked and fixed everything but I am stuck on the last line. ehosts.conf does not exist.
Guys what should I do I tried using lego to manually get a CA all to no avail.
Could not obtain certificates:
error: one or more domains had a problem:
[each1teach1.us] [each1teach1.us] acme: error presenting token: could not start HTTPS server for challenge: listen tcp :443: bind: address already in use
[www.each1teach1.us] [www.each1teach1.us] acme: error presenting token: could not start HTTPS server for challenge: listen tcp :443: bind: address already in us
Does anyone know this or have anyone seen this before this error is my nemesis.
With this particular problem, I think you may have accidentally inserted some text in /opt/bitnami/apache2/conf/bitnami/bitnami.conf on line 72, while trying to quit vi.
That text which says:
bitnami-apps-v:sse:ehosts.conf
is meant to say:
bitnami-apps-vhosts.conf
If you fix that mistake, it should be back to normal.