Long story short: I had to change the .pem certificate so I created a new temporary instance with new certificate, switched the volume to change the certificate with the new one, removed the temporary instance, attached the volume back to the main instance as primary volume. Now I have no issues connecting to the old(main) instance with the new certificate (SSH) but unfortunately the public DNS doesn`t work anymore. The Security Group is exactly the same as before, both 80 and 443 ports are open for incoming (same with port 22). Any idea what might be the issue?
Asked on Amazon Forum aswell but no answer...
答案 0 :(得分：0)
Did you check the public IP of the instance and the A record of the DNS entry against the domain name? Are they same?
As you have created a new instance and presuming that you have not used Elastic IP, the new instance would have gotten a new IP which might not be matching the IP present as the A record against the Domain Name. You can run command
dig <domain name>
and match it against
curl checkip.amazonaws.com
on that instance.
Could you please mention the forum link so that I could have a look at it? Thanks.
答案 1 :(得分：0)
原来，防火墙阻止了所有事情，并提出了问题。它的配置发生了变化，但我不知道为什么。