1

Hello, I have just been upgraded to 3.2 version of the android app, and when I enter my server information and credentials, I get an Untrusted Certificate error message with the option to view details, cancel, or proceed. If I hit proceed, it just throws me back to the screen where I enter my credentials and server information. We have spiceworks on-premise in a server which has an internal IP on port 9675. This has worked in the past, but the app isn’t working for me now.

How can I solve this?

1 Spice up
2

This may be an issue with Android, not Spiceworks. Look in your security settings on the device and tell it to accept all security certificates. If that fixes it, that’s where the problem was. Then, you just have to decide if you are OK with keeping that setting.

3

Hmm. I am running CM12.1 and can’t seem to find a place where I can tell the phone to accept all certificates. Other ideas? Or, do you know where to look to see this settings?

4

Our devs took a look at this and have figured it out. They will be submitting the fix to the store in the next few days. Not sure what the approval process looks like for Android, but it shouldn’t take too long after that.

5

Great, thanks for the update!

6

Any news on when the fix will be released?

7

Actually, this is interesting. I just modified the settings to use a domain name instead of an IP address, and got it working that way. What I noticed, though, is that what I had in there for the server was https://xxx.xxx.xxx.xxx . First thing I did was add :9675 to the end of it and tapped “save.” Well, it took me back to the screen where I tap on the profile and it said the profile was now called “https”. So I long-tapped the profile, and when it brought up the profile settings the URL was " https://http:9675 "

So then I tried clearing the server name field completely and entering the 3rd level domain name as the URL as in “subdomain.domain.com.” Saved this, and it told me the server was either too old or unavailable. Went back into profile and added :9675 to the end, and it again saved as " http://http:9675" . Something bizarre is happening with the way the app is saving URLs. Finally I cleared the field completely and entered “subdomain.domain.com:9675” and this time it worked!

So, it’s apparent it isn’t working exactly as it should, but it is at least functional.