So, TXT records is required only once to validate the domain by Let's Encrypt? And the SSL will also work after removing the txt records .
Yes, you can remove the TXT records.
They have served their purpose.
[If you renew the cert via DNS, you will have to create new TXT records in a few months from now]
As for the steps, we keep repeating ourselves.
You say, and show, all the steps that you have taken.
And I say that you must have missed one or it failed to do what you asked it to do.
I can't help you with those steps they no longer have anything to do with certbot nor obtaining a cert.
[that part is mostly complete - only part left is automating the renewals (which we can come back to after you take take of this bigger problem)]
What's the output of ls -l /opt/bitnami/apache2/conf/ ?
1 Like
This is giving followin output.
total 344
drwxrwxr-x 4 bitnami root 4096 Oct 4 09:15 bitnami
-rw-rw-r-- 1 bitnami root 263 Jun 24 12:44 deflate.conf
drwxrwxr-x 2 bitnami root 4096 Jun 3 17:24 extra
-rw-rw-r-- 1 bitnami root 19612 Jun 24 20:33 httpd.conf
-rw-rw-r-- 1 bitnami root 13064 Jun 1 21:42 magic
-rw-rw-r-- 1 bitnami root 60847 Jun 1 21:42 mime.types
-rw-rw-r-- 1 bitnami root 10210 Jun 1 21:45 modsecurity.conf
drwxrwxr-x 3 bitnami root 4096 Jun 3 17:24 original
-rw-rw-r-- 1 bitnami root 17333 Jun 1 21:45 pagespeed.conf
-rw-rw-r-- 1 bitnami root 141034 Jun 1 21:45 pagespeed_libraries.conf
lrwxrwxrwx 1 root root 50 Oct 8 06:24 server.crt -> /etc/letsencrypt/live/saraghsoft.com/fullchain.pem
lrwxrwxrwx 1 root root 61 Oct 4 17:24 server.crt.old -> /etc/letsencrypt/live/mmdev.lakshmilakshana.com/fullc
hain.pem
lrwxrwxrwx 1 root root 48 Oct 8 06:24 server.key -> /etc/letsencrypt/live/saraghsoft.com/privkey.pem
lrwxrwxrwx 1 root root 59 Oct 4 17:24 server.key.old -> /etc/letsencrypt/live/mmdev.lakshmilakshana.com/privk
ey.pem
-rw-rw-r-- 1 bitnami root 53146 Jun 1 21:45 unicode.mapping
drwxrwxr-x 3 bitnami root 4096 Oct 8 09:33 vhosts
I'm not that familiair with Bitnami, but isn't it strange there was a previous certificate for mmdev.lakshmilakshana.com for which you have renamed the symbolic link to .old (because you had to according to the manual..)?
By the way, did you run that command on your test server or your regular server? Because I thought we were talking about the new test server, right?
1 Like
Yeah! It's spelled Bitnami - LOL
[at least I know how to spell it - don't ask me anything more than that]
And I don't even know how to do that correctly! 
1 Like
Your knowledge of it is... a negative number! [you broke the meter] 
BITNAMI and TOMCAT
Two special breeds (in my book)
And totally proud of it! Not sure if I even want to be able to spell "Bitnami" correctly 
1 Like
This is not the cause since that certificate is deleted and once renamed to .old then that file didn't used by apache (in general)
Apparently test and mmdev resolve to the same IP.
From that I assume the spun up test to stage the change to mmdev (or others).
But neither is has worked 
Yes,
We are talking on test.saraghsoft.com We want to configure ssl certificate for that using Let's encrypt. The other domain is just pointed to this server for some other test purposes and it has no any effect or connection with test.saraghsoft.com
Note: test link created today for mentioning here and the all other certificates are deleted as of now, which also has the same issue.
But your previous directory listing said:
/etc/letsencrypt/live/saraghsoft.com/fullchain.pem
That's for the main domain? Or did you get a certificate for test.saraghsoft.com including the base domain?
That is mentioned here. Wildcard should resolve the subdomains.
Namaste!
The issue is now resolved using following method which directs with all neccesary steps.
Thank you!
2 Likes
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.