Cannot connect to the server from iPhone app

[ghost]

Issue

"Cannot connect to the server, please check that the server is running"

System

• UDM-Pro
• nano-HD AP
• Three separate networks
  • LAN
  • Guest WiFi
  • IoT WiFi
• MacBook Pro
• iPhone XS Max

Steps to Repro

1. On Mac: Install iperf3 via Homebrew.

2. Start the server with iperf3 -s -D.

3. Run iperf -c my-ip.
   All systems go!

4. With server still running, open the iperf3 app on iPhone

5. Type in my-ip (the same one as the Mac)

ERROR: "Cannot connect to the server, please check that the server is running" error.

Am I testing this correctly, should I be using my wi-fi network IP? The IP that my iPhone shows for WiFI?

Nothing seems to work but, with not very much documentation, there's a chance I'm screwing something up.

Any help is appreciated. Thanks

[pfalstad]

Ok I thought I was having this problem, but in my case I just forgot that I turned the wifi off on my phone. Once I turned it back on, it works fine now.

[ndfred]

The UI is pretty minimal right now, this error matches iPerf's IECONNECT error and they are suggesting we check herror / perror for details:
https://github.com/ndfred/iperf-ios/blob/master/Source/iperf3/iperf_api.h#L368

Maybe I could surface herror / perror to help diagnose these issues. FWIW this error is different from the server being busy. I would use the local IP for my iPerf server to perform the test.

[miguelpruivo]

I'm experiencing this issue as well. The server seems to be running properly on my MacOS machine (Big Sur) with no firewall enabled. The iOS app connected to the same network can't connect.

[ndfred]

I need to get back to publishing app updates, right now I am stuck with App Store certs issues (see #41), but once that is done I should be able to land a few improvements

[jiversen]

Just tried iperf on iPhone for first time.

i have the same problem. The server is running fine and can be contacted by other clients but not this app.

any progress fixing this?

[BlackBird11]

i had the same issue on windows and had to make a new rule for the firewall for this specific port, if that helps anyone. also with the firewall disabled it worked