This is well beyond my territory some other people are also reporting installation failures here on meta so maybe there is some issue with the code. It’s better to wait for someone from team to provide better details.

Sorry to hear that you are experiencing issues with this. From our end we can confirm that your Droplet is online, however it does not appear to be listening for web/http connections properly. This is typically a sign that either your web server service is not running properly, is not configured properly or there are firewall rules preventing connectivity issues.

To investigate this issue we would recommend that you first ensure that your web server service (Commonly used services are Apache or Nginx) is running. If the service is not running you will simply want to start it. If you encounter any issues starting the service you will want to use the logs provided during the startup process to investigate why there are issues. If the service is already running then we would recommend ensuring that it is configured to listen over port 80 on a publicly accessible interface. This can be checked by running the following command:

netstat -plnt

If this also is in order then the next thing you will want to check is your firewall to see if there are any rules preventing connectivity.

If this also is in order then the next thing you will want to check is your firewall to see if there are any rules preventing connectivity.

The netstat command verified it was listening, so almost definitely there were firewall rules in the way. “Connection timed out” is an indication something is dropping the connection attempt whereas “Connection refused” usually indicates the attempt makes it through but nothing is listening.

That said, we’re happy you’re able to get a supported install up and running !