Skip to main content

We (APA) are facing issues with security certificate installed on our FME Server.

The certificate has expired and we are not able to update it with new valid cert.

 

We have followed the workflow mentioned here: https://community.safe.com/s/article/Configuring-FME-Server-for-HTTPS-Updating-an-expired-Certificate

We completed all these steps but still not successful.

when we connect we still see old expired cert on browser.

Couple of things could be happening

  • Your browser might be caching the certificate, try in another browser or try with a incognito session
  • You might have a loadbalancer or reverse proxy or similar in place that is applying a certificate
    • Try logging onto the server hosting FME Flow and browsing to https://localhost:<port> and see what certificate is being used (you will get a warning about an invalid certificate, this is fine as the cert will be for <url> not localhost)

Couple of things could be happening

  • Your browser might be caching the certificate, try in another browser or try with a incognito session
  • You might have a loadbalancer or reverse proxy or similar in place that is applying a certificate
    • Try logging onto the server hosting FME Flow and browsing to https://localhost:<port> and see what certificate is being used (you will get a warning about an invalid certificate, this is fine as the cert will be for <url> not localhost)

Hi @hkingsbury​ 

 

Morning from Australia.

Thanks for your suggestions.

  • I tried going to FME Server landing page via incognito...same behaviour.
  • I went to FME Server landing page via private IPV4 address. Same warning. There as well the cert is expired and shows that cert is issued to the CNAME. I have engaged our networks team to understand if there is a load balancer in between and if yes, can we replace the cert there. I will try doing this step using localhost as well.

 

Any other amazing suggestions/checks?

 

Regards

Vagish

 


Reply