LegacyPulsar Posted June 13, 2017 Posted June 13, 2017 Hi all, I've been using Apple Configurator 2 for the last six months or so to deploy blueprints to iPads en-mass and, as many people working with Apple have surely done in the past, thought to myself "gee, I wish I could stop it downloading the OS and app every single time on every single iPad..." So I went and got MacOS Server from the App Store. Brill, I thought. An end to my woes!. So I've listened to the advice of many an article/video and left the settings as they are: I've given the cache a quota, a location and left the permissions/peer permissions on Only Local Subnets. I then tried updating an iPad that required 21 app updates via Apple Configurator 2, hoping to see the Cache Used bar periodically rise. Nothing. Not a sausage. Or even an app. I tried updating some elements on the mac acting as a server through the App store. Nothing. Tried updating an iPad locally through iTunes. Nothing. So i checked Debug.log located in Library/Server/Caching/Logs/ and I get the following messages: Cache manager initialized, cache contains 0 bytes of 420.00GB Retrieving configuration Request for configuration from http://suconfig.apple.com/resource/registration/c1/config.plist succeeded Cleaning cache Cleanup succeeded Registering for notifications Registering for service Request for certificate from https://lcdn-registration.apple.com/resource/cert.cer failed: an SSL error has occured and a secure connection to the server cannot be made. 1 consecutive registration failure(s). Server remains suspended pending successful registration. I've tried looking this up on Google but found nothing of any relevance, so I am throwing the problem out to you Apple experts! I hope someone can help I am running macOS 10.12.5 (Build 16F73) and Server 5.3.1 (Build 16S4128)
Brimstone Posted June 13, 2017 Posted June 13, 2017 So I presume you have a static public I.P. for the caching server..? 1
Arthur Posted June 13, 2017 Posted June 13, 2017 (edited) Is your Mac server going through a proxy that requires authentication? Could it be HTTPS inspection related too? Edited June 13, 2017 by Arthur
LegacyPulsar Posted June 14, 2017 Author Posted June 14, 2017 (edited) Thanks for the replies Brimstone: It wasn't, but now is. Upon switching caching on I now get a completely different error in the debug log, which sort've feels like a victory but not... You can see the details below: Arthur: Our ISP has supplied us with a transparent filtering module (basically it automatically applies the proxy to any device accessing our network at its default value) which is what the Mac was running on. I've now input a specific proxy that I utilise so that very few exclusions apply: the results of this are also in the screenshot above. Edited June 14, 2017 by LegacyPulsar
Brimstone Posted June 14, 2017 Posted June 14, 2017 This server looks like it is still going through your LA's SSL Proxy filter, whilst this may be transparent at your end, Apple's servers can not see and respond... Schools have set up the following with the LA so that they could point devices back to the schools Caching Server; TXT DNS record created by the caching server also needed to be added to the SWGL Core DNS Servers as well as our own. The ACL on the Cisco switch needed to allow the subnet for the proxies. The proxy IP range was added to the caching server, I'm not sure this one was necessary but have added it just to be sure. 1
LegacyPulsar Posted June 19, 2017 Author Posted June 19, 2017 This server looks like it is still going through your LA's SSL Proxy filter, whilst this may be transparent at your end, Apple's servers can not see and respond... Schools have set up the following with the LA so that they could point devices back to the schools Caching Server; TXT DNS record created by the caching server also needed to be added to the SWGL Core DNS Servers as well as our own. The ACL on the Cisco switch needed to allow the subnet for the proxies. The proxy IP range was added to the caching server, I'm not sure this one was necessary but have added it just to be sure. I went through our filtering system and added exceptions for various apple.com addresses with no joy, but I got in touch with the company maintaining the system and it turns out we had various ports that the caching service wanted closed: they're now open and I have the shiny blue 'cache used' bar of success! Many thanks to you both for your help and replies
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now