Bitnami上AWS Launchpad部署WordPress栈后无法访问及SSH连接求助

I’ve dealt with this exact headache before when deploying Bitnami WordPress via AWS Launchpad— let’s break down the most likely fixes step by step:

This is the #1 culprit for unreachable AWS instances, since default security groups block all inbound traffic by default.

• Head to your EC2 Console → Select your WordPress instance → Navigate to the Security tab → Click the linked security group.
• Check the Inbound rules:
  • Confirm there’s a rule for SSH (port 22) allowing traffic from either your specific public IP (recommended for security) or 0.0.0.0/0 (only for testing).
  • Ensure rules exist for HTTP (port 80) and HTTPS (port 443) with source 0.0.0.0/0 (or your IP if you’re just testing access).
• Double-check your Network ACLs (under the VPC Console) — they should allow inbound and outbound traffic on ports 22, 80, and 443 (ACLs are stateless, so both directions matter).

Bitnami instances have specific requirements that differ from standard AWS AMIs:

• Use the correct username: Bitnami’s default SSH user is bitnami, not ec2-user or root. Your SSH command should look like this:

  ssh -i "your-key-pair-file.pem" bitnami@your-instance-public-ip
  

• Fix key file permissions: If you get a "Permissions too open" error, run this on your local machine to lock down the key:

  chmod 600 your-key-pair-file.pem
  

• Test reachability: Try telnetting to port 22 to confirm network access:

  telnet your-public-ip 22
  

  If this times out, the issue is definitely network-related (go back to security groups/ACLs).

If you finally get into the instance, confirm the WordPress services are running:

• Run this command to check service status:

  sudo /opt/bitnami/ctlscript.sh status
  

• If Apache/Nginx or MySQL are stopped, start all services with:

  sudo /opt/bitnami/ctlscript.sh start all
  

• Check for startup errors in the web server logs:

  sudo tail -n 20 /opt/bitnami/apache2/logs/error_log
  

• Ensure your instance has a public IP assigned (check EC2 Console → Instance details → Networking). If it’s using only a private IP, assign an Elastic IP to make it accessible from the internet.
• When accessing in the browser, explicitly use http://your-public-ip or https://your-public-ip — Bitnami doesn’t always auto-redirect to HTTPS by default.
• If you get a "connection refused" error after starting services, check if the web server is listening on the correct ports:

  sudo netstat -tulpn | grep LISTEN
  

If none of the above works, pull the system logs from the EC2 Console to spot boot-time issues:

• Go to EC2 Console → Select your instance → Actions → Monitor and troubleshoot → Get system log.
• Look for errors like "SSH daemon failed to start" or "Network initialization failed" — these will point to deeper configuration problems.

If you’re still stuck, share the relevant parts of your system log or a sanitized screenshot of your security group rules, and we can dig deeper.

内容的提问来源于stack exchange，提问作者user3552407