The error while sending a deployment manifest is Error: socket hangup
User had to regenerate a new client certificate to get around this error.
The expired client certificate error on send-manifest should be more friendly/informational.
This error is likely coming from the provider itself, probably the client should just check its own certificate expiration and probably its presence on the chain (I guess the latter is already done) before letting send-manifest.
At the same time, provider should probably not just hangup the connection but instead give more verbose message giving a user more clue what could be wrong.
The error while sending a deployment manifest is![image](https://user-images.githubusercontent.com/107317698/212466514-f86bab52-98cb-47cb-b69d-467824dbaf06.png)
Error: socket hangup
User had to regenerate a new client certificate to get around this error.
The expired client certificate error on
send-manifest
should be more friendly/informational. This error is likely coming from the provider itself, probably the client should just check its own certificate expiration and probably its presence on the chain (I guess the latter is already done) before lettingsend-manifest
. At the same time, provider should probably not just hangup the connection but instead give more verbose message giving a user more clue what could be wrong.Reported by
OurLink | ValidatorNode#1503
user: https://discord.com/channels/747885925232672829/771909909335506955/1063486380694573076 https://discord.com/channels/747885925232672829/771909909335506955/1063529016474226698