You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The standard deployment creates a Azure MySql server with SSL off and a firewall rule of Allow 0.0.0.0
For the DB FW rule it might be a problem to provide the actual IPs of the WebApp at deployment time, but please use the setting "Allow all Azure services" instead of 0.0.0.0 - since this is much more restrictive, but will still allow access to the DB from the WebApp.
Regarding SSL - this seems to be a general Wordpress issue, there is no standard/parameter way of enabling SSL in the WP config to the DB? If it is possible, please make SSL default in this scenario and set the DB deployment parameter for SSL only. When hosting outside your private network, I think this is an important feature.
If for some obscure reason WP cannot support SSL to DB, then the deployement should use Azure spesific tools like delegation to a vnet to provide atleast a private network.
The text was updated successfully, but these errors were encountered:
The standard deployment creates a Azure MySql server with SSL off and a firewall rule of Allow 0.0.0.0
For the DB FW rule it might be a problem to provide the actual IPs of the WebApp at deployment time, but please use the setting "Allow all Azure services" instead of 0.0.0.0 - since this is much more restrictive, but will still allow access to the DB from the WebApp.
Regarding SSL - this seems to be a general Wordpress issue, there is no standard/parameter way of enabling SSL in the WP config to the DB? If it is possible, please make SSL default in this scenario and set the DB deployment parameter for SSL only. When hosting outside your private network, I think this is an important feature.
If for some obscure reason WP cannot support SSL to DB, then the deployement should use Azure spesific tools like delegation to a vnet to provide atleast a private network.
The text was updated successfully, but these errors were encountered: