ERROR: TypeError: Cannot read property 'kid' of undefined #19
読み込み中…
新しいイシューから参照
説明はありません。
ブランチ "%!s(<nil>)" の削除
ブランチの削除は恒久的です。 実際に削除されるまでの短い期間、ブランチが存在したままになることもありますが、たいていは元に戻すことはできません。 続行しますか？
I have encountered the following error when running the script to get a new certificate:
ERROR: TypeError: Cannot read property 'kid' of undefinedAfter a little bit of debugging it seems the error is raised when indexing into the undefined account object in this line, which might be due to the breaking changes mentioned here.
I was able to overcome my issue by making the following monkey patch to the line
if (options.accountKid || options.account && options.account.kid) {Looking to see if I should submit a pull request or if a maintainer wants to push this update or any advice on the issue is very much appreciated.
Thanks!
Thanks for the report. I'll fix that
You could tell me which plugins you're using and which versions? And what "script"?
For example:
That upcoming breaking change is unrelated to the current code (and won't break the code).
It shouldn't be possible for something to get to this module without an account in the first place... but I'll push that fix momentarily anyway. Again, thank you.
Published as v1.7.5. But please do let me know the conditions that were broke it so I can get that fixed as well.
I am using greenlock@v2.7.6 and le-challenge-dns@v2.3.2
Not a problem at all, thank you for responding and maintaining this repository and let me know if I can provide anything else to help
Hmm... those two versions are a bit out of sync.
You'll need to have
le-challenge-dns@v3.0.2, which should be in the package-lock.json for greenlock@2.7.6. But that's unrelated, I would think.I definitely saw the code where, during account registration, the account object is creating if it doesn't exist. I'm curious as to how that error is happening.
Anyway, do an
npm update; npm installand see if you still get the error.If you have a
package-lock.jsonin your project, maybe remove that first so it doesn't prevent updates (though it shouldn't block an explicitnpm update).I've done an update which included your patch fix and it seems to have solved my error 👍
thanks again for the help!