Overview

You have configured your SSL certificate for your custom domain (for PWA and/or Client Panel) so it can be secure, but there appears to be a problem when accessing your custom domain. This article explains why this might happen and how you can work around it.

Diagnosis

You got one of the following errors:

• Your custom domain seems to be broken having an invalid certificate name. For instance:

• Your connection is not private:

• SSL error when trying to access the PWA or the Client Panel. For instance, you get the following message:

Back to Top 

Solution

Below you can find a list of things to check to troubleshoot your problem and the corresponding solutions.

1. Check that the SSL certificate is valid.

Most of the industry browsers have a padlock next to the URL. You can click on that padlock on the address bar to view the certificate information. All digital certificates have a finite lifespan and are no longer recognized as valid upon expiration. So you need to check if they’ve expired.

There are various ways to check the validity. For instance, the Google Chrome browser has added an option to show automatically if the SSL certificate is valid

If you click on that link you can check when the SSL certificate expires

If you find out that the SSL certificate is not valid, you will have to contact the Certificate Authority and request for a new certificate

2. Check the CNAME record and confirm if it was configured correctly

• For issues with the PWA URL you can use the DNS Checker to confirm the availability of the CNAME
  • Check on the CMS platform to see if the custom domain is set properly. Follow the Testing Section of the Adding a Custom Domain for a Progressive Web App PWA KB article.  
  • If there is still an issue, reach out to your CNAME hosting provider to verify the configs and DNS resolution for the subdomain linking.
• For issues with the Subdomain Client Panel you can use DNS Checker to check and confirm that the subdomain is set up correctly and points to cms.mobileapphelper.com with a CNAME record.
  • If it is not correct, please check your subdomain set up. For instance, if you have used the GoDaddy service to set your subdomain, You can check the Setting up a GoDaddy subdomain KB article for more information. 
  • For more information, please refer to the following KBs:
    • Adding a Subdomain URL Link for the Client Panel
    • Cannot login to CMS using the subdomain URL

3. If the above didn’t help you and you still cannot figure out what the issue is, please contact Support providing the domain you are having issues with and the steps you’ve already taken. The BiznessApps Support team will run some checks on their own and – if needed – will escalate the issue to our Engineering team.

Back to Top 

Testing

You will be able to access your web app and/or your Client Panel through your Custom Domain URL.

Back to Top 

Related Articles

• Setting up a GoDaddy subdomain
• Adding a Subdomain URL Link for the Client Panel
• Cannot login to CMS using the subdomain URL