Jari Lehto

Q: Calendar server ports reset to 80, 443 when upgraded to server 5

OS X Server Calendar service should still answer in ports 8008 and 8443, right?

 

Calendar service was running but unreachable after upgrade to server 5, for this reason:

 

bash-3.2# serveradmin settings calendar  (irrelevant stuff left out from the result)

calendar:EnableSSL = yes

calendar:HTTPPort = 80

calendar:SSLPort = 443

 

After fixing this to

 

calendar:HTTPPort = 8008

calendar:SSLPort = 8443

 

Normal operation resumed, for client which were already configured.

I tried to add a CalDAV account to Calendar, and it didn't work with defaults. By manually specifying all parameters it does work.

 

Has Apple changed the way how this should be working? I mean, did I just fix the wrong place, should I look at Apache virtual host configs or something?

Posted on Oct 14, 2015 3:12 AM

Close

Q: Calendar server ports reset to 80, 443 when upgraded to server 5

  • All replies
  • Helpful answers

  • by ~morgen,

    ~morgen ~morgen Oct 16, 2015 10:45 AM in response to Jari Lehto
    Level 1 (140 points)
    Oct 16, 2015 10:45 AM in response to Jari Lehto

    Yes, things have changed in Server 5.  There is a front end "service proxy" (an apache instance that now handles incoming connections on behalf of various services such as Calendar and Contacts) which should be listening on 443 and 8443.  Calendar Server itself no longer listens to any TCP ports; it listens on a named UNIX socket that the service proxy forwards incoming requests to.  You should not change those calendar server settings.  If port 8443 wasn't working, then there is an issue with the service proxy.