Caching Service

Discussion in 'Mac OS X Server, Xserve, and Networking' started by IscariotJ, Dec 7, 2012.

  1. IscariotJ macrumors 6502a

    Jan 13, 2004
    I've just upgraded to Server 2.2, and thought I'd give the Caching Service a whirl, however, it's currently refusing to start saying that it can't be run on a public network. I've checked system.log, and the only thing that stands out is:

    Request for registration from failed:
    HTTP response 400, body "INVALID_LOCAL_ADDRESS"

    I'm a bit confused on what it's after, as all the other services ( DNS, DHCP, file sharing ) work as expected.

    Any ideas?
  2. macuser-1 macrumors newbie

    Jul 22, 2012
    Your server has to be behind a NAT for the Caching service (and only the Caching service) to work. That's because you don't want the server to be able to register itself to serve cached updates to other clients on the public internet -- it's intended for private networks only, and the only way to ensure that is to support NAT (non-public IP address ranges).

    For more information about the service, in, go to Help...Server Help. Then the Help Center window, expand "Update Client software", and click on Cache App Store software.
  3. macfusionuk macrumors newbie

    Dec 10, 2012
    non-public IP address ranges

    I've run into this problem, scoured the help in OS X server and am coming to the conclusion that the test Apple use for a NAT'ed network is to check the server's IP to the range -, -
    , -
    If anyone has any technical info on how the NAT is detected I'd appreciate a reply.
  4. pwbeninate macrumors newbie

    Dec 15, 2012
    What I know:
    The Caching Service registers it's outside IP address with Apple. This IP gets reported back to the client. (you can see this exchange in the logs)

    What I assume:
    If that IP is assigned to a network interface on the server, the registration fails.
  5. IscariotJ thread starter macrumors 6502a

    Jan 13, 2004
    Apologies for resurrecting an old thread, but I've just got around for fixing this, and thought I'd post it here in case it helps anyone else....

    Basically, my problem was due the Mac being multi-homed; I had to configure the Caching Server to listen on one interface:

    sudo serveradmin settings caching:Interface = en1

    Started the server, and now happily caching....

Share This Page