cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

ThingWorx Navigate is now Windchill Navigate Learn More

Translate the entire conversation x

Flow Configuration Error

rattmice
14-Alexandrite

Flow Configuration Error

I'm having a problem getting Flow 10 to get configured with Foundation 10.  All the services start and I can connect to Foundation via the Flow nginx port but I get the following error when running WorkflowSubsystem.ValidateFlowSetup:

 

Found 1 issues. [FLOW-API-01] - Failed to connect to Flow: Internal Server Error For more information, refer to the 'Troubleshooting Your Installation' topic in the Help Center.

 

The ApplicationLog has these errors:

 

2025-11-21 14:29:06.092+0000 [L: ERROR] [O: c.t.s.s.f.WorkflowSubsystem] [I: ] [U: Administrator] [S: ] [P: ] [T: https-openssl-nio-8443-exec-7] Failed to get Delegated UserOAuths : Internal Server Error 
2025-11-21 14:29:06.092+0000 [L: ERROR] [O: c.t.f.f.FlowDelegatedOAuthFilter] [I: ] [U: Administrator] [S: ] [P: ] [T: https-openssl-nio-8443-exec-7] Unable to initialize session attributes

 I don't have SSO currently enabled although I did have it on in previous attempts so I'm not sure with there is an OAuth error.

ACCEPTED SOLUTION

Accepted Solutions
rattmice
14-Alexandrite
(To:Constantine)

Thanks but ErrorLog didn't really contain anything valuable.  The Flow exchange error had this:

{"module":"flow-exchange","timestamp":"2025-11-25T01:10:37.462Z","level":"error","message":"unauthorized access”}

And the Flow oauth log had this:

{"module":"flow-oauth","timestamp":"2025-11-25T01:09:33.307Z","level":"info","message":"inbound : Connection Failed:  {"code":"ECONNREFUSED"}"}

 None of the logs were very direct in indicating exactly what was wrong and the connection failed was difficult to track down because I could access everything via browser/curl.

In the end, it turned out that I messed up the orchestration.crt by following the instructions to generate those by hand instead of copying what was already there for Foundation.

View solution in original post

2 REPLIES 2

Just a generic advice, sorry -- try to check other log files, e.g. ErrorLog.log. They might contain more details about this issue, some stack traces and context information.


Vilia (my company) | GitHub | LinkedIn
rattmice
14-Alexandrite
(To:Constantine)

Thanks but ErrorLog didn't really contain anything valuable.  The Flow exchange error had this:

{"module":"flow-exchange","timestamp":"2025-11-25T01:10:37.462Z","level":"error","message":"unauthorized access”}

And the Flow oauth log had this:

{"module":"flow-oauth","timestamp":"2025-11-25T01:09:33.307Z","level":"info","message":"inbound : Connection Failed:  {"code":"ECONNREFUSED"}"}

 None of the logs were very direct in indicating exactly what was wrong and the connection failed was difficult to track down because I could access everything via browser/curl.

In the end, it turned out that I messed up the orchestration.crt by following the instructions to generate those by hand instead of copying what was already there for Foundation.

Announcements


Top Tags