- Newest
- Most votes
- Most comments
Hello.
Since the name can be resolved using the dig command, there is probably no problem with the DNS settings.
dig conebeamcenter.com
; <<>> DiG 9.16.1-Ubuntu <<>> conebeamcenter.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2951
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;conebeamcenter.com. IN A
;; ANSWER SECTION:
conebeamcenter.com. 60 IN A 52.204.225.76
;; Query time: 0 msec
;; SERVER: 127.0.2.2#53(127.0.2.2)
;; WHEN: Wed Mar 13 13:41:44 JST 2024
;; MSG SIZE rcvd: 63
I can access it with the HTTP status 200 using the curl command, so I think the access problem has been resolved.
curl http://conebeamcenter.com -I
HTTP/1.1 200 OK
Server: nginx/1.18.0 (Ubuntu)
Date: Wed, 13 Mar 2024 04:41:20 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 18661
Connection: keep-alive
X-Frame-Options: DENY
Vary: Cookie
X-Content-Type-Options: nosniff
Referrer-Policy: same-origin
Cross-Origin-Opener-Policy: same-origin
Cf-Team: 1ed7b67d2f000020912b618400000001
It can also be accessed using HTTP using a browser.
If you cannot access it, please try deleting your browser's cache.
Try configuring your Lightsail firewall to allow ICMP packets.
https://docs.aws.amazon.com/lightsail/latest/userguide/understanding-firewall-and-port-mappings-in-amazon-lightsail.html
Thank you so much. The issue is resolved. :-)
Hi, You may want to delete the screenshots from your question since they show a lot of details about your resources and setup.
Hello,
Can you delete the cache in your browser and try to connect again. The website "http://conebeamcenter.com/" is accessible via domain name as well as public IP address.
Relevant content
- Accepted Answerasked 7 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 months ago
ICMP Ping is a supported protocol in Lightsail Firewall. I believe you mean, the user has NOT configured ICMP ping on their instance.