This would likely spawn some errors in your apache logs when the virtual hosts that also use 8443 try and load. One would be to comment out one of the lines for the listeners. There are a few things you can do to correct this. The server always had a default site listening on ports 80 and 443, but now Caldav response is using 8443 for a Virtual Host for the CalendarServer that redirects to /webcal on port 443. One of which is the fact that the server listens on some ports you might not mean for it to listen on, by default including 80, 443, 8008, 8800, 8443, and 8843. In /Library/Server/Web/Config/Proxy/apache_nf there are a few new funny things due to proxy services (that whole proxy folder is new btw). Well, that means that the server has probably just totally ganked port 8443 for that funky new proxy thing.
System/Library/CoreServices/Applications/Network\ Utility.app/Contents/Resources/stroke 127.0.0.1 8443 8443Īnd let’s say you get this response (again, with the JSS stopped): Well, let’s say you run stroke and you see this (when the JSS is stopped):
For example, let’s say that you’re trying to start a JSS on port 8443. If you have a 3rd party service that isn’t loading, you may find that a port is already in use. This is of particular interest to people running Tomcat sites (e.g. So here are some issues I’ve seen with Apache in the latest OS X Server.
Notably for Casper administrators, this includes port 8443. One of these is OS X Server usurping some ports that would otherwise potentially be used by other tools. But, there are some funny issues that are popping up. I’m guessing there was an impetus to get it out the door before OS X 10.11 ships, so that caching and software update servers can facilitate quicker adoption and tools like Profile Manager will work on 0-day. It’s the first time I’ve seen an OS X Server version drop before an OS release.
0 kommentar(er)
