-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
On v1.1.4,problem occurs with the node built with PROMPT_MAIN #378
Comments
The custompreset used in this validation is: `privateKeySecurityMode: PROMPT_MAIN #main address = TAA6DP62XPOGLJ7EPOQZOSEBA3CH2QSOXMF4DVOZ` Until v1.1.3, the above problems have not occurred. |
@fboucquez I investigated the issue. I was able to fix it by copy same method Not sure what is cause but would be good to check other prompts with validation too. |
Thanks @dusanjp for reporting this issue. @cryptoBeliever, thanks for the suggestion! It's one of those ugly circular dependencies that are hard to detect, related to how imports work, if the files import more than it should. Could you have a look at pr #379 ? |
Hello, @fboucquez I missed your comment. I've checked, and I'm able to:
with strategy PROMPT_MAIN 👍 👍 |
When with bootstrap v1.1.4
renewCertificates does not work properly on nodes built using "privateKeySecurityMode: PROMPT_MAIN"
Also, if "privateKeySecurityMode: PROMPT_MAIN" is used and built new node with config / start is executed, an error will be issued and the process will end.
The text was updated successfully, but these errors were encountered: