Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installing Valid Certificate for an OSS application/web service running on Azure VMSS #266

Open
lalitm14 opened this issue May 4, 2022 · 1 comment

Comments

@lalitm14
Copy link

lalitm14 commented May 4, 2022

I have deployed Moodle instance using the ARM template provided herein this post. The FQDN of my Moodle server is : “<Azure_load-balancer_label>.<Azure_Region_name>.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
not secure warning

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

@SorraTheOrc
Copy link
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants