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?

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. 

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. 

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

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

Any updates on this?

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)

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.