Posted on 12-19-2017 07:28 AM
Hey folks.
We have our JSS and our main DP on the same server. We are configuring downloads over HTTPS but have issues with getting it to work.
We can fetch packages just fine when opening a browser from a client and manually entering the URL for the packages on the server. When running jamf policy -verbose from a client we get the following error:
We are not using a self signed cert.
Also a sidenote question; When HTTP/S is enabled, does the clients only fetch packages from HTTP/S? And SMB is only used by Casper Admin to upload packages?
Solved! Go to Solution.
Posted on 12-19-2017 07:48 AM
I'm almost certain you're seeing an SSL cert issue. Does the machine you're testing on have installed and trust the cert that's being used for SSL?
I tend to test with plain HTTP initially when I set up a HTTP/S DP and then add SSL into the mix once everything is working.
Posted on 12-19-2017 07:48 AM
I'm almost certain you're seeing an SSL cert issue. Does the machine you're testing on have installed and trust the cert that's being used for SSL?
I tend to test with plain HTTP initially when I set up a HTTP/S DP and then add SSL into the mix once everything is working.
Posted on 12-19-2017 11:28 AM
I'm facing the same issue lately with 10.1.1 hopefully someone has a solution to this.
Posted on 12-20-2017 04:40 AM
@stephanpeterson We solved it! It was a bit of misconfiguration from our part. Instead of the hostname to our DP we had put the IP address instead. Im not very well-versed into certificates but I guess it cannot validate with the just the IP address. Changing it to the hostname solved it!