Challenge failed for domain

Make sure your EC2 Security Group allows inbound access on that port.

And, check any other rules you may have setup in your AWS VPN

2 Likes

Supplemental information Ports 80 & 443 shows closed and Port 8443 shows filtered.

$ nmap -Pn -p80,443,8443 ec2.brasens.com
Starting Nmap 7.80 ( https://nmap.org ) at 2024-03-27 17:40 UTC
Nmap scan report for ec2.brasens.com (34.216.32.171)
Host is up (0.019s latency).
rDNS record for 34.216.32.171: ec2-34-216-32-171.us-west-2.compute.amazonaws.com

PORT     STATE    SERVICE
80/tcp   closed   http
443/tcp  closed   https
8443/tcp filtered https-alt

Nmap done: 1 IP address (1 host up) scanned in 1.41 seconds
2 Likes

These are my Inbound Rules, the outbound ones are also like this

Can "filtered" be caused by AWS security settings?

filtered usually means some sort of firewall.

It could be an ACL rule in your VPN for example. But, you would have created it so probably would remember if you did.

Likely something related to your Spring / Tomcat config. Might try their forum. Looks like it started listening on port 8443 but I don't know if you might need to set other things.

I say this because the response to port 443 is an immediation "connection refused" but to port 8443 the nmap says filtered but a connection request just times out. So, probably getting past your EC2 inbound checks and failing after that.

You are now in the area of server and comms config rather than certs. We often help with common config problems but yours is not. Someone here might recognize something but Spring forum probably best at this stage.

4 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.