Skip to main content
Question

Issues launching JSS after upgrade

  • March 6, 2017
  • 33 replies
  • 199 views

Show first post

33 replies

Forum|alt.badge.img+10
  • Valued Contributor
  • March 6, 2017

@BreakingZeus - excellent. That's the way to do it.


Forum|alt.badge.img+9
  • Contributor
  • March 6, 2017

@Typhoon_87 Yes!

I was getting a ERR_SSL_VERSION_OR_CIPHER_MISMATCH when logging into the JamF server after restoring my original keystore and certs.

I'm in the process now of creating a new keystore with newly generated certs, I'm currently waiting on my return request cert to import (My web admin has to do this)

I'll let you know if it helps


Forum|alt.badge.img+9
  • Valued Contributor
  • March 6, 2017

I had the same issue this morning, DB Connection Error. Windows Server 2008 R2. As has been mentioned, the Database.xml file had the user and password entries actually change from what I set them originally as to the defaults in the admin guide. This was done in Dev, so no real fire but it's another in the line of installs gone sideways. Stay safe out there...


Forum|alt.badge.img+9
  • Valued Contributor
  • March 6, 2017

I had the same issue this morning, DB Connection Error. Windows Server 2008 R2. As has been mentioned, the Database.xml file had the user and password entries actually change from what I set them originally as to the defaults in the admin guide. This was done in Dev, so no real fire but it's another in the line of installs gone sideways. Stay safe out there...


Forum|alt.badge.img+2
  • New Contributor
  • March 6, 2017

@FastGM3 Thank you I do have a case open but have not heard back since this morning. Assuming their support is inundated with users who suffered through this. I keep getting

Your changes have not been saved.

Could not create the certificate


Forum|alt.badge.img+9
  • Contributor
  • March 6, 2017

Typhoon_87 new certs worked for me, I'm back up and running.

Good Luck


Bcodom
Forum|alt.badge.img+4
  • Contributor
  • March 7, 2017

I made one of the posts that @lehmanp00 commented about. I found out that we had a previous snapshot in place back in July of 2016, so I reverted back to that snapshot (thank goodness for VMWare snapshots), and I upgraded to version 9.97.1482356336, and recovered the database to the most recent version (thankfully it was a snapshot before the botched upgrade). So I have recovered very well.

I would say the easiest option is to recover from a previous snapshot or backup if you are able to, otherwise it does look like you may have to reinstall the whole thing.

Also, before I reverted back, I did have two JSS instances in Add/Remove Programs. I'm going to be contacting my Jamf buddy and inform him about this update. I don't think I am going to update until this has been resolved.

This is probably another good point to make: If you don't have a dev server or don't do this already, backup your server or create a snapshot if you run it on a VM. It comes in VERY handy!


Forum|alt.badge.img+17
  • Contributor
  • March 7, 2017

Hey all,

If you're experiencing this issue, and have not already, please contact support.

Thanks!
Amanda Wulff
Jamf Support