Skip to main content
Solved

Unable to connect to FME Flow

  • October 1, 2024
  • 8 replies
  • 496 views
djmcdermott
Contributor
Forum|alt.badge.img+6

Hello FME’ers.

We recently upgraded our FME Flow and FME Form instances from 2023.1 to 2024.1 (Build 24622). FME Flow is installed as an express installation on single Windows Server 2016 and is configured to use HTTPS and Azure AD. FME Form is also installed on the server and my laptop. 

When testing the connection from Form to Flow on my laptop everything was fine. I way able to connect and upload/download workbenches. However, I am unable to do the same on the server itself. When connecting as Admin, I get:

Login failed (Connection Error) - Unable to connect to FME Flow.

When trying to connect was my user I get:

Connection Storage: Request to update access token failed. (HTTP Error 'HTTP/1.1 400')

I then went to refresh the Azure AD connection and got the following error:

Server's certificate does not match the URL.
Client does not have access to any certificates from the following issuers:
Go Daddy Secure Certificate Authority - G2
Go Daddy Root Certificate Authority - G2

I am able to get to the FME Flow Web UI through a browser on the server and the certificates are valid.

Please help.

David

Best answer by TandraAtSafe

Hi @djmcdermott 

I see that you are using Windows Server 2016 as the operating system. It was recently discovered that there is a compatibility issue between Form 2024 and connecting to Flow on Windows Server 2016.

Unfortunately our recommendation is to upgrade to Windows Server 2022 since Microsoft ended mainstream support for Windows Server 2016 in 2022. If you have any further questions about this our support team can provide more information if you wish to submit a support ticket. 

View original
Did this help you find an answer to your question?

8 replies

hkingsbury
Celebrity
Forum|alt.badge.img+53
  • hkingsburyCelebrity
  • Celebrity
  • October 1, 2024

Just clarifying, you’re seeing two different issues here? one connecting to Flow via Form on the server, then second being unable to connect to Azure AD

 

For the first, On the server, are you connecting as Localhost, or using the full URL? you could try deselecting ‘Verify HTTPS Certificates’ under the webconnection
 

 

For the second, It’s possible the machine may not have those intermediary certificates installed, in which cause you’ll need to install them from Go Daddy. Additionally, is the server whitelisted to connect to Azure in the firewalls?

 

 

djmcdermott
Contributor
Forum|alt.badge.img+6
  • djmcdermottContributor
  • Author
  • Contributor
  • October 2, 2024

Hi @hkingsbury. Thank you for your response. 

I have tried the connection as the FQDN and https://localhost with the “Verify HTTPS Certificates” checked on and off. I get the same result. 

The GoDaddy Root and intermediate certificates are installed and in date. They are in Certificates - Local Computer > Trusted Root Certificate Authority > Certificates. 

I can ping from the server to https://login.microsoftonline.com so I assume it can connect out. 

TandraAtSafe
Safer
Forum|alt.badge.img+7
  • TandraAtSafeSafer
  • Safer
  • Best Answer
  • October 3, 2024

Hi @djmcdermott 

I see that you are using Windows Server 2016 as the operating system. It was recently discovered that there is a compatibility issue between Form 2024 and connecting to Flow on Windows Server 2016.

Unfortunately our recommendation is to upgrade to Windows Server 2022 since Microsoft ended mainstream support for Windows Server 2016 in 2022. If you have any further questions about this our support team can provide more information if you wish to submit a support ticket. 

Tandra G (Technical Support Specialist)
djmcdermott
Contributor
Forum|alt.badge.img+6
  • djmcdermottContributor
  • Author
  • Contributor
  • October 8, 2024

Thank you @TandraAtSafe. Is there a record of this bug somewhere? 

TandraAtSafe
Safer
Forum|alt.badge.img+7

We do have an internal ticket for this issue: FMEFORM-31805 but no known bug article yet. 

Tandra G (Technical Support Specialist)
tino
Contributor
Forum|alt.badge.img+17
  • tinoContributor
  • Contributor
  • October 31, 2024
TandraAtSafe wrote:

We do have an internal ticket for this issue: FMEFORM-31805 but no known bug article yet. 

Any updates on this?

sandrab
1 person upvoted this
  • sandrab
    sandrab
tino
Contributor
Forum|alt.badge.img+17
  • tinoContributor
  • Contributor
  • November 4, 2024

Okay, there is a article available on this issue:
https://support.safe.com/hc/en-us/articles/31497316396301-Known-Issue-FME-Form-HTTPS-Connection-Fails-on-Windows-Server-2016


But in my opinion this issue is so critical, that Windows Server 2016 (which is supported until Jan 2027) should be removed from the list of supported platform on https://support.safe.com/hc/en-us/articles/25407433729933-FME-Platform-Technical-Specifications

(At least until FME Form 2024.2.1 is released)

agelfert
Contributor
Forum|alt.badge.img+8
  • agelfertContributor
  • Contributor
  • December 3, 2024

For what it’s worth, I can confirm that upgrading to Windows Server 2019 solves the issue.

I do a lot of FME Desktop development in a server environment. So, going server to server when publishing is pretty much my standard MO. After upgrading to FME Flow 2024.2 (why the name change - argh?!), I was wanting to be on the latest Desktop version and went to FME Form 2024.2. Publishing from FME Desktop 2022 to Flow 2024.2 worked fine but from Form 2024.2, I was getting the same:

Login failed (Connection Error) - Unable to connect to FME Flow.

Once server team got me to Win Server 2019, I’m a happy camper again.

Reply


Helpful Members This Week

Community Stats

31,233
Posts
118,432
Replies
38,828
Members

Latest FME

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.