Well, the description of this bug is not generally reproducible, so whatever is causing it, it's not as simple as using a high port with a server name. I teste

Well, the description of this bug is not generally reproducible, so whatever is causing it, it's not as simple as using a high port with a server name. I tested this specifically on a number of servers that I run with port numbers > 10000, using /usr/bin/ssh on macOS 10.15.4, with and without IP addresses. Nothing broke for me.