MCEC Client Host is failing on an IP address about mcec HOT 4 CLOSED

Thanks for the bug report. I'll look into it asap!

from mcec.

I can't reproduce this.

I've tried using both a hostname / IP address for

1. localhost / 127.0.0.1
2. chugach (my local machine name) / 192.168.4.53
3. public DNS name / my home's public IP address
4. core4 / 192.168.4.56 (another local device).

All 8 combinations worked.

I'm going to release a new build with more logging. Would you be willing to try it?

from mcec.

Please try with v2.2.11.3. Hopefully the debug spew I added will help track this down.

from mcec.

I'm not sure how adding Debug info helped... but... 2.2.11.3 fixed it. Many thanks!
Could it have been a local issue on my machine last week? Really odd.

2022-12-12 10:59:38,569 INFO - Client: Starting (delay = False)
2022-12-12 10:59:38,572 DEBUG - SocketClient: Connect - 192.168.x.x:5150
2022-12-12 10:59:38,573 DEBUG - SocketClient: 1 IP v4 addresses found
2022-12-12 10:59:38,573 DEBUG - SocketClient: new IPEndPoint(192.168.x.x, 5150)
2022-12-12 10:59:38,573 DEBUG - ClientSocketNotificationHandler - ServiceStatus.Started
2022-12-12 10:59:38,573 INFO - Client: Connecting to 192.168.x.x:5150
2022-12-12 10:59:38,573 DEBUG - SocketClient: BeginConnect(192.168.x.x, 5150)
2022-12-12 10:59:38,576 DEBUG - SocketClient: In BeginConnect call back: 192.168.x.x:5150
2022-12-12 10:59:38,576 DEBUG - SocketClient: BeginConnect succeeded: 192.168.x.x:5150
2022-12-12 10:59:38,576 DEBUG - SocketClient: Back from EndConnect: 192.168.x.x:5150
2022-12-12 10:59:38,576 DEBUG - ClientSocketNotificationHandler - ServiceStatus.Connected
2022-12-12 10:59:38,576 INFO - Client: Connected to 192.168.x.x:5150

from mcec.