Full Guide: FME Flow Troubleshooting Guide
Are you encountering issues connecting a web service to FME Flow (formerly FME Server)?
Many workspaces that are run from FME Flow require you to connect and authenticate to a web service. FME Flow allows you to securely upload, store and reference your own authentication parameters with Web and Database Connections. And just like in FME Workbench, connections to web services are safely stored as self-contained objects. Once uploaded to FME Flow, the Web Connections page provides a convenient management hub.
Note that Web and Database Connections previously shared the same troubleshooting article. We have since broken the article into separate articles so we could expand on each topic as well as it would be easier to find via search. Please navigate to FME Flow Troubleshooting: Database Connections article for troubleshooting database connections in FME Flow.
Content Overview
- General Troubleshooting
- Getting Started
- Relevant Logs
-
Common issues
- After upgrading FME Flow, my web connection stopped working
- Unauthorized request by user due to lack of proper permissions
- How can multiple users share web connections on FME Flow?
- How do I enable an OAuth web connection to authenticate from my private network?
- My web connection works in FME Workbench, but not FME Flow
- Additional Resources
General Troubleshooting
-
Has the connection been uploaded from FME Form (formerly FME Desktop) and is it up-to-date?
-
Has the Web Service been configured correctly from FME Workbench?
When a web connection fails on FME Flow only after some period of time, but still connects from FME Workbench, this is a tell-tale sign that your web connection is not authorized with FME Flow. Many web services require specific configuration on FME Flow to authenticate.
You'll need to create a new App from the web service you are trying to connect to. After creating the App, update the client and secret in the FME Workbench web service then reupload the web connection to FME Flow. For more instructions, please review the documentation for Managing Web Services.
(TIP: In most cases, the Web Service Redirect URI should be "<yourFMEFlow>/fmeoauth")
-
Have you checked the FME Flow fmeoauth.log for errors or warnings?
This log can be found from the FME Flow Web UI, under Resources > Logs > service > current > fmeoauth.log
- If you are receiving a web connection error while running a job, have you tried Log Debug?
In FME Workbench, enable Log Debug under Tools > FME Options > Translation > Log Message Filter. Then, republish to FME Flow and rerun the job. Check the job log again. Log Debug mode may provide more information, like access token expiry times and API call details.
Getting Started
If you're looking for general information about web connections, these pages are great places to start:
Relevant Logs
See Troubleshooting with Logs for where to find log files.
Logs > service > current > fmeoauth.log
Logs > core > current > fmeconnection.log, fmeserver.log
Common Issues
“After upgrading FME Flow, my web connection stopped working”
See our known issues in FME 2021.x. or 2022.x.
If the problem does not correspond to a known issue, please ensure all original network settings have been migrated to the upgraded FME Flow.
"How do I give permission for other users to use my web connections?”
Unauthorized request by user due to lack of proper permissions
Often, this error comes down to user permissions to connections and resources. Please review FME Flow Connections Runtime Error: Unauthorized request by user due to lack of proper permissions for possible causes and how to resolve the error.
"How can multiple users share web connections on FME Flow?"
The solution for sharing connections often begins with desktop connection management. Once workspaces are uploaded, they can easily share connections by referencing the same named connection. Consult Making Database and Web Connections Public for best practices.
“How do I enable an OAuth web connection to authenticate from my private network?”
Some web services require a Public DNS. There are a few ways to do this, so we recommend consulting your organization’s IT services first. For our documentation on the process, please consult Enabling FME Flow for Public Access.
Note: not all web services require a Public DNS. Some examples of web connections that do not require a public DNS include ArcGIS Online and Microsoft Graph.
“My web connection works in FME Workbench, but not FME Flow”
Republish the web connection from FME Workbench.
For OAuth web connections, consult Configuring FME Flow to use OAuth-based Web Connections.
- Authorize the web connection in FME Flow.
- Configure the web service in FME Flow. Some web services required further configuration to be compatible with FME Flow, e.g.
- Remove the web service, republish from FME Workbench, and reauthorize from FME Flow.
Additional Resources
Are you still experiencing issues?
Please consider posting to the FME Community Q&A if you are still experiencing issues that are not addressed in this article. There are also different support channels available.
Have ideas on how to improve this?
You can add ideas or product suggestions to our Ideas Exchange.
Comments
0 comments
Please sign in to leave a comment.