I noticed this one and I was wondering why the command you were all using wasn't working on my side.
Any idea why it's not working? I'd like to fix it.
I can replicate this issue with the latest 1.8.1 duniter server.
duniter start --keyprompt? This node's current public key is: 8XhY8XhYZyDyUb7hMcy5qsanaHBC11AwPefcCQRBQNA Modify your keypair? Yes? Key's salt [hidden]? Key's password [hidden]Starting duniter_default daemon...duniter_default daemon started. PID: 56759
Then I can see that the process has got closed inmediately.
TO work, I have to use the direct_webstart parameter and nohup or screen sessions in order to let the process running:
screenduniter direct_webstart --keypromptctrl + a + d (to deattach session)