1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
Hi Justin,
It sounds like there is a connectivity issue with your first EC2 instance. Here are a few recommended things you can check. Try reconnecting after each troubleshooting step to verify if the fix works.
- Make sure EC2 Security groups allow the right IP addresses and ports of the service you are connecting to
- If you are using an ALB, follow the guide linked below to see if that is the issue
- Attempt to connect to the first EC2 instance via the command line or via the Management Console using EC2 connect to verify connections can be made
- Check if your EC2 is using an elastic IP address, as EC2's without an EIP change their IP after reboot.
- Verify that any route tables/NACLs in your VPC allow the type of traffic you need
If there are no issues with your second EC2, you may try creating an AMI and relaunch another EC2 with that AMI.
Guides:
- https://aws.amazon.com/premiumsupport/knowledge-center/504-error-alb/
- https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html
- https://docs.aws.amazon.com/toolkit-for-visual-studio/latest/user-guide/tkv-create-ami-from-instance.html
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 7 Monaten
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
If you connect to your WordPress instance, is there anything remarkable in the WordPress logs? I'm not exactly sure where the logs would "live," but this would be my best guess where to start: https://docs.bitnami.com/aws-templates/apps/wordpress/troubleshooting/debug-errors-apache/