Possible Errors
1. Your connection is not private
Resolution Path:
1. Check if the CNAME for the portal URL is present using this link CNAMELookup. If not present the issue is due to deleted CNAME or the right CNAME is not added.
2. To verify the CNAME details, use the query - "cname_domain" and in respective Haystack based on the pod details in Freshops. The CNAME(will be an alphanumberic.freshdesk.com) should pop up in the CNAMELookup as well. If it's not right, ask the customer to point to the right CNAME obtained from logs.
3. If there are no haystack logs available, go to step 4.
4. Navigate to Admin > Portal > Inspect and click on edit portal. In the Network logs, the generate_cname should have the CNAME in the response :
5. Once the above steps are verified and the portal is still not secure, proceed with the below steps.
6. Navigate to this link and choose the LetsEncrypt option from the Service Categories.
7. Choose the Get certificate in Domain controller from properties panel and submit.
8. If the certificate is created successfully, we get an update in the LH ticket as
9. Please move on to Custom SSL in DevOps and fill in the information and submit the Enable Custom SSL button
10. The site is secured, we can verify by visiting the site using chrome
11. If it's still not working, raise a L2 ticket.
Slack channel - fd-ssl for queries
Point of Contact - Roshan Borale