-
All replies
-
Helpful answers
-
Sep 22, 2015 7:37 AM in response to Matthew Hockerby BobHarris,According to this web page it is an iCal service
<TCP and UDP ports used by Apple software products - Apple Support>
-
Sep 22, 2015 7:59 AM in response to Matthew Hockerby Luis Sequeira1,You should probably ask this in the OS X Server forum.
My guess is that you need to change the port where the ical service is located, but I am not familiar with how to do that.
-
Sep 22, 2015 8:21 AM in response to Luis Sequeira1by Matthew Hocker,I can't find the Server forum... does anyone have a link?
-
-
Oct 1, 2015 12:18 AM in response to Matthew Hockerby _metamatt_,★HelpfulIt'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.
-
Feb 8, 2016 8:30 PM in response to _metamatt_by jkuzniar,Nice one @_metamatt_ I just finally updated to Server app v5.0.15 and my UniFi controller wouldn't load. This helped a lot. Thanks.
-
Mar 10, 2016 10:10 AM in response to Matthew Hockerby sherlockfromclassic,For me, turning off Profile Manager did it. I am not using it but was going to do some testing with it. Once I turned that off in Server Manager I was able to launch the UniFi App and open up the web management console.
-
Apr 9, 2016 4:15 AM in response to Matthew Hockerby applentoast,Hi
I found it easier to change the Ubiquiti ports to get the Ubiquiti controller running.
- go to ~/Library/Application Support/UniFi/data
- open system.properties
- ad following two lines
portal.https.port=9843
unifi.https.port=9443
is_default=false
Regards
applentoast
-
May 24, 2016 2:54 PM in response to applentoastby tbw-it,@applentoast,
Thanks for posting this. I've been searching the Ubiquity forums for a solution. Your's worked perfectly. -William
- go to ~/Library/Application Support/UniFi/data
- open system.properties
- ad following two lines
portal.https.port=9843
unifi.https.port=9443
is_default=false
-
May 25, 2016 5:13 PM in response to tbw-itby Marcolepsy,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.
-
May 29, 2016 9:31 AM in response to Marcolepsyby willrun4fun,Do you or someone have config file I could get?
-
Sep 13, 2016 3:01 AM in response to willrun4funby Cowan Pettigrew,Did you still need this? I just solved this issue for my home stack. thanks to Marco