- Newest
- Most votes
- Most comments
Hello.
Is the TTL of the DNS record set too long?
If the TTL is long, the IP may be accessed before the DNS is updated.
If it is a TTL problem, it may become accessible after a little time.
It is also possible that there may be some cache left in the router from which you are connecting or in your terminal, so a reboot may be effective.
Have you attempted visiting the instance IP address directly and ensuring it is working? This could let you know if the instance is with your instance or with DNS.
If you visit your IP directly (e.g. 1.2.3.4) and see the same problems, then you know the issue is with your instance itself. If the site loads as expected when visiting the IP then you know the issue is with your DNS records. Once we know that we can attempt to identify and address the issue.
The IP takes me to the Nginx Server.
Welcome to nginx!
If you see this page, the nginx web server is successfully installed and working. Further configuration is required.
For online documentation and support please refer to nginx.org. Commercial support is available at nginx.com.
Thank you for using nginx.
I am using a reverse proxy with .netcore. The service is running on the server.
The IP works with the MySQL server and am able to access the database remotely.
Relevant content
- asked 4 years ago
- asked 7 months ago
- Accepted Answerasked 4 years ago
AWS OFFICIALUpdated a month ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 months ago
I waited for 2 days and it didnt connect. I changed the IP back to the old instance and it connected. The only difference between the 2 snapshot instance and the original instance is that the original is 18.04 and I upgraded the snapshot instance to 20.04. All the services are running on both