TM Port In Use Mac

[MrSchmtizSVVSD]

I am running TM on a MacBook Air M2 2022 running Ventura 13.4. Every time I try to create a new tournament, it tells me Port in Use. I have disabled Airplay Receiver and rebooted, but it is still giving me an error. My laptop is a managed device by my school district, so I am limited in what settings I can modify.

Are there any other suggestions to try?

Thank you!

[Connor]

It could be that the port is currently being used by another application.

What TCP/UDP ports does Vex Tournament Manager use?

TM uses these ports: TCP 5000 UDP 5111 You may come across some 5 digit ports. You happened to get 59214-59216. When I did it, I got 52661-62664. Those don’t really matter. They’re not ports. They’re sockets. You need not worry about them. Try forwarding the above two, and see if it works out. But I would recommend allowing the application through windows firewall (I assume you’re using windows firewall) since if an application is allowed through, it doesn’t matter what ports it uses. Wi…

Make sure that you don’t have any instance using ports 80, 5443, and perhaps any other ports.

You can find all running ports via:

sudo lsof -i -P -n | grep LISTEN

My output:

(base) connor@Connors-MBP ~ % sudo lsof -i -P -n | grep LISTEN
launchd       1           root    7u  IPv6 0x297be296c671afbb      0t0    TCP *:22 (LISTEN)
launchd       1           root    8u  IPv4 0x297be296c5e824b3      0t0    TCP *:22 (LISTEN)
launchd       1           root   10u  IPv6 0x297be296c671afbb      0t0    TCP *:22 (LISTEN)
launchd       1           root   11u  IPv4 0x297be296c5e824b3      0t0    TCP *:22 (LISTEN)
launchd       1           root   29u  IPv6 0x297be296c671c7bb      0t0    TCP *:445 (LISTEN)
launchd       1           root   30u  IPv4 0x297be296c5e83ad3      0t0    TCP *:445 (LISTEN)
launchd       1           root   32u  IPv6 0x297be296c671c7bb      0t0    TCP *:445 (LISTEN)
launchd       1           root   33u  IPv4 0x297be296c5e83ad3      0t0    TCP *:445 (LISTEN)
rapportd    631         connor    3u  IPv4 0x297be296c5e53d33      0t0    TCP *:58214 (LISTEN)
rapportd    631         connor    4u  IPv6 0x297be296c674cfbb      0t0    TCP *:58214 (LISTEN)
gateway   23149         connor   21u  IPv6 0x297be296c671cfbb      0t0    TCP 127.0.0.1:6942 (LISTEN)
gateway   23149         connor   26u  IPv6 0x297be296c671e7bb      0t0    TCP 127.0.0.1:63342 (LISTEN)
gateway   23149         connor   49u  IPv6 0x297be296c6718fbb      0t0    TCP 127.0.0.1:5990 (LISTEN)
gateway   23149         connor   55u  IPv6 0x297be296c4405fbb      0t0    TCP 127.0.0.1:58253 (LISTEN)
jetbrains 23693         connor   39u  IPv6 0x297be296c67197bb      0t0    TCP 127.0.0.1:63343 (LISTEN)
jetbrains 23693         connor   49u  IPv6 0x297be296c674efbb      0t0    TCP 127.0.0.1:54630 (LISTEN)
kdc       58595           root    5u  IPv6 0x297be296c674d7bb      0t0    TCP *:88 (LISTEN)
kdc       58595           root    7u  IPv4 0x297be296c49eafc3      0t0    TCP *:88 (LISTEN)
ControlCe 95892         connor    5u  IPv4 0x297be296c5e790f3      0t0    TCP *:7000 (LISTEN)
ControlCe 95892         connor    6u  IPv6 0x297be296c671f7bb      0t0    TCP *:7000 (LISTEN)
ControlCe 95892         connor    7u  IPv4 0x297be296c5e7c843      0t0    TCP *:5000 (LISTEN)
ControlCe 95892         connor    8u  IPv6 0x297be296c67207bb      0t0    TCP *:5000 (LISTEN)
Discord   96369         connor   55u  IPv4 0x297be296c4bc2fc3      0t0    TCP 127.0.0.1:6463 (LISTEN)

Source

You can check which process is using a port by doing:

sudo lsof -i :80

If there’s nothing using that port, it won’t show anything. If there is, it would show what application would be using it. For instance, if I want to see what is using port 22, I can do:

sudo lsof -i :22

and my output would be

(base) connor@Connors-MBP ~ % sudo lsof -i :22
COMMAND   PID   USER   FD   TYPE             DEVICE SIZE/OFF NODE NAME
launchd     1   root    7u  IPv6 0x297be296c671afbb      0t0  TCP *:ssh (LISTEN)
launchd     1   root    8u  IPv4 0x297be296c5e824b3      0t0  TCP *:ssh (LISTEN)
launchd     1   root   10u  IPv6 0x297be296c671afbb      0t0  TCP *:ssh (LISTEN)
launchd     1   root   11u  IPv4 0x297be296c5e824b3      0t0  TCP *:ssh (LISTEN)
gateway 23149 connor   53u  IPv6 0x297be296c4404fbb      0t0  TCP connors-mbp.grandenetworks.net:58252->power-server-ethernet.grandenetworks.net:ssh (ESTABLISHED)

Source

Since I can see ssh is using PID 1, I can run the command sudo kill <pid>:

sudo kill 1

Source

You should be running these commands to see if ports 80 and 5443 are being used

sudo lsof -i :80

sudo lsof -i :5443

sudo kill <pid>

[MrSchmtizSVVSD]

@Connor

sudo lsof -i :5443

Thank you! When I checked on both ports (80 and 5443) it displayed nothing, so I am stumped as to what is causing the issue. I emailed the developer, but have not received a response.

Open to any other suggestions

[kmmohn]

@MrSchmtizSVVSD

Open to any other suggestions

Not the answer you’re looking for now…but perhaps something to consider for the future if you host lots of events:

We use a stand-alone T/M workstation packed into a roll-around ATA Case, part of our “event trailer” setup. All the equipment, including a dedicated windows laptop (windows seem to play nicer with T/M software than Mac), is included in the case or attached to the field monitors, and everything stays connected up, other than plugging in a few network cables. More details here if interested: event trailer contents.xlsx - Google Sheets