I created an EC2 instance for Filecloud and I can't access to the VM

Question

Hi Team,

I just created an EC2 instance for Filecloud and for some reason when I try to access to the webpage externally using the External DNS name I'm getting this message "This site can’t provide a secure connection".
When I made a capture on my PC I noticed that the Instance is sending a 400 Bad request message:

*13964	2024-07-01 11:53:48.576939	13.39.79.44	443	10.227.65.32	64100	HTTP	446	HTTP/1.1 400 Bad Request  (text/html)*

So, there's reachability from my PC to the instance.
I followed the article that I found in another question ["Troubleshoot connecting to your Linux instance"](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstancesConnecting.html#TroubleshootingInstancesConnectionTimeout) and everything seems to be fine, there's a default gateway assigned to the subnet and the ACL appears to be fine.

I tried to access externally using SSH too and the instance is not working either.

I've deleted 3 instances and created them again and I always got the same issue.
Does anyone have an idea about what it could be?

Pandurangaswamy · Answer

Hi   Keypo,

Please go through the below steps once i hope it will helps to resolve your issue.

**Troubleshooting Steps**

**Security Group:** Ensure inbound rules allow:

* SSH (Port 22) from your IP
* HTTPS (Port 443) from all (0.0.0.0/0) or your IP

**Network ACLs and Route Tables:**

* Allow necessary ports in Network ACLs.
* Ensure the subnet route table has a route to the internet via an Internet Gateway.

**Instance Configuration:**

* Verify instance has a public IP or Elastic IP.
* Check that Filecloud and web server services are running.

**Check Logs:**

* SSH into the instance.
* Review Filecloud and web server logs for errors.

**Filecloud and SSL/TLS Configuration:**

* Ensure Filecloud and SSL/TLS certificates are correctly configured.

**Firewall and Local Network:**

* Ensure no local or network firewalls block the connection.

**Example Security Group Inbound Rules**

```
| Type| Protocal | Port range| Resource |
| --- | --- | --- | --- |
| SSH | TCP| 22 | Your IP|
| HTTPS | TCP | 443 | 0.0.0.0/0 |
```
**AWS Documentation:**

https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstancesConnecting.html

Parthasaradi · Answer

Hello,

Please try this solution.

The simplest way to troubleshoot the 400 Bad Request error with Filecloud on your EC2 instance is to.

**Check Security Group**

Make sure inbound traffic on port 443 (HTTPS) is allowed from your IP address in the security group rules for your EC2 instance. This is the most common cause for the error

Please look at AWS Document Link you will get more information.

https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstancesConnecting.html

rePost-User-4014483 · Answer

Hi,
A http 400 doesnt sound like a security group / firewall issue - more that something might be wrong with the webserver/https setup.

Can you access the website locally on the server itself via curl/wget - does that work?

Cheers,
Rich

I created an EC2 instance for Filecloud and I can't access to the VM

相關內容