UMS 8.2 Mojave 10.14.5 Port 1900 Unavailable ?!?

For help and support with Mac OS X-specific issues
Forum rules
Please make sure you follow the Problem Reporting Guidelines before posting if you want a reply
Post Reply
VaZdef
Posts: 3
Joined: Thu Jul 11, 2019 5:15 am

UMS 8.2 Mojave 10.14.5 Port 1900 Unavailable ?!?

Post by VaZdef » Thu Jul 11, 2019 5:28 am

I've been trying to figure this out for the past 3 weeks.
UMS 8.2 Mojave 10.14.5 Java 8 Update 211 set to high security (medium is gone now?), UMS says ERROR Unable to bind to 1900

When i run lsof -nP +c 15 | grep LISTEN in the terminal it shows port 1900 NOT being used by anything.

rapportd 431 vaz 3u IPv4 0xd7913c629e0419eb 0t0 TCP *:49159 (LISTEN)
rapportd 431 vaz 4u IPv6 0xd7913c629888f2ab 0t0 TCP *:49159 (LISTEN)
wired 497 vaz 11u IPv4 0xd7913c629f7713eb 0t0 TCP *:4871 (LISTEN)
wired 497 vaz 13u IPv6 0xd7913c629888e16b 0t0 TCP *:4871 (LISTEN)
EyeTV 570 vaz 20u IPv4 0xd7913c62a3cb69eb 0t0 TCP *:50389 (LISTEN)
Transmission 701 vaz 8u IPv4 0xd7913c62ab3706eb 0t0 TCP *:56675 (LISTEN)
Transmission 701 vaz 9u IPv6 0xd7913c629888dbab 0t0 TCP *:56675 (LISTEN)
UMS 1252 vaz 43u IPv4 0xd7913c62baa7e6eb 0t0 TCP *:9001 (LISTEN)
UMS 1252 vaz 198u IPv4 0xd7913c62ba5efd6b 0t0 TCP 192.168.0.3:5001 (LISTEN)

My router shows UPnP Enabled and Zero Config Enabled.Tried port forwarding 1900 to no avail.
OSX Firewall shows UMS is Allowing Incoming Connections.
If i Restart Mac in Safe Mode it works.
Using a PC laptop with UMS on the network works too. Its something specific on the Mac. Please HELP!!!

VaZdef
Posts: 3
Joined: Thu Jul 11, 2019 5:15 am

Re: UMS 8.2 Mojave 10.14.5 Port 1900 Unavailable ?!?

Post by VaZdef » Tue Jul 16, 2019 2:46 am

Some more info my Console shows this every few seconds..Could it be Java ??
DEBUG 2019-07-15 08:43:46.701 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2019-07-15 08:43:46.701 [UPNP-AliveMessageSender] Error sending ALIVE message
java.net.BindException: Address already in use (Bind failed)

Nadahar
Posts: 1402
Joined: Tue Jun 09, 2015 5:57 pm

Re: UMS 8.2 Mojave 10.14.5 Port 1900 Unavailable ?!?

Post by Nadahar » Tue Jul 16, 2019 6:14 am

Those messages means that UMS is trying to announce its presence on the local network, but isn't allowed to do so by macOS.You should disregard the "Address already in use" part, that's an assumption based on the fact that UMS isn't allowed to bind to the socket. Normally, this can only be caused by the socket already being in use. It seems though that aPple in their infinite wisdom has made some new "security" feature that prevents access to network sockets. Unless you find a way to turn off this "security feature", UMS simply won't work, as it needs to use the network.

I suspect that their "long term goal" is to prevent any software that's not in their "app store" from being run. Since you have to pay aPple on a yearly basis to include your software in their "app store", this is a great way for them to capitalize not only on the OS and hardware, but on every piece of software you wish to run as well. This will however mean that there will be no free stuff unless it's full of ads or it collects your data and sells it. I doubt there are many people that want to PAY aPple to be allowed to give away their software for free.

VaZdef
Posts: 3
Joined: Thu Jul 11, 2019 5:15 am

Re: UMS 8.2 Mojave 10.14.5 Port 1900 Unavailable ?!?

Post by VaZdef » Tue Jul 16, 2019 8:46 am

Actually i just figured it out and it has nothing to do with aPple ... but that's a funny theory it made me laugh !! :roll:

I use eyetv and ums so eyeconnect locked onto port 1900 at startup with its eyetvhelper which prevented ums from locking on. The trick was to remove eyetvhelper from startup items, set ums as a login item, reboot, and ums opens at login and locks onto port 1900 before eyetv has a chance.

Thanks Nobody for all your help !! :lol:

Nadahar
Posts: 1402
Joined: Tue Jun 09, 2015 5:57 pm

Re: UMS 8.2 Mojave 10.14.5 Port 1900 Unavailable ?!?

Post by Nadahar » Tue Jul 16, 2019 8:57 am

I understood your first post as if you had already excluded the possibility that the socket was in use. The next explanation then would be some kind of OS level permission to bind that was rejected. I'm glad you enjoyed my theory, but I think you'll see that this IS their long-time goal even if this was unrelated. I also believe that MS has the same goal with Windows and their "marketplace" in Windows 10.

If eyeconnect locks port 1900 its developers are make some serious mistakes though. Port 1900 is supposed to be bound for multicast (it is a "special" port in that it's reserved as the "UPnP port"), which aren't exclusive. Unicast binds are exclusive, but with multicast any number of processes can listen to the same port. As such, the idea that some other software was blocking UMS from accessing it was even more unlikely from my POV.

Post Reply