We are running into the issue as well, we have an open support case with JAMF and their engineering team is looking into it. From looking at the logs of my iPad in iOS Console it appears to be related to SSL.

Code=-1200 "An SSL error has occurred and a secure connection to the server cannot be made."

Do you have a case number we might be able to reference?

Us too. waiting on a case number.

Looks like it updated yesterday:
Updated: Jan 24, 2016
https://itunes.apple.com/us/app/self-service-mobile/id718509958?mt=8&ign-mpt=uo%3D4

product issue (D-010095)

Hi all,

Thank you very much for bringing this to our attention. We were wondering if you would be able to update your ciphers on your JSS by following this article:

https://jamfnation.jamfsoftware.com/article.html?id=384

After following this workflow please attempt to open Self Service Mobile once more.

Also, don't hesitate to reach out to JAMF Support by creating a support ticket under more > my support, calling into the general support line at 612-216-1296, or emailing support@jamfsoftware.com

Best,

Christian Dooley
JAMF Support

Hi,
Just a +1 for fixing your cyphers :)
This did not require anything on the other end, iPad: Self Service worked as soon as cyphers fixed and Tomcat restarted

We figured it was going to be a cipher thing. Unfortunately for us we can't just make a change in our server.xml. Our clustered environment is behind a load balancer and our load balancer is what is serving SSL. So we are going to have to re-compile pound to support all the new ciphers. It will be good in the long run, just a pain up front.

Updated the ciphers on both our internal and DMZ server, still getting unable to connect to server.

Updating the ciphers worked perfectly. Thank you!!

Anyone not have the ciphers fix the issue. I only have a handful affected. Thanks

I do have this issue on self-service web app. So far after using ciphers fix it works.

We struggled with this the past two days. The cipher fix didn't do it for us. What did do it was updating the Java JDK to 1.8(was on 1.6). After doing both Self Service sprung to life.

Upgrading our load balancer to incorporate all the new cipher suites fixed our issue.

Ciphers fix has not worked here... JSS 9.82 with 1300 iPad Air devices running iOS 9.2.1

I'm assuming that your java instance on the server is current? Have you reached out to your TAM?

Yup, Java version 1.8.0_45

Haven't contacted TAM yet as I often get a good fix right here on the forums. The WebClip works fine as a backup for now, so I'm tempted to hang on to see what the community can dig up.

The JDK right and not just the standard plugin? I installed mine per this article: https://jamfnation.jamfsoftware.com/article.html?id=28

Looks like our JSS had an sha1 cert... replaced that and we were running again.

Our JSS also had a SHA1 cert. We were planning on replacing the cert this summer, just got pushed up a bit.

Sadly it seem my issue is back after running awhile.... Anyone got update how to resolve this issue?

So, I'm pretty sure that I'm seeing issues with latest Self Service Mobile due to a ciphers issue on our load balancer* (A10) ... external testing (i.e. not under lb) is fine as ciphers are good to go on JSS web apps.

That said, I'm seeing fails across the board (internal/external) when I switch out to JAVA 8 (.65 and .71) ... haven't tested downlevel versions of 8.

When I switch back to JAVA 7 (update-alternatives --config java), I only see the fail internally due to aforementioned (likely) load balancer cipher issue.

Sorry for random thoughts, and I'll update if things change/more info to add.

*Unfortunately, I don't own the means of production re: load balancer, so waiting on another team for fix of that issue.

@joshbuddy We are also using pound and it looks like we have the same issue.
Could you please tell me how you fixed the ciphers in pound?

How to fix "ciphers" by ourselves? I got "unable to connect to server" in self service app too.

Hi!
Jss v. 9.8.2
I am manually installing Self Service Mobile to specifics smart groups. It is the only app I have set so far to update automatically. I noticed that worked, the app is now 9.9 on many devices so far.
Then I had a connection error on a couple devices, and discovered that my configuration got wiped out on the app in the jss. Put that info back in and all is well. I have switched over to devices based app distribution over the last week (spring break) and all is now well. App works better than ever, just need to test apps as a few have gone away from the App Store (blogger) I do not remember dong anything with/to that app, so not sure how the config got wiped out.

Updating the ciphers as per:

[https://jamfnation.jamfsoftware.com/article.html?id=384](link URL)

worked for me too.