Domain Registry Go to Subdomian setup of your domain name Subdomain Name Subdirectory / URL test.mydomain.com test.azurewebsites.net Go to DNS & Nameservers -> DNS Records Record Name Content CNAME test test.azurewebsites.net TXT test <azure id> Get <azure id> from within your Azure App Service properties. Azure App Service Go to Custom Domains in App Service... » read more
Error: The SMTP server requires a secure connection or the client was not authenticated. The server response was: 5.7.0 Must issue a STARTTLS command first. Fix: Step (1): smtp.EnableSsl = true; if not enough: Step (2): “Access for less secure apps” must be enabled for the Gmail account used by the NetworkCredential using google’s settings page:
From portal.azure.com … Go to “Networking” section of VM. Add Inbound port rule … Port: xxxxx Protocol: Any Note: There maybe firewall port that needs to be open as well. For this, go to “Windows Defender Firewall with Advanced Security” to add new inbound rule for port xxxxx.
From portal.azure.com … Go to “Networking” section of VM. Add Inbound port rule … Port: 1433 Protocol: Any Check List: SQL Server Properties -> Connections -> “Allow remote connections to this server” is checked SQL Server Network Configuration -> TCP/IP is enabled and set to port 1433 Windows Defender Firewall with Advanced Security -> Inbound... » read more
SQL Server Mail Account Setup Server name: smtp.gmail.com Port number: 587 This server requires a secure connection (SSL): Checked Basic Authentication: enter your username and password Google Email Make sure “Allow less secure apps” is set to ON Note: for Google Admin users go to Gmail -> Security -> Less Secure Apps Run the following... » read more
Error: Message The mail could not be sent to the recipients because of the mail server failure. (Sending Mail using Account 1 (2020-07-23T17:27:13). Exception Message: Cannot send mails to mail server. (Mailbox unavailable. The server response was: 5.7.1 Unable to relay). ) Fix: Make sure the SQL Server Mail Account and Profile are setup correctly.
Please be aware that depending on your DNS provider it can take up to 48 hours for the DNS entry changes to propagate. You can verify that the DNS propagation is working as expected by using http://digwebinterface.com/ http://digwebinterface.com