The main thing to bear in mind here is that setup.sh (core of all the installation processes) is not idempotent.
This means that if somehow the script failed in the middle of running, you can't simply run it again.
In case something went wrong with the installation, follow these instructions:
- Try to check the output of the setup.sh script and figure out what the reason for its failure could be. Possible reasons include permissions/missing packages.
- It's always better to reinstall rather than try and run the script from where it stopped.
- Review the section which explains setup.sh, in combination with the logs. This might give you the answer.
- If using AWS/GCE, verify that ports 22, 80, and 443 are reachable (sometimes, even if not in the cloud, corporate users have strict firewall rules, so you might have to check it even if not on AWS/GCE).