OK, so it worked!
And thank you so much @jota for the help... the documentation certainly does not provide this level of help
For reference, the things to do to set up a wildcard SSL on the multisite domain name is to use the alternative method.
To then set up SSL for mapped domains:
1. Generate SSL using alternate method for the domain.
2. Note down the file paths where the generated certs are stored (/etc/letsencrypt/live/$DOMAIN/). Two files will be made, both with *.pem filetypes. One will be fullchain and one will be the key.
3. Make a link for both files generated in Step 2 in the folder /opt/bitnami/apps/wordpress/conf/certs/ ... To note is that while making these links, I used the custom names for the domain name to distinguish these files from any further cert files for other domains. The command I ran was:
sudo ln -s /etc/letsencrypt/live/$DOMAIN/privkey.pem /opt/bitnami/apache2/conf/MappedDomainName.key
sudo ln -s /etc/letsencrypt/live/$DOMAIN/fullchain.pem /opt/bitnami/apache2/conf/MappedDomainName.crt
Note that both filenames are changed to *.key and to *.crt filenames, why this is so I am not exactly sure.
These two files were confirmed to now exist in the apache2/conf folder with the
sudo ls /opt/bitnami/apache2/conf/
- Virtual hosts were then changed as per the tutorial here
Ensure that the file names for the new MappedDomain are reflective of the different location of the certs that were made in Step 3.
was added to " /opt/bitnami/apache2/conf/bitnami/bitnami-apps-vhosts.conf"
- Apache restarted.
Both domains, the main domain for the multisite, and the mapped domain, are working with SSL right now, by God's Grace!
Thank you for the help again, and hope this breakdown of steps helps other noobs like me to get going with installing SSLs for mapped domain on their Bitnami WordPress Multisite installs.
All the best