Skip to main content
Solved

upgrade to 2017.1.1.1 configuring https on same machine


Forum|alt.badge.img

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.

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

4 replies

Forum|alt.badge.img
If your request is time sensitive, please start a live chat session (www.safe.com/live-chat/) and reference your case number (C133215), or reply to this email and ask for your case to be escalated.

 

 

 


Forum|alt.badge.img+2
  • Best Answer
  • December 12, 2017

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.


david_r
Celebrity
  • December 12, 2017

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.


Forum|alt.badge.img

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.


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