I have deployed Moodle instance using the ARM template provided herein this post. The FQDN of my Moodle server is : “..cloudapps.azure.com”.
Issue:
After deployment, when this Moodle server is accessed with the above FQDN, there is a invalid certificate warning, and use has to opt to proceed inspite of system generated caution. (see picture attached)
Purchasing a SSL certificate and installing on NGINX does not seem feasible in this situation as the domain ownership proving methods include editing Azure.com DNS zone or receiving email at a azure.com email address, which is not permitted/accessible. The SSL certificate vendor permits editing website as a third way to prove ownership of the above domain, but as this Method also may not be doable as Moodle is a PHP application and the web service root directory does not permit installing any host static HTML files, that could be loaded with the verification code provided by the SSL certificate provider. The application dynamically generates the HTML that are served to the users accessing the application
Request/Ask:
If some of us have faced and resolved this issue, I would like to learn from them the ways of resolving this situation. The desired outcome is installing a Valid certificate for this service so the caution message does not come up.
SorraTheOrc
commented
2 years ago
I have deployed Moodle instance using the ARM template provided herein this post. The FQDN of my Moodle server is : “..cloudapps.azure.com”.
Issue: After deployment, when this Moodle server is accessed with the above FQDN, there is a invalid certificate warning, and use has to opt to proceed inspite of system generated caution. (see picture attached)
Purchasing a SSL certificate and installing on NGINX does not seem feasible in this situation as the domain ownership proving methods include editing Azure.com DNS zone or receiving email at a azure.com email address, which is not permitted/accessible. The SSL certificate vendor permits editing website as a third way to prove ownership of the above domain, but as this Method also may not be doable as Moodle is a PHP application and the web service root directory does not permit installing any host static HTML files, that could be loaded with the verification code provided by the SSL certificate provider. The application dynamically generates the HTML that are served to the users accessing the application
Request/Ask: If some of us have faced and resolved this issue, I would like to learn from them the ways of resolving this situation. The desired outcome is installing a Valid certificate for this service so the caution message does not come up.
Thanks in advance ... Regards