Frank
Frank
My NodeJS version is 7.8.0, that's the only difference I can see with your configuration. May be you could try to upgrade to a more recent NodeJS version.
If you could try to identify the particular commit that causes the regression that could help fixing it.
I haven't found a proper solution to handle this particular case of failing auto-refresh requests. Do you have any suggestions to do?
Mostly from each dashboard element controller, like here: https://github.com/mably/lncli-web/blob/master/public/js/controllers/lnd/listpeers.js#L35 One solution could be to disable auto-refresh in case of similar repeating errors. Don't know how it could be cleanly implemented....
Yep, lncli-web isn't preloading all peer aliases.
Definitely, thanks a lot 😄
It's probably platform/OS/... specific as I don't have such configuration parameters in my openssl.cnf file.
What version of node.js are you guys running on?
Could some of you test the suggestion described here: https://github.com/lightningnetwork/lnd/issues/795#issuecomment-374903140 You just need to update the corresponding env var defined in this file: https://github.com/mably/lncli-web/blob/master/app/lightning.js#L10
Thanks @tyzbit for letting us know how you solved your SSL problem. It will help others.