Answers.Body: <p>At least until the most recent 4.7 releases, CiviCRM needed to contact itself via http to populate the dashboard. Your picture suggests that it's not able to, probably related to how the proxy is setup. If you have a command line interface in environment that the code is executing, see if you can contact yourself using, say curl or wget. Sometimes hardcoding the domain in /etc/hosts is a solution.</p>
  
  <p>Another way to mess up your dashboard is with a slightly broken certificate on a https only site - some will render for you in Chrome, but curl/wget won't like it. But in that case, you'd get a spinning thingy.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-10-25T18:03:07.563Z
Answers.Text: Hardcoding the domain in /etc/hosts and/or upgrading is definitely the correct answer!
Answers.UserDisplayName: Jon G - Megaphone Tech
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-10-26T08:20:18.160Z
Answers.Text: http://civicrm.stackexchange.com/questions/4448/ssl-enabled-civicrm-with-forever-loading-dashlets/4453#4453 and https://civicrm.stackexchange.com/questions/3426/the-dashboard-does-not-render/3430#3430 might be worth a reference if you decide to not go the upgrade route.
Answers.UserDisplayName: Chris Burgess
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-10-25T17:35:10.720Z
Answers.LastActivityDate: 2016-11-01T18:03:11.017Z
Answers.LastEditDate: 2016-11-01T18:03:11.017Z
Answers.UserDisplayName: Alan Dixon
Body: <p>Webfaction hosted servers are behind firewalls/proxies. Unlike standing up apache (i.e., socket:xxxx on localhost), their wordpress installation appears to simply be the wordpress code. Therefore, they appear to application route the WP requests vs. NAT/firewall the TCP.</p>
  
  <p>I would guess the civicrm plugin doesn't pass "HOST:" http headers ...</p>
  
  <p>yes, no, solutions? (see pict)</p>
  
  <p>Note:specific menu items (e.g., Administer-> System Settings -> Option Groups) render fine. (and, that messed up CSS is probably due to the 404 page's css)</p>
  
  <p><a href="https://i.sstatic.net/rG7GB.jpg" rel="nofollow noreferrer"><img src="https://i.sstatic.net/rG7GB.jpg" alt="Wordpress, Civicrm admin page on Webfaction"></a></p>
  
Tags: <dashboard>
Title: Webfaction hosting, behind a proxy - broken dashlet
ThreadText: # Webfaction hosting, behind a proxy - broken dashlet
  
  (Asked by: username_0 on 2016-10-23)
  
  Webfaction hosted servers are behind firewalls/proxies. Unlike standing up apache (i.e., socket:xxxx on localhost), their wordpress installation appears to simply be the wordpress code. Therefore, they appear to application route the WP requests vs. NAT/firewall the TCP.
  
  I would guess the civicrm plugin doesn't pass "HOST:" http headers ...
  
  yes, no, solutions? (see pict)
  
  Note:specific menu items (e.g., Administer-> System Settings -> Option Groups) render fine. (and, that messed up CSS is probably due to the 404 page's css)
  
  [![Wordpress, Civicrm admin page on Webfaction](https://i.sstatic.net/rG7GB.jpg)](https://i.sstatic.net/rG7GB.jpg)
  
  **Tags:** dashboard
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2016-10-25. Score: 3
  
  At least until the most recent 4.7 releases, CiviCRM needed to contact itself via http to populate the dashboard. Your picture suggests that it's not able to, probably related to how the proxy is setup. If you have a command line interface in environment that the code is executing, see if you can contact yourself using, say curl or wget. Sometimes hardcoding the domain in /etc/hosts is a solution.
  
  Another way to mess up your dashboard is with a slightly broken certificate on a https only site - some will render for you in Chrome, but curl/wget won't like it. But in that case, you'd get a spinning thingy.
  
  > **Comments:**
  > **username_2**: Hardcoding the domain in /etc/hosts and/or upgrading is definitely the correct answer!  
  > **username_3**: http://civicrm.stackexchange.com/questions/4448/ssl-enabled-civicrm-with-forever-loading-dashlets/4453#4453 and https://civicrm.stackexchange.com/questions/3426/the-dashboard-does-not-render/3430#3430 might be worth a reference if you decide to not go the upgrade route.  
  
  ---
  
  