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

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

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

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