An Azure service that provides real-time messaging for web applications using WebSockets and the publish-subscribe pattern.
HI @Director
Thanks for reaching us regarding your issue from the deep investigation we found that The issue is due to an SSL certificate hostname mismatch. The root domain loads securely because it has a valid certificate bound, but the www hostname is not included in the certificate, which results in the ERR_CERT_COMMON_NAME_INVALID browser warning. DNS resolution is correct; the missing SSL binding for the www hostname is the cause.
To resolve this, add www.<domain> as a custom domain in Azure App Service and bind an SSL certificate (App Service Managed Certificate is recommended and free on Basic+ plans). Once the www hostname shows as secured, the warning will be resolved.
Quick steps:
- Azure portal > App Service > Custom domains > verify the www hostname is listed (add it using + Add custom domain if missing, using the existing CNAME).
- Next to the www hostname > Add binding > Source: App Service Managed Certificate > Validate (add the TXT record shown by Azure to DNS).
- Select Add >status changes to Secured after validation completes.
Reference :
https://learn.microsoft.com/en-us/azure/app-service/configure-ssl-bindings
https://learn.microsoft.com/en-us/azure/app-service/app-service-web-tutorial-custom-domain?tabs=root%2Cazurecli
If the answer is helpful, Please do click "Accept the answer” and Yes, this can be beneficial to other community members.
If you have any other questions, let me know in the "comments" and I would be happy to help you