Answers.Body: <p>You should look at log the load balancer. the 503 might be generated there (ie. the LB can't reach the backend) or it might be that the LB can reach the real servers hosting civi, but they can't process the request</p>
  
  <p>Assuming you trust amazon (a big assumption), you might want to say that the https LB can talk to an unsecure civi server (via http).</p>
  
  <p>Otherwise if you want to be more secure and don't trust amazon, you might need to configure your civicrm server so they handle https too.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-11-04T01:05:55.393Z
Answers.LastActivityDate: 2017-11-04T01:05:55.393Z
Answers.UserDisplayName: Xavier
Answers.Body: <p>It's hard to say without knowing more about your configuration - but the first thing to check is that your BASE_URL setting in <code>civicrm.settings.php</code> is set to HTTPS.</p>
  
  <p>Besides that, I'd check the web server logs (Apache/nginx/etc.) on the CiviCRM host.  It's pretty common to get a 503 from a reverse proxy when it can't connect to the backend server.  Troubleshooting that is out of scope for this Stack Exchange, but it will tell you whether this problem is CiviCRM-specific or not.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-11-03T18:50:09.440Z
Answers.LastActivityDate: 2017-11-03T18:50:09.440Z
Answers.UserDisplayName: Jon G - Megaphone Tech
Body: <p>I recently installed Civicrm on AWS. App works great! However, when I creat a load balancer with a SSL certificate and point the Domain towards the LB, I get a 503 page. If I don't use SSL, everything works fine. </p>
  
  <p>What am I missing? </p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-11-13T14:14:00.567Z
Comments.Text: I don't think you are going to find the answer you want on this stack. I would suggest posting to https://superuser.com/ or https://serverfault.com/
Comments.UserDisplayName: Sleewok
Tags: <urls>
Title: URL issue with AWS load balancer and SSL certificate
ThreadText: # URL issue with AWS load balancer and SSL certificate
  
  (Asked by: username_0 on 2017-11-03)
  
  I recently installed Civicrm on AWS. App works great! However, when I creat a load balancer with a SSL certificate and point the Domain towards the LB, I get a 503 page. If I don't use SSL, everything works fine.
  
  What am I missing?
  
  **Tags:** urls
  
  > **Comments:**
  > **username_1**: I don't think you are going to find the answer you want on this stack. I would suggest posting to https://superuser.com/ or https://serverfault.com/  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_2 on 2017-11-04. Score: 1
  
  You should look at log the load balancer. the 503 might be generated there (ie. the LB can't reach the backend) or it might be that the LB can reach the real servers hosting civi, but they can't process the request
  
  Assuming you trust amazon (a big assumption), you might want to say that the https LB can talk to an unsecure civi server (via http).
  
  Otherwise if you want to be more secure and don't trust amazon, you might need to configure your civicrm server so they handle https too.
  
  
  ---
  
  ### Answer by username_3 on 2017-11-03. Score: 0
  
  It's hard to say without knowing more about your configuration - but the first thing to check is that your BASE\_URL setting in `civicrm.settings.php` is set to HTTPS.
  
  Besides that, I'd check the web server logs (Apache/nginx/etc.) on the CiviCRM host. It's pretty common to get a 503 from a reverse proxy when it can't connect to the backend server. Troubleshooting that is out of scope for this Stack Exchange, but it will tell you whether this problem is CiviCRM-specific or not.
  
  
  ---
  
  