All Collections
Support
Certificate Request Failed
Certificate Request Failed

If your custom domain request fails and you receive one of the following error messages, follow the suggested steps to fix the problem.

Jazz Prado avatar
Written by Jazz Prado
Updated over a week ago

If you receive one of the following error messages, please follow the suggested steps to fix the problem. After resolving the problem, please submit a new custom domain request.
​

Topics

  • Error message: Domain Not Allowed

  • Error message: Additional Verification Required

  • Error message: Invalid Public Domain

  • Error message: No Available Contacts

  • Error message: Other


Error message: Domain Not Allowed

One or more of the domain names in the certificate request was reported as unsafe by VirusTotal. To fix the issue, please try the following:

  • Search for your domain name on the VirusTotal website. If your domain is reported as suspicious, please read Google Help for Hacked Websites for more information.

  • If you believe that the result is a false positive, notify the organization that is reporting the domain. VirusTotal is an aggregate of several antivirus and URL scanners and cannot remove your domain from the blacklist itself.

Once the underlying issue is fixed and the VirusTotal registry has been updated, you can request a new certificate.


Error message: Additional Verification Required

AWS Certificate Manager (ACM) requires additional information to process this certificate request. This can happen as a fraud-protection measure, such as when the domain ranks within the Alexa top 1000 websites. To provide the required information, please contact us at support@beam.gg.
​

Note: You cannot request a certificate for Amazon-owned domain names such as those ending in amazonaws.com, cloudfront.net, or elasticbeanstalk.com.


Error message: Invalid Public Domain

One or more of the domain names in the certificate request is not valid. Typically, this is because a domain name in the request is not a valid top-level domain.
​
Try to request a certificate again, correcting any spelling errors or typos that were in the failed request, and ensure that all domain names in the request are for valid top-level domains. For example, you cannot request an ACM certificate for example.invalidpublicdomain because "invalidpublicdomain" is not a valid top-level domain.

If you continue to receive this failure reason, please contact us at support@beam.gg.


Error message: No Available Contacts

You chose email validation when requesting a certificate, but AWS Certificate Manager (ACM) could not find an email address to use for validating one or more of the domain names in the request. To correct this problem, you can do one of the following:

  • Ensure that you have a working email address that is registered in WHOIS and that the address is visible when performing a standard WHOIS lookup for the domain names in the certificate request. Typically, you do this through your domain registrar.

  • Ensure your domain is configured to receive email. Your domain's name server must have a mail exchanger record (MX record) so ACM's email servers know where to send the domain validation email.

Accomplishing just one of the preceding tasks is enough to correct this problem; you don't need to do both. After you correct the problem, please request a new certificate.

If you follow these steps and continue to get the No Available Contacts message, please contact us at support@beam.gg.


Error message: Other

Typically, this failure occurs when there is a typographical error in one or more of the domain names in the certificate request. Try again to request a certificate, correcting any spelling errors or typos that were in the failed request. If you continue to receive this failure message, please contact us at support@beam.gg.

Did this answer your question?