チャノさん＠C103, 2日目、東ヒ48a on Nostr: Tonight's stream was twice punctuated by attempts at troubleshooting/fixing ...
Tonight's stream was twice punctuated by attempts at troubleshooting/fixing Shadowchat problems, and after the stream was done I went back and tinkered some more, finally fixing the issue. There were several things I learned in the process:
1) The initial problem was something I already knew could (and often does) happen; the remote node monero-wallet-rpc was pointed at stopped working for whatever reason, and thus both monero-wallet-rpc and shadowchat keep spitting connection errors to logs
2) The usual solution is to kill both processes and restart them. However, even though monero-wallet-rpc is instructed to listen on port 28088, it doesn't actually start doing that until the wallet it's load is fully synchronzed with the current blockchain state. This can take a while, anywhere from 5 to 15 minutes, depending.
3) If Shadowchat is started right away, it'll try (and fail) to connect to the wallet RPC on port 28088, continually outputting errors and any attempts to initiate a superchat via web will result in a wallet connection error.
If anybody besides me decides to use Shadowchat, my advice would be to check logs on both the wallet RPC and Shadowchat at least an hour before you need to use it, and see if errors are happening. If they are, restart the wallet RPC and monitor logs to see if it finishes sync and starts listening on its assigned port, then look at Shadowchat logs to make sure it isn't complaining about connection errors. At that point, everything should work as expected.
1) The initial problem was something I already knew could (and often does) happen; the remote node monero-wallet-rpc was pointed at stopped working for whatever reason, and thus both monero-wallet-rpc and shadowchat keep spitting connection errors to logs
2) The usual solution is to kill both processes and restart them. However, even though monero-wallet-rpc is instructed to listen on port 28088, it doesn't actually start doing that until the wallet it's load is fully synchronzed with the current blockchain state. This can take a while, anywhere from 5 to 15 minutes, depending.
3) If Shadowchat is started right away, it'll try (and fail) to connect to the wallet RPC on port 28088, continually outputting errors and any attempts to initiate a superchat via web will result in a wallet connection error.
If anybody besides me decides to use Shadowchat, my advice would be to check logs on both the wallet RPC and Shadowchat at least an hour before you need to use it, and see if errors are happening. If they are, restart the wallet RPC and monitor logs to see if it finishes sync and starts listening on its assigned port, then look at Shadowchat logs to make sure it isn't complaining about connection errors. At that point, everything should work as expected.