- Newest
- Most votes
- Most comments
Hello.
I checked the DNS settings using the "dig" command, and the CNAME record value was successfully confirmed, so there seems to be no problem with the domain settings themselves.
dig www.franceola.com cname
; <<>> DiG 9.18.18-0ubuntu0.22.04.1-Ubuntu <<>> www.franceola.com cname
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56428
;; flags: qr rd ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available
;; QUESTION SECTION:
;www.franceola.com. IN CNAME
;; ANSWER SECTION:
www.franceola.com. 0 IN CNAME franceola.com.
;; Query time: 130 msec
;; SERVER: 172.29.240.1#53(172.29.240.1) (UDP)
;; WHEN: Mon Aug 26 14:31:16 JST 2024
;; MSG SIZE rcvd: 79
As shown below, it is not possible to directly access "franceola.com", so I think there is a problem with the settings on the web server side.
What settings do you have on your web server?
Also, are the required protocols allowed in the EC2 security group?
In this case, I think it is necessary to allow ports 80 and 443.
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/security-group-rules-reference.html#sg-rules-web-server
curl http://franceola.com
curl: (28) Failed to connect to franceola.com port 80 after 130129 ms: Couldn't connect to server
curl https://franceola.com
curl: (28) Failed to connect to franceola.com port 443 after 131362 ms: Couldn't connect to server
Is EC2's public IP address correct?
I checked the A record with the "dig" command, but please try to confirm that the IP address "50.19.19.246" belongs to the EC2 instance you are using.
dig franceola.com
; <<>> DiG 9.18.18-0ubuntu0.22.04.1-Ubuntu <<>> franceola.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 54801
;; flags: qr rd ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available
;; QUESTION SECTION:
;franceola.com. IN A
;; ANSWER SECTION:
franceola.com. 0 IN A 50.19.19.246
;; Query time: 79 msec
;; SERVER: 172.29.240.1#53(172.29.240.1) (UDP)
;; WHEN: Mon Aug 26 14:38:00 JST 2024
;; MSG SIZE rcvd: 60
dig -x 50.19.19.246
; <<>> DiG 9.18.18-0ubuntu0.22.04.1-Ubuntu <<>> -x 50.19.19.246
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52725
;; flags: qr rd ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available
;; QUESTION SECTION:
;246.19.19.50.in-addr.arpa. IN PTR
;; ANSWER SECTION:
246.19.19.50.in-addr.arpa. 0 IN PTR ec2-50-19-19-246.compute-1.amazonaws.com.
;; Query time: 80 msec
;; SERVER: 172.29.240.1#53(172.29.240.1) (UDP)
;; WHEN: Mon Aug 26 14:40:28 JST 2024
;; MSG SIZE rcvd: 122
Hi Riku,
Thank you so much for your assistance. I have followed your advice, but I am still encountering issues. Here is what I have done:
Web Server Settings:
I have configured an Apache server on an EC2 instance for my site franceola.com. I added the ServerName localhost directive in the httpd.conf file. I opened ports 80 (HTTP) and 443 (HTTPS) in the security group of the EC2 instance. I verified that the public IP address of the instance matches the A record in Route 53. Despite these configurations, the web server does not seem to respond to HTTP and HTTPS requests. The Apache service is running, but I keep getting an error message stating that it cannot reliably determine the server's fully qualified domain name (FQDN).
Security Group Protocols:
The required protocols are allowed in the security group of the EC2 instance. Here are the current security rules: Port 80 (HTTP): Allowed for all IPv4 traffic (0.0.0.0/0). Port 443 (HTTPS): Allowed for all IPv4 traffic (0.0.0.0/0). All traffic rule: Allowed with the source sg-0344ab71cc752227.... However, I still face connection issues.
Verification of EC2 Public IP Address:
The public IP address of the EC2 instance I'm using is 50.19.19.246, which matches the A record configured in Route 53. Yet, the curl tests show that connections to ports 80 and 443 are failing. Could you please advise on what else might be causing these issues?
Thank you again for your help. I really appreciate your support.
I don't think you can access it if "ServerName" is "localhost".
Try creating "ServerName" as "franceola.com".
Relevant content
- asked 2 years ago
- asked 8 months ago
- Accepted Answerasked 8 months ago
- asked 6 months ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a month ago