Failed to connect the WASM client to the proxy server

[rolznz]

Hi,

LNC seems to no longer be working: "Failed to connect the WASM client to the proxy server"

2024-05-23 17:01:01.049 [DBG] WASM: WASM client ready for connecting
lnc-v0.3.1-alpha.wasm:0x20ddf8 2024-05-23 17:01:01.604 [DBG] MBOX: (client) Dialing...
lnc-v0.3.1-alpha.wasm:0x20ddf8 2024-05-23 17:01:01.612 [DBG] MBOX: (client) New conn, read_stream=XXXX, write_stream=XXXX
lnc-v0.3.1-alpha.wasm:0x20ddf8 2024-05-23 17:01:01.612 [DBG] MBOX: (client) Attempting to create send socket/stream
lnc-v0.3.1-alpha.wasm:0x20ddf8 2024-05-23 17:01:02.572 [DBG] MBOX: (client) Connected to send socket/stream
lnc-v0.3.1-alpha.wasm:0x20ddf8 2024-05-23 17:01:04.973 [DBG] MBOX: (client) Receive mailbox initialized
lnc-v0.3.1-alpha.wasm:0x20ddf8 2024-05-23 17:01:05.275 [DBG] MBOX: (client) Got failure on receive socket/stream, re-trying: {"code":2,"message":"stream not found","details":[]}
lnc-v0.3.1-alpha.wasm:0x20ddf8 2024-05-23 17:01:07.578 [DBG] MBOX: (client) Got failure on send socket/stream, re-trying: failed to write: WebSocket closed: unclean connection close: status = StatusAbnormalClosure and reason = ""
lnc-v0.3.1-alpha.wasm:0x20ddf8 2024-05-23 17:01:08.149 [DBG] MBOX: (client) Receive mailbox initialized
lnc-v0.3.1-alpha.wasm:0x20ddf8 2024-05-23 17:01:08.422 [DBG] MBOX: (client) Got failure on receive socket/stream, re-trying: {"code":2,"message":"stream not found","details":[]}
lnc-v0.3.1-alpha.wasm:0x20ddf8 2024-05-23 17:01:09.580 [DBG] MBOX: (client) Attempting to create send socket/stream
lnc-v0.3.1-alpha.wasm:0x20ddf8 2024-05-23 17:01:10.467 [DBG] MBOX: (client) Connected to send socket/stream
Error: Failed to connect the WASM client to the proxy server
    at @lightninglabs_lnc-web.js?v=31fbb923:3932:229
Error: Failed to connect the WASM client to the proxy server
    at @lightninglabs_lnc-web.js?v=31fbb923:3932:229
connect
lnc-v0.3.1-alpha.wasm:0x20ddf8 2024-05-23 17:01:12.792 [DBG] MBOX: (client) Receive mailbox initialized
lnc-v0.3.1-alpha.wasm:0x20ddf8 2024-05-23 17:01:13.089 [DBG] MBOX: (client) Got failure on receive socket/stream, re-trying: {"code":2,"message":"stream not found","details":[]}
lnc-v0.3.1-alpha.wasm:0x20ddf8 2024-05-23 17:01:16.102 [DBG] MBOX: (client) Receive mailbox initialized
lnc-v0.3.1-alpha.wasm:0x20ddf8 2024-05-23 17:01:16.409 [DBG] MBOX: (client) Got failure on receive socket/stream, re-trying: {"code":2,"message":"stream not found","details":[]}
lnc-v0.3.1-alpha.wasm:0x20ddf8 2024-05-23 17:01:20.262 [DBG] MBOX: (client) Got failure on send socket/stream, re-trying: failed to write: WebSocket closed: unclean connection close: status = StatusAbnormalClosure and reason = ""
lnc-v0.3.1-alpha.wasm:0x20ddf8 2024-05-23 17:01:20.263 [DBG] MBOX: (client) Receive mailbox initialized
lnc-v0.3.1-alpha.wasm:0x20ddf8 2024-05-23 17:01:20.545 [DBG] MBOX: (client) Got failure on receive socket/stream, re-trying: {"code":2,"message":"stream not found","details":[]}

[jamaljsr]

Hello @rolznz, the "stream not found" message indicates that the mailbox associated with the pairing phrase cannot be found on the server.

There are a couple of things to check to gather more info on what could be wrong:

1. When creating the session in litd, check the logs to make sure that it successfully creates the mailbox that will be associated with the pairing phrase and that there are no errors logged. You should see a line that looks like this:

   2024-05-23 14:47:57.244 [INF] SESS: Mailbox RPC server listening on mailbox:90c4881ba1ff2f9e513ba3fa2ec727e02ecf1af070656019ec678f301702fae8c711ec426c40a48420b1440b7acc25be6df71e350d746b9437be6140fac28d44@mailbox.terminal.lightning.today:443
   

2. When connecting in the browser, ensure that you are using the same mailbox server host that litd used to create the mailbox. In the example above, it is mailbox.terminal.lightning.today:443

[rolznz]

Hi @jamaljsr

Thanks for the quick reply.

I tried again and this time it worked. It seems my last pairing phrase was not saved properly because when I opened Lit again I couldn't see it. I'm not sure exactly what happened.

I use the same mailbox server: