1

Hi,

When running Spiceworks Desktop for the first time I enter my credentials and I am then asked to enter our proxy server information, when I do this and hit the Test button I get an error saying HTTPS Failed.

Our environment uses a shared proxy managed by a third party and SSL inspection is enabled (third party cert is in trusted root ca store for both computer and user). If I use wireshark to see what’s happening during the test I see that there is a fatal Alert during the SSL negotiation saying Unknown CA however when trying to access community.spiceworks.com via an internet browser on the same machine everything works fine.

Any help is much appreciated.

Thanks,

Neil.

@Spiceworks

2 Spice ups
2

Hey ictsupport3,

Do you know what version of Spiceworks you downloaded? In 7.30042, and previous 7.3 versions, there were some issues related to SSL. We had a release that dropped yesterday that should help with those issues, though. Can you try downloading that from www.spiceworks.com/download to see if it helps?

3

Jon,

I upgraded to 7.30048 but still have the same problem. I am trying to get the proxy owner to exclude the traffic from SSL Inspection just to see if that makes a difference but any other thoughts?

Thanks, Neil.

4

Hey Neil,

Hmm, not off the top of my head. We could pull some logs from you and take a look at what’s going on. Could you shoot a message over to support@spiceworks.com so we can get those from you?

5

Jon,

Looking through the logs I see this:-

Proxy test error: OpenSSL::SSL::SSLError SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed

A quick google search seems to point towards the cacert.pem file, I guess the cert used for our SSL Inspection needs to be added to this somehow?

I’ll keep looking around but any thoughts?

Thanks, Neil.

6

Jon,

I got another patch today, installed it and all working now.

Thanks again for your response.

Neil.

1 Spice up
7

Hey Neil,

There were a few issues around SSL in previous versions of 7.3. Sounds like that is what you were running into… glad it’s working in the latest version, though!