- Newest
- Most votes
- Most comments
Hello.
I think it's possible that the EC2 specs are low and memory and CPU usage is high.
Installing Coolify on your EC2 instance may have placed a load on it, affecting the operation of the SSH process.
Does the EC2 instance you are using use an instance type that meets the minimum specifications listed in the following document?
https://coolify.io/docs/get-started/installation#_4-minimum-hardware-requirements
CPU: 2 cores
Memory (RAM): 2 GB
Storage: 30 GB of free space
Coolify may function properly on servers with lower specs than those mentioned above, but we recommend slightly higher minimum requirements.
Is your EC2 public?
If so, check the public IP address as it will change if you do not have an elastic IP
Yes I have a public IP address, I see it, but can't connect using it.
Relevant content
asked 2 years ago
My ECE is a free-tier t3.micro instance with 2 vCPUs, 1 GB of memory, and 8 GB of storage. I’m not sure if this is actually the cause, but I did see a Coolify message saying the installation was successful.
You may be able to install it, but that doesn't mean you'll be able to run Coolify. Your specs don't meet the minimum requirements listed in the documentation, so please recreate your EC2 instance with specs that meet the requirements and then try again.
You could stop the instance from the console and change the instance type to see if resources are the concern. Also, you can look at the server console messages from the AWS console to see if you get any output while it is booting.