File Reception Issue 'Room not ready' on Mac (M2 Pro)

[UlysseMtr]

Hey,

I tried using Croc with my Mac (M2 Pro). Sending works fine, but when my VM or my friend's Mac tries to receive a file I send, the following message appears: Securing channel... 2025/01/13 14:50:58 room not ready.

My friend and I also tested sending a file from his Mac to mine, but the same issue occurred. Interestingly, receiving files on my VM works without any problems. Furthermore, sending and receiving files between my VM and my friend's Mac works perfectly.

Thanks!

[schollz]

what happens with --debug?

[UlysseMtr]

This :

[schollz]

which croc version in both computers?

[UlysseMtr]

it's a modified croc version, but both my vm, friend's mac, and mine are on the same.
'croc version v9.5.6mcm-e8960ed'

[schollz]

you need to upgrade croc

[injust]

I think I'm running into the same problem. I'm transferring from macOS to a Windows system on the same LAN, with both ends running v10.2.1.

[debug] 18:49:32 cli.go:215: debug mode on
[debug] 18:49:32 cli.go:219: public IP address: xxx.xxx.xxx.xxx
connecting...[debug]    18:49:32 croc.go:884: attempt to discover peers
[debug] 18:49:32 croc.go:924: all discoveries: [address: yyy.yyy.yyy.yyy, payload: croc9009]
[debug] 18:49:32 croc.go:926: discovery 0 has payload: address: yyy.yyy.yyy.yyy, payload: croc9009
[debug] 18:49:32 croc.go:931: switching to local
[debug] 18:49:32 tcp.go:462: pinging yyy.yyy.yyy.yyy:9009
[debug] 18:49:32 comm.go:78: dialing to yyy.yyy.yyy.yyy:9009 with timelimit 300ms
[debug] 18:49:32 comm.go:87: connected to 'yyy.yyy.yyy.yyy:9009'
[debug] 18:49:32 comm.go:151: initial read error: read tcp zzz.zzz.zzz.zzz:58782->yyy.yyy.yyy.yyy:9009: wsarecv: An existing connection was forcibly closed by the remote host.
[debug] 18:49:32 tcp.go:475: read tcp zzz.zzz.zzz.zzz:58782->yyy.yyy.yyy.yyy:9009: wsarecv: An existing connection was forcibly closed by the remote host.
[debug] 18:49:32 croc.go:946: could not ping: read tcp zzz.zzz.zzz.zzz:58782->yyy.yyy.yyy.yyy:9009: wsarecv: An existing connection was forcibly closed by the remote host.
[debug] 18:49:32 croc.go:950: discoveries: [address: yyy.yyy.yyy.yyy, payload: croc9009]
[debug] 18:49:32 croc.go:951: establishing connection
[debug] 18:49:32 croc.go:967: got host '168.119.238.198' and port '9009'
[debug] 18:49:32 croc.go:969: trying connection to 168.119.238.198:9009
[debug] 18:49:32 comm.go:78: dialing to 168.119.238.198:9009 with timelimit 5s
[debug] 18:49:33 comm.go:87: connected to '168.119.238.198:9009'
[debug] 18:49:33 tcp.go:523: strong key: e1c6893f6fe703df00663527cbeb8893b2f785f5676737472c1538950e8829d8
[debug] 18:49:33 tcp.go:537: sending password
[debug] 18:49:33 tcp.go:548: waiting for first ok
[debug] 18:49:33 tcp.go:566: sending room; 01cecb4101c2cb4327a68f623b1adb736530963563892d774da1294ad9032f5b
[debug] 18:49:33 tcp.go:577: waiting for room confirmation
[debug] 18:49:33 tcp.go:593: all set
[debug] 18:49:33 croc.go:982: receiver connection established: &{connection:0xc0002120e0}
[debug] 18:49:33 croc.go:983: banner: 9010,9011,9012,9013,9014,9015,9016,9017
[debug] 18:49:33 croc.go:1015: data:
[debug] 18:49:33 croc.go:1104: exchanged header message
securing channel...[debug]      18:49:33 croc.go:1122: ready
[debug] 18:49:33 message.go:61: writing pake message (unencrypted)
[debug] 18:49:34 compress.go:50: error copying data: unexpected EOF
[debug] 18:49:34 croc.go:1506: problem with decoding: unexpected end of JSON input
[debug] 18:49:34 croc.go:1148: data:
[debug] 18:49:34 croc.go:1149: got error processing: problem with decoding: unexpected end of JSON input
[debug] 18:49:34 croc.go:1203: error: problem with decoding: unexpected end of JSON input
room (secure channel) not ready, maybe peer disconnected

I don't think this is a recent regression, either. croc hasn't worked for me for at least a year.