-
Type:
Suggestion
-
Resolution: Unresolved
-
Component/s: Domain Verification - Initial Setup
-
None
-
2
Problem Definition
When attempting to Verify a Domain using the HTTPS File method, if the Domain Check fails, a generic error is presented stating that there is a problem and to check for a valid SSL Certificate :
If the Browser's Network Console is reviewed, reasons are presented to the Organization Admin; for example:
Too many redirects/invalid redirect:
message:"Domain could not be verified" reason:"Redirections other than https://example.com -> https://www.example.com are not supported"
File does not exist:
message: "Domain could not be verified" reason: "Request (method=GET;protocol=https:;hostname=example.com;port=443;path=/atlassian-domain-verification.html) returned unexpected HTTP response code: 404"
Suggested Solution
Update the UI error message to match what is seen within the Browser console
Why this is important
A more accurate error message being presented would help Organization Admins identify possible solutions if they experience issues with the HTTPS File domain verification method
Workaround
As an Organization Admin experiencing issues with the HTTPS File verification method, check the Browser Network Console to view additional details about the error.