How to deploy an LNC proxy server?

[youngzhenhao]

When I use https://terminal.lightning.engineering/#/connect/pair to connect my node, it often fails to connect successfully. I am using mailbox.terminal.lightning.today:443 and a newly generated pairing_secret_mnemonic.

Failed to connect
Session Not Found. Failed to connect the WASM client to the proxy server. Try reloading the page or obtaining a new pairing phrase.

I suspect it might be a network issue causing frequent failures to connect to the proxy server.
I would like to know how to deploy an LNC proxy server?

[guggero]

You can deploy an instance of aperture and turn on the hashmail functionality here: https://github.com/lightninglabs/aperture/blob/master/sample-conf.yaml#L256

Another option would be to debug the connection issue. If you open the browser's console (usually with the F12 key), you should see more debug output which you can post here.
Or use the debug page described here to debug the connection: https://github.com/lightninglabs/lightning-node-connect/tree/master/example

[yl7996]

Hello! The lightninglabs/lnc web package seems to only support one node link now; May I ask if it is possible to store multiple node link information in the local storage of a website, and achieve node switching and linking by matching the data in the local storage with the password? If the function I mentioned is not supported, may I ask if there is any way to achieve it? Please let me know

[guggero]

That might be a question better suited for the https://github.com/lightninglabs/lnc-web/ repository. I only wrote the Golang part, so I'm not really familiar with the web/NodeJS wrapper.

[jamaljsr]

I've replied to the lnc-web issue you created. lightninglabs/lnc-web#118

Please feel free to continue the conversation on multi-node support there.