I have installed FME Flow 2026.1 in AWS has a High Availability WebUI/Core with distributed engines.
The setup uses HTTPS on an internal url (corporate network)
When I try to connect FME Form to Flow, I get the following error message
Unable to retrieve public key from Flow Unable to establish secure communications with Flow Deployment parameter access failed (Connection Error) - Unable to connect to FME Flow.
Has anybody seen this before? Thanks
When I use the url in the browser on the same machine (tested on 2 different machines), i can log in using my admin user account
Best answer by anryan
@zoe.forbes sorry I don’t have a ticket number. We just send an email to our Safe vendor/reseller with questions.
I would love to know what the proper process and tools are used to submit support tickets. Thanks.
The account I was using was the default admin account to connect Form to Flow.
I had to reinstall FME Flow 2026.1 in our AWS account again using the same default admin account and now it’s working. The only difference with this install compared to the previous install was I used FQDN for the hosts in the install wizard and it all works now. The short name and FQDN both resolved to the EC2s IP addresses.
Also, I just tried connecting using SAML and that worked as well.
Can you please confirm you’re not encountering the following known issue? It should be have been fixed but it would be good to double check:
Assuming this isn’t the problem, I had a look for your support ticket but I can’t find it in our system - could you please send your 5-digit ticket number? Feel free to do this here or over DM.
@zoe.forbes sorry I don’t have a ticket number. We just send an email to our Safe vendor/reseller with questions.
I would love to know what the proper process and tools are used to submit support tickets. Thanks.
The account I was using was the default admin account to connect Form to Flow.
I had to reinstall FME Flow 2026.1 in our AWS account again using the same default admin account and now it’s working. The only difference with this install compared to the previous install was I used FQDN for the hosts in the install wizard and it all works now. The short name and FQDN both resolved to the EC2s IP addresses.
Also, I just tried connecting using SAML and that worked as well.
Sorry for the delayed response. I hope the problem has been solved by now!
Posting on the Community and reaching out to your vendor is the best way to get support - they’ll reach out to us if necessary. Users who purchase FME through Safe directly get support here, but this channel follows our support policy which is likely different than your vendor’s.
Please let me know if you have any questions about this!
