ThingWorx Flow Error [FLOW-API-01] after regenerating self-signed certificate

[GabrielAzevedo]

Hi everyone,

I am running ThingWorx Flow 9.3.10 and I’m hitting a wall trying to fix an expired self-signed certificate.

The Issue: My self-signed certificate for Flow expired, so I needed to regenerate it. I followed the official guide here: CreateSelfSignedCertificate.html

I generated the new files, placed them in the SSL directory, and restarted the services. However, Flow is now failing to connect.

Symptoms:

1. Redirect Loop: When I try to open the ThingWorx Flow app, it automatically redirects me back to the ThingWorx Composer.

2. Validation Error: When I run ValidateFlowSetup in the WorkflowSubsystem, I get:

   [FLOW-API-01] - Failed to connect to Flow: Internal Server Error

3. Log Error: The flow-exchange module logs show this error, which suggests a trust issue:

   {"module":"flow-exchange","timestamp":"...","level":"error","message":"unauthorized access"}

It seems like the internal services aren't accepting the new certificate I generated. Has anyone experienced this? Is there an extra step missing in the documentation to update the internal TrustStore or Keystore?

Any advice would be appreciated.

Thanks!

[abandal]

Hello @GabrielAzevedo,

Please provide the following information:

• OS and version 
• ThingWorx Platform version 
• Port used for accessing ThingWorx Platform and Flow 
• Whether ThingWorx Platform is accessible via the nginx (Flow) port 
• Whether Flow is installed on the same machine as ThingWorx Platform 
• Whether Flow was working as expected before the self-signed certificate update 

• Please also ensure:
  • The **Issued To** name on the certificate must match the hostname of the ThingWorx Flow server to avoid certificate-related errors 
  • `server_name` is correctly set in `<nginx_home>\conf\conf.d\vhost-flow.conf` 
  • `extra.crt` and `orchestration.crt` files match 

Regards,

Abhi