search

mworks / mworks-issues

MWorks issue tracker
0 stars 0 forks source link

Sometimes client won't connect after macOS restart #445

Open cstawarz opened 1 year ago

cstawarz commented 1 year ago

Occasionally, immediately after a macOS restart, MWClient won’t connect to MWServer. The problem persists until the system is restarted again.

I have no idea why this is happening. It seems to have started relatively recently (maybe the past few years). Could it be related to the addition of IPv6 support (mworks/mworks@08cfb13e704546a8e1fd6a6824ecea44f913d136)?

cstawarz commented 1 year ago

This issue has been mentioned on MWorks Support. There might be relevant details there:

https://mworks.discourse.group/t/mworks-sound-issue/888/4

cstawarz commented 1 year ago

This issue has been mentioned on MWorks Support. There might be relevant details there:

https://mworks.discourse.group/t/mwclient-cannot-connect-to-mwserver-localhost/922/6

cstawarz commented 9 months ago

This issue has been mentioned on MWorks Support. There might be relevant details there:

https://mworks.discourse.group/t/mworks-support-for-macos-14/944/2

cstawarz commented 7 months ago

I've confirmed that changing the server address, in MWClient only, from "localhost" to "127.0.0.1" works around the issue.

Does this mean that, when this issue arises, MWClient is resolving "localhost" to the IPv6 link-local address (::1), whereas MWServer is resolving it to the IPv4 version?

cstawarz commented 7 months ago

Does this mean that, when this issue arises, MWClient is resolving "localhost" to the IPv6 link-local address (::1), whereas MWServer is resolving it to the IPv4 version?

Yes, I've confirmed this. Also confirmed that the problem seems to have spontaneously resolved itself, and both client and server now resolve "localhost" to ::1.

cstawarz commented 1 month ago

This issue has been mentioned on MWorks Support. There might be relevant details there:

https://mworks.discourse.group/t/mworks-client-server-connection/1030/7