title: 503 error when running WordPress on AWS EC2 ELB SSL
body: <p>I'm just starting with the AWS...</p>
  <p>I have 1 <a href="https://aws.amazon.com/ec2/instance-types/" rel="nofollow noreferrer">EC2 Instance</a>, which is running WordPress (WordPress powered by Bitnami image from the Marketplace - <a href="https://aws.amazon.com/marketplace/pp/B007IP8BKQ" rel="nofollow noreferrer">https://aws.amazon.com/marketplace/pp/B007IP8BKQ</a>).
  Everything works fine, I can access both front and back-end of the WP installation running from standard <code>HTTP</code>.</p>
  <p>The problem starts when I connect the Instance to the ELB and I'm trying to access the site via the <code>HTTPS</code>.</p>
  <p>I've run through the process of setting up the SSL certificate using the ACM and applied the cert to the ELB. I've also got the 443 and 80 port enabled on the security group for the EC2 instance. The port forwarding on the ELB is set up for both 443 and 80 to go to 80 and my WP config file is set up to check the H<code>TTP_X_FORWARDED_PROTO</code> header to stop WP getting into an infinite redirect loop.</p>
  <p>I think this is all working fine, as I can access the site via the HTTPS and browse the pages. However, when I attempt to log in I am redirected to HTTP and to solve this problem I have set WP site URL and WP home URL to HTTPS. This then results in numerous 503 errors (<code>503 Service Unavailable: Back-end server is at capacity</code>). From the AWS Dashboard, I can see the Instance is running just fine.</p>
  <p>I've researched quite a lot to make sure I have everything set up correctly (some threads I've come across - <a href="https://serverfault.com/questions/304621/endless-redirect-loop-with-aws-elb-and-wordpress-site-using-wordpress-https-plug">Link 1</a> <a href="https://forums.aws.amazon.com/thread.jspa?threadID=58801&amp;start=0&amp;tstart=0" rel="nofollow noreferrer">Link 2</a> ) and everything seems fine (but something is obv wrong).</p>
  <p>Any suggestions on how to get the ELB to work?</p>