Hi @dvasquez ,

This may be related to a new feature in 9.3.
In the JSS webapp, please go to the Settings Gear >> Computer Management >> Security >> and set Package Validation to Never.

Save, and give it a try again; if we still get the same error, we may want to remove and re-upload the packages.

Please let us know if that helps!

Amanda Wulff
JAMF Software Support

That did help. Thank you! Justin from support helped me as well.

As part of this now I am seeing this error more and more regularly on clients after policy's run and packages install:

Running Recon...
Error running recon: Connection failure: "The host MYJSSSERVER.com is not accessible."
The results of this policy were not logged at the time of execution.

@dvasquez I have been seeing that a lot ever since upgrading to Casper 9.

Thanks @charles.hitch there are many weird things happening. I am thinking of going back to 9.25, maybe.

@amanda.wulff, I'm experiencing a very similar issue outlined at: https://jamfnation.jamfsoftware.com/discussion.html?id=10295

Even with the security setting changed to not require package validation, it still fails when used as a policy. This is a major problem at this point since I am re-enrolling all managed clients after a push certificate account change.

We ran into this issue too...went from 8.73 > 9.31 over the weekend. Thankfully the temporary fix in this thread worked.

We'll open a ticket with JAMF to make sure this is on their radar, in our environment we need to have things as secure as possible, so turning off Package Validation is a bit of a concern.

PS, we did get the Migrate button in Casper Admin after copying over our Distribution Point (file share) from the old 8.73 server to the new 9.31 server. No errors during the migration. Maybe the packages didn't all validate? :)

Don

Got a quick response from JAMF....show "Checksum" column in Casper Admin. Create checksum (right click) for any packages that may not have them. Then re-enable Package Validation (security is always a good thing).

You guys rock! :D

Don

Okay well I am seeing this similar issue but I only saw it after we changed ports that Casper is running on. Not sure if ti is related but it seems odd that we were fine until that point.

@ifbell, what do you mean you changed which port Casper is running on? Are you referring to 8443? Can that traffic be sent over another port? I'm asking because my security team recently approached me on that topic, and I said I would look into it further.

Nice to know Don.. I am not having these issues anymore but this will help in the future.

@Millertime

The port used by the JSS can be changed (most commonly we see it changed from 8443 to 443) by making sure the port you want to use is open and editing the server.xml a bit.

This thread has a little more information on that process.

Amanda Wulff
JAMF Software Support