diff --git a/docs/gcp/getting-started-on-gcp.md b/docs/gcp/getting-started-on-gcp.md
index 8b934798..8475a43b 100644
--- a/docs/gcp/getting-started-on-gcp.md
+++ b/docs/gcp/getting-started-on-gcp.md
@@ -70,4 +70,8 @@ You can specify with which [Machine Type](https://cloud.google.com/compute/docs/
 
 ```sh
 darknode up --name my-first-darknode --gcp --gcp-credentials PATH_TO_YOUR_DOWNLOADED_JSON_FILE --gcp-machine-type f1-micro
-```
\ No newline at end of file
+```
+
+### How to fix a faulty installation/deploy or reinstall
+
+You can use the configuration file to fix a registered node that didn't deploy right or doesn't connect. Simply deploy another node without registering, then copy the `config.json` file from the faulty installation to the new node installation both locally and remote. Locally the file will be located on `~/.darknode/darknodes/YourNodeName/config.json` and remotely `/home/darknode/config.json`. Once copied, the node and CLI should automatically connect.