By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

Domain suspended due to verification issue, still inactive after completing verification

0

Hello everyone, I'm currently facing an issue with my domain and I would appreciate any help or guidance you can provide. Here's a summary of my situation:

  1. I purchased a domain from "namecheap.com" and tried to connect it with the Elastic IP of my AWS EC2 instance.
  2. However, I failed to complete the domain verification process on time, resulting in the suspension of my domain.
  3. I have now completed the verification process, they said it would take 24 to 72 hours for restoration, so waited, but the domain is still not active.
  4. Namecheap said it was no issues on their end, asking me to contact the IP address provider.
  5. I reached out to AWS support, but they informed me that since the domain is neither hosted nor registered with AWS, they cannot assist with this issue without additional premium service, which is very unfair and frustrating.

I'm not sure what steps I should take next to resolve this problem. I would greatly appreciate any suggestions or advice from the community.

Additional information:

  • My EC2 instance is running on AWS Linux 2023
  • I am using Apache as the web server on the EC2 instance

Thank you in advance for your help! Best regards, Neal

Topics
Compute
Tags
Amazon EC2Amazon Linux
Language
English
Neal
asked 13 days ago91 views
2 Answers
1

I presume you can still hit the elastic IP address of your EC2 instance in a browser, e.g. http://12.34.56.78/ ?

If this all works, on the namecheap side you need to create an A-record whose value is the IP address of the EC2.

If you want to use SSL/TLS and connect over HTTPS, which I presume you will, you'll need to get a CA-signed certificate and configure that within Apache. Assuming you're just using EC2 (and not putting CloudFront or a load balancer in front of it) the best option might be Let's Encrypt https://docs.aws.amazon.com/linux/al2023/ug/SSL-on-amazon-linux-2023.html

profile picture
EXPERT
Steve_M
answered 13 days ago
profile picture
EXPERT
Osvaldo Marte
reviewed 13 days ago
profile picture
EXPERT
Riku_Kobayashi
reviewed 13 days ago
  • Neal
    13 days ago

    Thank you for your response and suggestions.

    To clarify my current situation:

    1. I am unable to connect to my EC2 instance using the Elastic IP. Directly accessing the IP in a web browser does not work.
    2. I have already configured the SSL/TLS certificate correctly about a week ago, so that should not be the issue.
    3. I am currently unable to connect to the instance via SSH or any other terminal to investigate the situation further. The instance seems to be inaccessible. Given these points, it appears that there might be a problem with the instance itself, possibly at the network or operating system level. As I am unable to access the instance directly, it is difficult for me to identify and resolve the issue on my own.

    I would greatly appreciate any further insights or suggestions you might have. If the problem persists, I think the best course of action would be to contact AWS support for professional assistance. I can provide them with details of the current situation and the steps I have tried so far, and grant temporary access to the instance for troubleshooting purposes.

    Thank you again for your help !!

  • Steve_M EXPERT
    13 days ago

    The EC2 availability issue needs to be resolved first before you can progress the rest. You mention SSH won't work, have you tried EC2 Instance Connect or Systems Manager and do you get any more joy there?

    If the instance is definitely unreachable, it looks like you're going to have to restart it and hopefully it comes up cleanly. As you've associated an Elastic IP it should be on the same IP address.

    Setting up CloudWatch agent to collect more detailed system logs https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Install-CloudWatch-Agent.html may help with root cause analysis should this happen again future.

    You mention giving AWS Support access to your instance, that may be an option for you depending on the support plan you're on https://aws.amazon.com/premiumsupport/plans/

    You may not actually be able to hand control to AWS, but you could get an engineer to be on a screen-share with you. Talk to your account manager (or TAM if you have one).

0

Thank you for many suggestions, Steve, they were very insightful! Now, my domain is suddenly working well, it needed more hours, I guess :)

Best, Neal

Neal
answered 13 days 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.

Guidelines for Answering Questions

Relevant content