-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
12
-
Severity 3 - Minor
Issue Summary
Hello team,
When the customer is trying a custom email option for their Statuspage and when they are facing issues with DKIM validation the error noticed on the customer end is invalid.
In one example the customer got the error: "There was a problem on our side when checking this. Try hitting the 'Revalidate All Records' button above, or contacting support."
In some cases, this seems to happen if the domain is already registered with Mailgun for another service - In other cases, this seems to be a backend error preventing the DKIM configuration/validation.
Steps to Reproduce
- Configure a custom "Send from email"
- Check the "DNS Configuration" tab
Expected Results
The DKIM #1 expected hostname/values should appear, or in case the domain is already registered with Mailgun, it should warn the user explicitly
Actual Results
The error generated on the admin panel at customer end states "There was a problem on our side when checking this. Try hitting the 'Revalidate All Records' button above, or contacting support." causes confusion that the issue is at Statuspage end
Workaround
Contact Statuspage support at https://support.atlassian.com/contact/#/
[STATUS-727] Generic / Invalid error on Statuspage DNS for DKIM validation issues
| Support reference count | Original: 11 | New: 12 |
| Support reference count | Original: 10 | New: 11 |
| Support reference count | Original: 9 | New: 10 |
| Description |
Original:
h3. Issue Summary
Hello team, When the customer is trying a custom email option for their Statuspage and when they are facing issues with DKIM validation the error noticed on the customer end is invalid. In one example the customer got the error: "There was a problem on our side when checking this. Try hitting the 'Revalidate All Records' button above, or contacting support." In some cases, this seems to happen if the domain is already registered with Mailgun for another service - In other cases, this seems to be a backend error preventing the DKIM configuration/validation. h3. Steps to Reproduce # Configure a custom "Send from email" # Check the "DNS Configuration" tab h3. Expected Results The DKIM #1 expected hostname/values should appear, or in case the domain is already registered with Mailgun, it should warn the user explicitly h3. Actual Results The error generated on the admin panel at customer end states "There was a problem on our side when checking this. Try hitting the 'Revalidate All Records' button above, or contacting support." causes confusion that the issue is at Statuspage end h3. Workaround NA |
New:
h3. Issue Summary
Hello team, When the customer is trying a custom email option for their Statuspage and when they are facing issues with DKIM validation the error noticed on the customer end is invalid. In one example the customer got the error: "There was a problem on our side when checking this. Try hitting the 'Revalidate All Records' button above, or contacting support." In some cases, this seems to happen if the domain is already registered with Mailgun for another service - In other cases, this seems to be a backend error preventing the DKIM configuration/validation. h3. Steps to Reproduce # Configure a custom "Send from email" # Check the "DNS Configuration" tab h3. Expected Results The DKIM #1 expected hostname/values should appear, or in case the domain is already registered with Mailgun, it should warn the user explicitly h3. Actual Results The error generated on the admin panel at customer end states "There was a problem on our side when checking this. Try hitting the 'Revalidate All Records' button above, or contacting support." causes confusion that the issue is at Statuspage end h3. Workaround Contact Statuspage support at [https://support.atlassian.com/contact/#/] |
| Support reference count | Original: 8 | New: 9 |
| Support reference count | Original: 7 | New: 8 |
| Support reference count | Original: 6 | New: 7 |
| Security | Original: Atlassian Staff [ 10750 ] |
| Description |
Original:
h3. Issue Summary
Hello team, When the customer is trying a custom email option for their Statuspage and when they are facing issues with DKIM validation the error noticed on the customer end is invalid. In one example the customer got the error: "There was a problem on our side when checking this. Try hitting the 'Revalidate All Records' button above, or contacting support." Upon further investigation, we found that the issue with DKIM validation was due to the customer domain being used on the customer side in a different service under the Mailgun. This is reproducible on Data Center: (yes) / (no) NA h3. Steps to Reproduce NA h3. Expected Results Provide a specific error on Statuspage admin panel for customers to avoid any confusion h3. Actual Results The error generated on the admin panel at customer end states "There was a problem on our side when checking this. Try hitting the 'Revalidate All Records' button above, or contacting support." causes confusion that the issue is at Statuspage end h3. Workaround NA |
New:
h3. Issue Summary
Hello team, When the customer is trying a custom email option for their Statuspage and when they are facing issues with DKIM validation the error noticed on the customer end is invalid. In one example the customer got the error: "There was a problem on our side when checking this. Try hitting the 'Revalidate All Records' button above, or contacting support." In some cases, this seems to happen if the domain is already registered with Mailgun for another service - In other cases, this seems to be a backend error preventing the DKIM configuration/validation. h3. Steps to Reproduce # Configure a custom "Send from email" # Check the "DNS Configuration" tab h3. Expected Results The DKIM #1 expected hostname/values should appear, or in case the domain is already registered with Mailgun, it should warn the user explicitly h3. Actual Results The error generated on the admin panel at customer end states "There was a problem on our side when checking this. Try hitting the 'Revalidate All Records' button above, or contacting support." causes confusion that the issue is at Statuspage end h3. Workaround NA |
| Support reference count | Original: 5 | New: 6 |