To use my domain name programmatically doesn't work any more

0

I recently created a new Lightsail MEAN instance and assigned my already existing domain name and my already existing static ip addresss to it, then deleted the old instance. Now, unlike before, if I try to access a service running on my site programmatically (it's a database running on port 9001 which I enabled) with my domain name in the url, this doesn't work any more (it worked with my old instance). It only works when I specifiy the ip address instead. Strange detail: when I ping the service port from my local computer with telnet specifying the domain name it takes quite long until it works because telnet first tries to find my site with another ip address (it seems to me that that was the dynamic ip address of the new instance before I attached my old static address to it).

Moreover, another functionality on the same site that I use via https, is now becoming extremely slow (takes 20 minutes or so) to be executed, it used to take only a few seconds before.

Any idea why?

asked 4 months ago141 views
3 Answers
0

Ensure you have updated your DNS which points to the correct instance and you have no entries in your localhost file

profile picture
EXPERT
answered 4 months ago
0

Would you be able to share the logs of the database and/or web server?

zeus
answered 4 months ago
  • In the specific case of the database when I use the domain name I run into a timeout: there's no log on the db server itself as it is obviously not reached. So it's just (as this is Java) a jdbc timeout message.

    In the case of https, there is also no specific message: actually the functionality works (in this case I use the domain name!), but it works very slowly as I said (the program contacts an update site to look for updates, which it then, if found, imports).

0

From your log above, there are 2 IP addresses which resolve to two different instances.

197.75.59.52.in-addr.arpa domain name pointer ec2-52-59-75-197.eu-central-1.compute.amazonaws.com. 149.19.158.18.in-addr.arpa domain name pointer ec2-18-158-19-149.eu-central-1.compute.amazonaws.com.

Did you setup any firewall? Maybe the cache in your instance? Is any IP hard coded?

zeus
answered 4 months ago
  • Thank you for your answer. There is no firewall. But as explained in my last post, the problem is already solved. It was due to the fact that the original dynamic ip address was still pointing to my site after I reattached the static ip address from the old instance. I didn't know that I had to explicitly delete that dynamic address. Both addresses were attached to my domain, but only the static ip address was valid and that caused the trouble.

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.

Guidelines for Answering Questions