You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Server port 8443 suddenly enabled - how to turn off?

I have been using Mac OS X server for several years with no issues. Recently however, an update enabled a web user interface on port 8443 - a port that I need for my Ubiquiti UniFi administration console, which now refuses to start because of the conflict. The page that appears on this port says "Welcome to OS X Server" and has links to profile manager, wiki, Xcode, and my settings - none of which I've enabled, thus making this page useless to me.


How do I turn this port off or at the very least, change the port? I do not need any of these services.


Thank you!

Mac mini, OS X Yosemite (10.10)

Posted on Sep 22, 2015 6:59 AM

Reply
Question marked as Top-ranking reply

Posted on Apr 9, 2016 4:15 AM

Hi


I found it easier to change the Ubiquiti ports to get the Ubiquiti controller running.


  1. go to ~/Library/Application Support/UniFi/data
  2. open system.properties
  3. ad following two lines

portal.https.port=9843

unifi.https.port=9443

is_default=false


Regards

applentoast

12 replies

Oct 1, 2015 12:18 AM in response to Matthew Hocker

It's not the caldav/carddav services. I just noticed the same problem and I don't have those services enabled.


If you just point your browser at https://localhost:8443 you'll see a web management interface for Server itself. Nothing there is actually useful, but that's another story.


It seems to be coming from here:


downsample:~>sudo lsof -i tcp:8443

COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME

httpd 10449 root 13u IPv6 0x2233e860f31fe631 0t0 TCP *:pcsync-https (LISTEN)

httpd 10472 _www 13u IPv6 0x2233e860f31fe631 0t0 TCP *:pcsync-https (LISTEN)

httpd 10473 _www 13u IPv6 0x2233e860f31fe631 0t0 TCP *:pcsync-https (LISTEN)

httpd 10474 _www 13u IPv6 0x2233e860f31fe631 0t0 TCP *:pcsync-https (LISTEN)

httpd 10476 _www 13u IPv6 0x2233e860f31fe631 0t0 TCP *:pcsync-https (LISTEN)

httpd 10477 _www 13u IPv6 0x2233e860f31fe631 0t0 TCP *:pcsync-https (LISTEN)

httpd 10710 _www 13u IPv6 0x2233e860f31fe631 0t0 TCP *:pcsync-https (LISTEN)

downsample:~>ps ax | grep httpd

10449 ?? Ss 0:00.13 /usr/sbin/httpd -D FOREGROUND -f /Library/Server/Web/Config/Proxy/apache_serviceproxy.conf -E /private/var/log/apache2/service_proxy_error.log

10453 ?? Ss 0:00.16 /usr/sbin/httpd -D FOREGROUND -f /Library/Server/Web/Config/apache2/services/ACSServer.conf -E /var/log/apache2/services/ACSServer_error_log

10471 ?? S 0:00.01 /usr/sbin/httpd -D FOREGROUND -f /Library/Server/Web/Config/apache2/services/ACSServer.conf -E /var/log/apache2/services/ACSServer_error_log

10472 ?? S 0:00.14 /usr/sbin/httpd -D FOREGROUND -f /Library/Server/Web/Config/Proxy/apache_serviceproxy.conf -E /private/var/log/apache2/service_proxy_error.log

10473 ?? S 0:00.15 /usr/sbin/httpd -D FOREGROUND -f /Library/Server/Web/Config/Proxy/apache_serviceproxy.conf -E /private/var/log/apache2/service_proxy_error.log

10474 ?? S 0:00.09 /usr/sbin/httpd -D FOREGROUND -f /Library/Server/Web/Config/Proxy/apache_serviceproxy.conf -E /private/var/log/apache2/service_proxy_error.log

10476 ?? S 0:00.16 /usr/sbin/httpd -D FOREGROUND -f /Library/Server/Web/Config/Proxy/apache_serviceproxy.conf -E /private/var/log/apache2/service_proxy_error.log

10477 ?? S 0:00.06 /usr/sbin/httpd -D FOREGROUND -f /Library/Server/Web/Config/Proxy/apache_serviceproxy.conf -E /private/var/log/apache2/service_proxy_error.log

10710 ?? S 0:00.12 /usr/sbin/httpd -D FOREGROUND -f /Library/Server/Web/Config/Proxy/apache_serviceproxy.conf -E /private/var/log/apache2/service_proxy_error.log

11677 s000 S+ 0:00.00 grep httpd

If you look in /Library/Server/Web/Config/Proxy/apache_serviceproxy.conf you'll see apache httpd configured to listen on a bunch of ports: 80, 443, 8008, 8800, 8443, 8843.

Editing that .conf file, commenting out the "Listen 8443" line, and "sudo killall httpd" seems to keep it off of 8443. I had to do the same thing for 8843 which the unifi controller apparently also wants. After that, and waiting a while (maybe for sockets in CONN_WAIT to close), I was able to start the unifi controller. Hopefully this stays fixed.

May 25, 2016 5:13 PM in response to tbw-it

One caveat with this solution... It only seems to work if you ran the Unifi controller software before upgrading to Server 5.0.15. If you do so afterwards, the system.properties file doesn't seem to get created. You get the error, but can't there's no file to edit.


In this case simply copy a system.properties file over from another installation, and apply the changes.

Server port 8443 suddenly enabled - how to turn off?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.