Skip to content

Can't route domains to instance

0

I'm trying Lightsail for the first time using the free trial option, and I'm struggling with many things (I'm used to the ease of use at Digital Ocean). I've been able to work around most issues, but I just can't figure out why my domain is not routing to my instance.

  1. I created a static IP address for my instance
  2. The domain initially pointed to cloudflare nameservers and I tried simply adding DNS records pointing to the static IP there. This didn't work.
  3. I then created a DNS zone in Lightsail and updated the newly provided nameservers at my domain registrar.
  4. When in the "manage" interface of the static domain, I don't know if I should attach the domain to my resource or the static domain. It seems both choices result in the same config. I tried variations and none of them result in my domain resolving.
  5. I performed a DNS check and the domain does point to the static IP.
  6. When I enter the static IP in a browser the default apache "It works" page loads
  7. When entering my domain in ta browser, it returns:

Hmmm… can't reach this page ***.com took too long to respond Try: Checking the connection Checking the proxy and the firewall ERR_TIMED_OUT

  1. When I create a new DNS record (www and the top level domain record already existed before at CF) test.***.com and enter it in my browser I get the default apache page.

Thanks in advance for any help!

asked 2 years ago218 views
2 Answers
0
Accepted Answer

Hello.

If the "dig" command can resolve the name to Lightsail's static IP address, I expect that Lightsail will be accessible.
For example, are there any settings on the Apache side that are refusing connections?
Also, are there any settings on your PC or network firewall that are blocking connections?

dig example.com

By the way, is it possible for you to share the domain you are actually using?
If you share the domain you are actually using, the users at AWS re:Post can troubleshoot further.

EXPERT
answered 2 years ago
EXPERT
reviewed 2 years ago
0

Thanks very much for the reply. It turned out that for some reason the php.ini file for apache2 was using impossible defaults preventing PHP from serving files. I updated the resource values and that got me past this step into the next problem :)

answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.