Keywords: General - Google Cloud Platform - Technical issue - Other
I have a Bitnami GCE VM that I had successfully setup to have "vhost" (subdomains) using the steps outlined here: https://docs.bitnami.com/virtual-machine/infrastructure/lamp/configuration/configure-custom-application/
For each vhost, I successfully setup custom applications, as outlined here: https://docs.bitnami.com/aws/infrastructure/lamp/administration/create-custom-application-php/
Everything was working well.
I then setup a Let's Encrypt SSL certificate on the same GCE VM by running "generate-certificate.sh" as instructed here: https://docs.bitnami.com/aws/how-to/generate-install-lets-encrypt-ssl/
The Let's Encrypt SSL certificate successfully installed on all the domains, but running "generate-certificate.sh" had an unexpected side-effect that it re-configured my vhost and Document root to point to "/opt/bitnami/apache2/htdocs" for all domains.
My custom apps remain unchanged, but I did notice that "/opt/bitnami/apache2/conf/bitnami/bitnami.conf" has vhost and Directory entries that point to the default "/opt/bitnami/apache2/htdocs" document root.
What I do not know is:
Did these entries already exist and were they being overridden by my custom config?
Did were these entries inserted by running "generate-certificate.sh"?
If "generate-certificate.sh" created those entries, what do I do to fix the situation?
If the entries are default and "generate-certificate.sh" made changes elsewhere, where did it make those changes? How do I fix it?
If there is a certain way to add Let's Encrypt certificates to vhosts, how do I do it?
Thanks in advance, for your help!