[help] Telegram: GetWalletInfoErr after changing LND's SSL

[Falci]

I have to update my node's key and I can't get BOS working anymore.

Got this:

Dec 25 12:10:21 potato5 systemd[1]: Started bos.service - bos-telegram.
Dec 25 12:10:24 potato5 bos[353851]: err: failed_to_connect
Dec 25 12:10:24 potato5 bos[353851]: err:
Dec 25 12:10:24 potato5 bos[353851]:   message: 503,GetWalletInfoErr,[object Object]
Dec 25 12:10:24 potato5 bos[353851]:   stack:
Dec 25 12:10:24 potato5 bos[353851]:     - Error: 503,GetWalletInfoErr,[object Object]
Dec 25 12:10:24 potato5 bos[353851]:     -     at /usr/lib/node_modules/balanceofsatoshis/node_modules/async/asyncify.js:105:87
Dec 25 12:10:24 potato5 bos[353851]:     -     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Dec 25 12:10:24 potato5 systemd[1]: bos.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Dec 25 12:10:24 potato5 systemd[1]: bos.service: Failed with result 'exit-code'.
Dec 25 12:10:24 potato5 systemd[1]: bos.service: Consumed 3.881s CPU time.

[alexbosworth]

it can't connect so try running it manually like bos telegram and if that doesn't work try other commands and see what errors you see

there is a telegram group for community support

[Falci]

It does work when connecting via CLI. The issue only happens when running it as a service

[alexbosworth]

OK that likely means something is messed up in the path or permissions as far as allowing the service user to access the TLS cert or macaroon

You could try using saved nodes as a workaround, or use docker