So far so good today, uploads and replications working normally. Cloud Primary, US-East.
Over the past few days, I've been trying to get my Jamf Cloud Distribution point sync'd with my on-prem primary distribution point again since I've been experiencing a lot of issues. Things have been faster syncing overall, but any new files it's taking 4 to 5 times to upload to the JCDS – doesn't matter the size. One thing I keep noticing is that I get a warning message in the Casper Admin Sync Log that there is a "connection failure: "The operation couldn't be completed ( error 502.)"":
At the end of sync, I got a list of files that didn't upload - which was 6 this time (a lot better than in the past). I decided to run a sync again to see what would happen. It took about 15 seconds to run and I got a message saying "Replications of the drives complete." Huh? I don't know what to believe on this one. This is the first time I actually got a favorable message after syncing and am a little leery on the integrity of what's uploaded to JCDS.
Hi, we have the same issue. I am trying to upload Office 16.38 package to Jamf Pro - Akamai via webapp.
I am receiving the error: Timed out uploading icon.
We are in central Europe.
The change https://status.jamf.com/incidents/ksf6fsfttbfd. was only related to US?
br
Hello @pipo
The changes for last week were specific to the US-based regions. We are in the process of planning the maintenance windows for all other regions and you should expect an email being sent out soon with the details for your region.
I am chasing the same from last few weeks, i have renamed the file etc did lots but there is not fix yet received. Still getting error 504 when replicating DP to JAMF Cloud.
As well as getting error 400 when executing the policy when i tried to upload the package from GUI.
Anecdotal, but we recently migrated to JamfCloud from on-prem. We were having some trouble getting large packages to upload, remembered a Mac vs Windows discussion here and switched to a Windows pc. That worked for a slightly over 1GB package but still had multiple failures on a ~7GB Adobe CC package. Renamed it (taking out underscores, spaces, etc.) and it uploaded. No idea if that was a solution, or it just decided to work that time.
Anyone else having an issue uploading Xcode 12.4 to their JAMF Cloud through the web console? Tried probably 7 times and fails each time. Tried renaming, repackaging. Takes like 2+ hours each try and you don't get notified of the package failure until the end.
Lately I've actually had luck using the Jamf Admin app for large packages. Even though Jamf says not to use it...
@stutz Take a look at pkgChunker. Do NOT try to use the installer, just download and run the script. You might also want to adjust the chunk size used in the script to something smaller Tham 7GB.
