"Site Can't Be Reached" When Opening the AWS Public IP After Launching a Grengin Instance

The Issue

After launching a new Grengin instance from AWS Marketplace, you’re taken through a setup wizard hosted directly on your server to complete the installation. This wizard is accessed using your EC2 instance’s public IP address.
If you open that public IP with https:// — for example:

https://16.113.91.xxx

— the page fails to load, showing “This site can’t be reached” with ERR_CONNECTION_TIMED_OUT.

Why This Happens

This is expected at this stage of setup, not an error. Until the installer wizard is completed, no SSL/TLS certificate exists on the instance yet — so there is nothing listening on port 443 (HTTPS). The setup wizard is only served over plain HTTP.
Once you finish the wizard, Grengin automatically provisions a subdomain with a proper SSL certificate for you (and you also have the option to connect your own domain). From that point on, HTTPS works as expected — but not before.

The Fix

While completing the setup wizard, always access your instance using http://, not https://:

http://16.113.91.xxx

Replace 16.113.91.xxx with your own instance’s public IP address.
Steps:

1. Go to your EC2 instance’s Instance details page and copy the Public IPv4 address.
2. Open a new browser tab.
3. Type http:// followed by that IP address (don’t let the browser auto-upgrade it to https://).
4. Press Enter — the Grengin setup wizard should now load.
5. Complete the wizard. Once finished, you’ll be issued a Grengin subdomain with SSL already configured (or you can point your own domain to it).

Tip

Some browsers auto-force https:// for any address typed without a protocol (via “HTTPS-Only Mode” or similar). If this keeps happening:

• Disable “Always use secure connections” / “HTTPS-Only Mode” for this site, or
• Open the page in an incognito/private window, or
• Try a different browser.
  This is only needed until the setup wizard is complete — after that, use your Grengin subdomain or custom domain, which will always be served over HTTPS.

---

Still stuck after the wizard completes? Drop a comment below with your instance’s security group settings and any error details.