-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error Timeout on apply.yml up --build #6
Comments
Similar to this terraform issue above. Have verified that it is not a security group error as ssh incoming traffic is enabled for inbound. Going to have to dig into terraform or some of the partial config details in the plans |
Might be a username issue https://stackoverflow.com/questions/62945878/terraform-timeout-when-connecting-to-ec2-instance |
Hey @sdoan99, thanks for reporting this, I haven't tried deploying in a bit, so I'm not sure exactly what the issue could be. I'll try and see if I can reproduce. My first instinct would indeed be a username or credential issue, since I've had timeouts happen because of that before. Just to verify, you followed the instructions for generating SSH keys prior to building, planning, and applying? Regarding the link you posted, I'm fairly certain the username is correct for the AMI this project uses (had to experiment with that when building the scripts). It's possible something's changed on the AWS side, but I'll need to take a look. Please feel free to post additional details or updates if you figured out what's going on! |
Thanks for putting the docker/terraform and guide together. Its great to have everything packaged into containers and auto created through a few scripts. Kill switch is nice too haha.
Tried to install jellyfin on aws but couldnt get the server past the firewall or appear on the site really.
This is also first time working with docker/tf. Ran into an error here
The docker-compose -f docker-compose.terraform.apply.yml up --build is getting timed out when trying to build aws_instance.jellyfin_server
spits out an i/o timeout then sends an error
The text was updated successfully, but these errors were encountered: