- 0 minutes to read

FAQ - Troubleshooting Alarm Plugins

Quickly resolve common Alarm Plugin issues in Nodinite with this FAQ and troubleshooting guide. Learn how to fix Office365 and SendGrid email problems, configure your environment, and customize alert properties for seamless monitoring and notifications.

✅ Step-by-step solutions for common Alarm Plugin issues
✅ Office365 and SendGrid email troubleshooting and configuration tips
✅ SSL/TLS certificate validation and firewall configuration guidance
✅ Guidance on customizing alert properties with macros
✅ Direct support contact for unresolved problems

If you have any issues that you cannot solve, contact our Support or send us an email at support@nodinite.com

Common Email Alarm Plugin Problems

DNS Resolution Errors

Problem: Test Alarm fails with "The requested name is valid, but no data of the requested type was found" (WSANO_DATA error) when attempting to send emails.

Root Cause: SMTP hostname cannot be resolved due to DNS configuration issues, missing DNS records (A/AAAA records), firewall blocking DNS port 53, or internal DNS zone configuration problems.

Quick Fix: Verify DNS resolution using nslookup smtp.example.com and Resolve-DnsName. Ensure firewall allows outbound UDP/TCP port 53 to DNS servers.

Read complete DNS troubleshooting guide →

Office365 Email Configuration

Problem: Emails fail to send through Office365/Microsoft 365 SMTP (smtp.office365.com) with authentication or connection errors.

Root Cause: SMTP Authentication disabled in Office365, MFA blocking password authentication, TLS 1.2 not enabled, or expired/changed passwords.

Quick Fix: Enable SMTP Authentication in Microsoft 365 admin center. For MFA-enabled accounts, generate app passwords. Ensure TLS 1.2 is enabled on your server.

Read complete Office365 configuration guide →

SSL/TLS Certificate Revocation Validation

Problem: Emails fail with "The revocation function was unable to check revocation for the certificate" when sending through SendGrid, Mailgun, or other SMTP providers.

Root Cause: Firewall blocking access to Certificate Revocation Lists (CRL) and OCSP endpoints (crl.godaddy.com, ocsp.digicert.com), missing CA certificates, or proxy configuration preventing certificate validation.

Quick Fix: Allow outbound HTTP (port 80) to *.godaddy.com and *.digicert.com for certificate validation. Install missing GoDaddy/DigiCert intermediate certificates. For v7.2+, consider the "Ignore certificate revocation errors" option as temporary workaround.

Read complete SSL/TLS troubleshooting guide →