Article - CS315901
Configuring SSL for ThingWorx Flow results in "NET::ERR_CERT_COMMON_NAME_INVALID" and other errors
Modified: 29-Apr-2026
Applies To
- ThingWorx Platform 8.4 to 10.1
- ThingWorx Flow
Description
- How to configure ThingWorx Flow to work with a certificate signed by a well-known Certificate Authority (CA)
- Need to implement ThingWorx Flow SSL to work with a custom root Certificate Authority
- Have to change ThingWorx Flow from using Self-Signed Certificate
- What SSL/TLS options are available for ThingWorx Flow?
- Chrome shows NET::ERR_CERT_COMMON_NAME_INVALID when trying to access Composer or Flow
- SSL_ERROR_BAD_CERT_DOMAIN seen in Firefox when trying to access the Fully Qualified Domain Name of the ThingWorx host
- ThingWorx Flow installs successfully, but the dialog for login never appears
- Self-signed certificate appears in ThingWorx Flow URL when CA signed certificate is expected
- Cannot access ThingWorx Flow after renewing SSL certificate
- Using the WorkflowSubsystem service ValidateFlowSetup, the following message is returned:
-
Found 2 issues. [FLOW-API-02] - Failed to connect to Flow. Ensure that you are accessing ThingWorx via Nginx URL. Ensure that all Flow services are running and are healthy. In case of self-signed certificate, make sure that correct CN is provided. [FLOW-OAUTH-02] - Failed to connect to Flow OAuth service. Check whether Flow keys are imported in ThingWorx KeyStore. For more information, refer to the 'Troubleshooting Your Installation' topic in the Help Center.
-
This is a printer-friendly version of Article 315901 and may be out of date. For the latest version click CS315901