User reports issue deploying caprover

[gmachtel]

Using play.test.grid.tf

node 130 on testnet

[abom]

As a suggestion we can have a more user friendly error returned from grid client.
@AhmedHanafy725

[AhmedHanafy725]

Changing the error message would be hard as we need to know what is the actual reason, it may the node is not reachable, gridproxy went down, or there is no wireguard port available. If we hide this error with a friendly one would be hard to detect the issue later.

For this one, the node went down when the deployment started.

[gmachtel]

Making the error more user friendly does not necessarily mean that we have to hide essential info. Goal should be to give some info to the user so that he knows what he needs to do: should he retry the deployment, should he do something else ? Should he contact some support office (to be avoided as an answer if we want it to be decentralised). Or do we refer to some error repository/manual where this kind of error is explained in more detail. The error code maybe should be described in some structured way, as a detail on a more user-friendly general explanation.