We have just upgraded our 2017.0 to 2017.1.1.1 server and restored backup. We previously configured https on this machine. Anyone know if you can reuse the certificate on the same server? I would think that if I pasted the keystone file into the directory and made all the changes to the tomcat xml files it would work? Once I completed the FME Server Application Service would not startup and https isn't working? Any thought?
Best answer by jlutherthomas
Hi @brianapeters
As the original tomcat configuration should have been removed with the uninstall and new install of FME Server, I wouldn’t suggest copying the keystone file.
I’d suggest starting the HTTPS configuration from scratch, and see if that works.
If the web app server isn’t starting, you should be able to see errors in the tomcat log files that should hopefully point out why.
+2Hi @brianapeters
As the original tomcat configuration should have been removed with the uninstall and new install of FME Server, I wouldn’t suggest copying the keystone file.
I’d suggest starting the HTTPS configuration from scratch, and see if that works.
If the web app server isn’t starting, you should be able to see errors in the tomcat log files that should hopefully point out why.
My hunch is that you'll need a new certificate, since the private key generated by your new installation of FME Server won't be identical to your previous private key.
But it would be great if you could keep us updated here once you've tried.
We finally got this working. Looks like due to the full uninstall upgrade there is changes to the tomcat folder. This prevents you from re-using the certificate. We decided to completely start from scratch and in the end everything worked. The FME Server Application Service not starting was an human error. The permissions on the Engines service needed to be an admin account.
