Article - CS371329
"Invalid Connector" Is Seen When Creating a Connector After Loading OAuths in ThingWorx Flow
Modified: 24-Jun-2022
Applies To
- ThingWorx Platform 9.0 to 9.3
Description
- Invalid Connector when using Nodes/Triggers (Ex. Gmail - Send and Email)
- Getting the following Errors after loading OAuths:
- [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.
- [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.
- Seeing the following errors within <Flow>\pm2\logs\oauth-error.log:
- {"module":"flow-oauth","timestamp":"<Timestamp>","level":"error","message":"OAuth module is not found for <OAuth> ,error message is Cannot find module <Partial stack trace> stack trace is Error: Cannot find module <Full error stack>"}
- Unable to create OAuth based Connect in ThingWorx Flow after executing the LoadOAuthConfigurations service
- Seeing "Invalid Connector" or "Unable to Validate Connector" even though the OAuth Client ID and Client Secret are correct
This is a printer-friendly version of Article 371329 and may be out of date. For the latest version click CS371329