Skip to main content
Solved

FME Flow 2025.1 Distributed deployment in Azure - Unable to Run a workspace

  • August 4, 2025
  • 2 replies
  • 77 views

tp_atkins
Contributor
Forum|alt.badge.img+1

I have just deployed a distributed Flow (2025.1) in Azure with following configurations (this is to replace a similar deployment in Azure with 2021.1 FME Server version)

Core machine - 1

Engine machine -1

Azure storage account

Azure hosted postgresql flexible server

Azure application gateway

 

In addition to the internal load balancer Azure creates as part of the deployment, we also have a public load balancer associated with the core VM to allow outgoing external traffic.

A backup of the configurations from the 2021.1 FME Server is restored to the 2025.1 using the backup/restore fucntion in FME Flow. (Used an intermediate version 2024.2 to restore a backup from 2021.1 and then created a backup to restore to 2025.1, no error and everything works fine in Automation mode) 

However when select a workspace and ‘Run Workspace’ option is selected, it throws a message saying: There was an error submitting the job. This is same for any workspaces (Sample, test and project specific). The error is 301 Moved Permanently.

 

In addition, if trying to upload a file from local machine, it throws another error called ‘There was  a problem communicating with the REST API.

No sure these are related. Anyone who has deployed FME Flow in Azure as distributed deployment and familiar with what I see above? 

Thomas

Best answer by hkingsbury

a few things to check here:

  • What url do the services have? (under System Config, Networking and Email)
  • In your screenshots, what url are the network calls going to?
  • Where are your load balancers pointing? To the existing Flow, or the new one?
  • What is FME_SERVER_WEB_URL set to in fmeFlowConfig.txt?

 

Also have a look through here: https://support.safe.com/hc/en-us/articles/25407364556941-FME-Flow-Troubleshooting-Guide

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

2 replies

hkingsbury
Celebrity
Forum|alt.badge.img+63
  • Celebrity
  • 1632 replies
  • Best Answer
  • August 4, 2025

a few things to check here:

  • What url do the services have? (under System Config, Networking and Email)
  • In your screenshots, what url are the network calls going to?
  • Where are your load balancers pointing? To the existing Flow, or the new one?
  • What is FME_SERVER_WEB_URL set to in fmeFlowConfig.txt?

 

Also have a look through here: https://support.safe.com/hc/en-us/articles/25407364556941-FME-Flow-Troubleshooting-Guide


tp_atkins
Contributor
Forum|alt.badge.img+1
  • Author
  • Contributor
  • 5 replies
  • August 5, 2025

@hkingsbury Many thanks for pointing out the FME_SERVER_WEB_URL parameter, which was the issue. It was pointing to the http:appgateway:80 rather than https. After updating this, I also updated the ‘Change allhosts’ and that sorted everything.

Best Thomas