tyzbit

I made a [helm chart](https://github.com/tyzbit/helm-charts/tree/main/charts/neko) for neko that I use personally. Feel free to use or copy any or all of it. In its current state, it parses the env...

This is supported in `v14-dev` of discord.js https://github.com/discordjs/discord.js/issues/7998 and there is a PR backporting to `v13`: https://github.com/discordjs/discord.js/pull/7999

This is still not resolved. All that's needed is to bump discord.js to at least 13.8.0.

This is not resolved. I just checked version `2.0.0` and it appears it was built with `13.8.0`: https://github.com/eritislami/evobot/blob/9ae5898c2a906011a4062ae944ea169ee0bc7689/package-lock.json#L1527

Did you re-generate your certificates for LND as outlined [here](https://github.com/mably/lncli-web#generate-lnd-certificates-compatible-with-nodejs-grpc)?

I think more generally the app/underlying library should be adapted to work with the certs that lnd generates, but that's definitely not a trivial task. I'd recommend trying to re-generate...

This is the cert I generated that worked, I added `localhost` to the CN ```Certificate: Data: Version: 3 (0x2) Serial Number: 13168852819585109774 (0xb6c129de2ac58f0e) Signature Algorithm: ecdsa-with-SHA256 Issuer: CN=localhost, O=lnd Validity...

@ubenmackin if that previous command still doesn't work for you, what I did was also added this to the bottom of my `/etc/ssl/openssl.cnf` file: ``` [ alt_names ] IP.1 =...

Before we close, I think we should leave open so the documentation can be updated, either to provide this fix as an alternate if the main cert generation doesn't work....

If anyone wouldn't mind re-generating their certs but using this as the middle command instead and confirming it works? if so I'll have a PR open with documentation changes shortly...