Answers.Body: <p>This can also happen if you have an authorised CiviCRM user who does not have a contact record i.e. you haven't sync'd users to contacts. I've only seen this where Drupal was the CMS, but it was 100% reproducible.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-06-23T19:32:56.690Z
Answers.LastActivityDate: 2015-06-23T19:32:56.690Z
Answers.UserDisplayName: Andy Clark
Answers.Body: <p>Just FYI, I had a problem where my dashlets would not load after upgrading from Apache 2.2 to 2.4. We have https with a certificate from Comodo and the problem was that our security certificate was no longer installed correctly after the upgrade, somehow causing Civi not to be able to load the dashboard.</p>
  
  <p>Browsers were still recognizing the certificate, so at first I didn't know there was a problem with the certificate. I needed to move the chain/bundle certificates over to the main SSLCertificateFile file (chain file certificates were deprecated in Apache 2.4). As soon as I fixed the certificate and reloaded Apache, back came the dashboard!</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-11-12T23:22:24.777Z
Answers.LastActivityDate: 2015-11-12T23:22:24.777Z
Answers.UserDisplayName: desierto
Answers.Body: <p>I faced this issue and had to reinstall (not duplicate) the wordpress site using the following procedure:
  1. exported content using wordpress export
  2. copied theme folder and uploads
  3. clean install of wordpress
  4. install civicrm 
  5. enabled theme
  6. import of content</p>
  
  <p>This was not due to active plugins.  Something must of become corrupted in WordPress.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-07-01T01:28:57.030Z
Answers.LastActivityDate: 2015-07-01T01:28:57.030Z
Answers.UserDisplayName: Sonicthoughts
Answers.Body: <p>A few things may cause issues like this.</p>
  
  <h2>Webserver cannot make HTTP(s) requests to itself</h2>
  
  <p>If CiviCRM / PHP cannot make a request to the CiviCRM site itself, it will be unable to retrieve the dashboard data. This can happen for multiple reasons:</p>
  
  <ul>
  <li>Webserver is behind a proxy and proxy does not permit requests from internal network</li>
  <li>Webserver has DNS which won't deliver request to the webserver</li>
  <li>Webserver is not permitted to make HTTP requests</li>
  <li>Webserver fails SSL negotiation (PHP5.6 requires a <a href="http://php.net/manual/en/migration56.openssl.php" rel="nofollow">valid certificate chain</a> installed, see note below)</li>
  </ul>
  
  <h2>Misconfigured base URL / access URL</h2>
  
  <p>CiviCRM requires a single configured canonical base URL, and it <em>might</em> be that if this doesn't match the URL you're using then CiviCRM won't handle the dashboard requests correctly. Check that the value defined for <code>CIVICRM_UF_BASEURL</code> in your <code>civicrm.settings.php</code> corresponds to the URL you're using - including both schema (<code>http://</code> or <code>https://</code>) and hostname (<code>example.org</code> or <code>www.example.org</code>).</p>
  
  <p>Because this can cause various issues, I recommend setting up an automatic redirect to prevent visitors viewing the site via the "wrong" URL (which will appear to work fine, except when it doesn't). See your webserver's documentation for how to do this - I think both Drupal and WordPress <code>.htaccess</code> files contain example rewrite snippets?</p>
  
  <h2>PHP5.6 and SSL sites</h2>
  
  <p>A few reports are surfacing of the <a href="http://php.net/manual/en/migration56.openssl.php" rel="nofollow">changed default in PHP v5.6</a> affecting sites ability to connect to themselves (and to CiviCRM.org). In addition to having your SSL certificate correctly installed, PHP requires a correctly installed certificate chain to connect to SSL sites (including the local site). If your CA chain is outdated on the webserver, this may lead to failed dashboard and other issues when communicating with remote sites using SSL (payment processors, CiviCRM.org, and local requests such as dashboard widgets and API over HTTP).</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-04-12T08:47:48.263Z
Answers.Text: how can this be resolved if the dashboard doesn't load only to some users? All the Drupal users have contact records in CiviCRM
Answers.UserDisplayName: Kboy
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-04-12T08:49:48.737Z
Answers.Text: At a guess @Kboy that might affect specific users if their permissions granted them access to a dashboard which took overlong to render. Once I was confident the issue affected users differently, I'd continue debugging by inspecting your webserver logs and seeing which dashboard reports are rendered for the affected and unaffected users.
Answers.UserDisplayName: Chris Burgess
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-04-13T12:57:30.107Z
Answers.Text: thanks @ chris, i'm getting this error from certain users: $Fatal Error Details = Array
  (
      [callback] => Array
          (
              [0] => CRM_Core_Error
              [1] => handle
          )
  
      [code] => 0
      [message] =>
      [mode] => 16
      [debug_info] =>
      [type] => PEAR_Error
      [user_info] =>
      [to_string] => [pear_error: message="" code=0 mode=callback callback=CRM_Core_Error::handle prefix="" info=""]
Answers.UserDisplayName: Kboy
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-04-13T19:45:46.810Z
Answers.Text: Recommend answering a separate question with your debug info front and centre @Kboy, maybe mention this question and what's different about your situation so it's obviously not a dupe. Easier for people to help if it's not just in a comment on another Q.
Answers.UserDisplayName: Chris Burgess
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-04-13T19:46:54.707Z
Answers.Text: That error message isn't so helpful ... I think you'll need some help teasing out the source of the problem.
Answers.UserDisplayName: Chris Burgess
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-10-04T09:46:35.487Z
Answers.Text: @ChrisBurgess nice answer :)
Answers.UserDisplayName: michaelmcandrew
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-06-22T01:44:18.397Z
Answers.Text: See also [Dashlet refresh can crash server](https://issues.civicrm.org/jira/browse/CRM-16035) but I don't think that's your problem.
Answers.UserDisplayName: Chris Burgess
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-06-27T11:11:13.830Z
Answers.Text: Thanks, the problem was that the civicrm wordpress install is behind a varnish proxy and the local DNS response to the domain was incorrect.
Answers.UserDisplayName: FGiorlando
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-06-22T01:43:08.380Z
Answers.LastActivityDate: 2016-11-01T00:01:15.837Z
Answers.LastEditDate: 2016-11-01T00:01:15.837Z
Answers.UserDisplayName: Chris Burgess
Body: <p>The dashboard when I log in to CiviCRM does not render, it just continues to say "loading".
  I have tried:</p>
  
  <ul>
  <li>refreshing dashboard</li>
  <li>reconfiguring dashboard</li>
  <li>going to another page and coming back to dashboard.</li>
  </ul>
  
  <p>I can't see any obvious errors in the javascript console in Firefox (firebug) or Chromium.  There are no errors in the apache logs either.</p>
  
  <p><img src="https://i.sstatic.net/nzpVo.png" alt="enter image description here">
   CiviCRM 4.6.4, Wordpress 4.2.1, Apache 2.4, PHP 5.6.9-1, Mariadb 10.0, Debian Wheezy/Sid hybrid</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2018-04-24T22:11:06.323Z
Comments.Text: **Note:** As of CiviCRM 4.7.11 and higher, these answers no longer apply. A permanent improvement was made to eliminate the problem that the answers below refer to.
Comments.UserDisplayName: Jon G - Megaphone Tech
Tags: <dashboard>
Title: The dashboard does not render
ThreadText: # The dashboard does not render
  
  (Asked by: username_0 on 2015-06-21)
  
  The dashboard when I log in to CiviCRM does not render, it just continues to say "loading".
  I have tried:
  
  * refreshing dashboard
  * reconfiguring dashboard
  * going to another page and coming back to dashboard.
  
  I can't see any obvious errors in the javascript console in Firefox (firebug) or Chromium. There are no errors in the apache logs either.
  
  ![enter image description here](https://i.sstatic.net/nzpVo.png)
  CiviCRM 4.6.4, Wordpress 4.2.1, Apache 2.4, PHP 5.6.9-1, Mariadb 10.0, Debian Wheezy/Sid hybrid
  
  **Tags:** dashboard
  
  > **Comments:**
  > **username_1**: **Note:** As of CiviCRM 4.7.11 and higher, these answers no longer apply. A permanent improvement was made to eliminate the problem that the answers below refer to.  
  
  ---
  
  ## 4 answers
  
  ### Answer by username_5 on 2015-06-22. Score: 6 | Accepted answer
  
  A few things may cause issues like this.
  
  ## Webserver cannot make HTTP(s) requests to itself
  
  If CiviCRM / PHP cannot make a request to the CiviCRM site itself, it will be unable to retrieve the dashboard data. This can happen for multiple reasons:
  
  * Webserver is behind a proxy and proxy does not permit requests from internal network
  * Webserver has DNS which won't deliver request to the webserver
  * Webserver is not permitted to make HTTP requests
  * Webserver fails SSL negotiation (PHP5.6 requires a [valid certificate chain](http://php.net/manual/en/migration56.openssl.php) installed, see note below)
  
  ## Misconfigured base URL / access URL
  
  CiviCRM requires a single configured canonical base URL, and it *might* be that if this doesn't match the URL you're using then CiviCRM won't handle the dashboard requests correctly. Check that the value defined for `CIVICRM_UF_BASEURL` in your `civicrm.settings.php` corresponds to the URL you're using - including both schema (`http://` or `https://`) and hostname (`example.org` or `www.example.org`).
  
  Because this can cause various issues, I recommend setting up an automatic redirect to prevent visitors viewing the site via the "wrong" URL (which will appear to work fine, except when it doesn't). See your webserver's documentation for how to do this - I think both Drupal and WordPress `.htaccess` files contain example rewrite snippets?
  
  ## PHP5.6 and SSL sites
  
  A few reports are surfacing of the [changed default in PHP v5.6](http://php.net/manual/en/migration56.openssl.php) affecting sites ability to connect to themselves (and to CiviCRM.org). In addition to having your SSL certificate correctly installed, PHP requires a correctly installed certificate chain to connect to SSL sites (including the local site). If your CA chain is outdated on the webserver, this may lead to failed dashboard and other issues when communicating with remote sites using SSL (payment processors, CiviCRM.org, and local requests such as dashboard widgets and API over HTTP).
  
  > **Comments:**
  > **username_5**: See also [Dashlet refresh can crash server](https://issues.civicrm.org/jira/browse/CRM-16035) but I don't think that's your problem.  
  > **username_0**: Thanks, the problem was that the civicrm wordpress install is behind a varnish proxy and the local DNS response to the domain was incorrect.  
  > **username_6**: how can this be resolved if the dashboard doesn't load only to some users? All the Drupal users have contact records in CiviCRM  
  > **username_5**: At a guess @username_6 that might affect specific users if their permissions granted them access to a dashboard which took overlong to render. Once I was confident the issue affected users differently, I'd continue debugging by inspecting your webserver logs and seeing which dashboard reports are rendered for the affected and unaffected users.  
  > **username_6**: thanks @ chris, i'm getting this error from certain users: $Fatal Error Details = Array (     [callback] => Array         (             [0] => CRM_Core_Error             [1] => handle         )      [code] => 0     [message] =>     [mode] => 16     [debug_info] =>     [type] => PEAR_Error     [user_info] =>     [to_string] => [pear_error: message="" code=0 mode=callback callback=CRM_Core_Error::handle prefix="" info=""]  
  > **username_5**: Recommend answering a separate question with your debug info front and centre @username_6, maybe mention this question and what's different about your situation so it's obviously not a dupe. Easier for people to help if it's not just in a comment on another Q.  
  > **username_5**: That error message isn't so helpful ... I think you'll need some help teasing out the source of the problem.  
  > **username_7**: @ChrisBurgess nice answer :)  
  
  ---
  
  ### Answer by username_2 on 2015-06-23. Score: 2
  
  This can also happen if you have an authorised CiviCRM user who does not have a contact record i.e. you haven't sync'd users to contacts. I've only seen this where Drupal was the CMS, but it was 100% reproducible.
  
  
  ---
  
  ### Answer by username_3 on 2015-11-12. Score: 1
  
  Just FYI, I had a problem where my dashlets would not load after upgrading from Apache 2.2 to 2.4. We have https with a certificate from Comodo and the problem was that our security certificate was no longer installed correctly after the upgrade, somehow causing Civi not to be able to load the dashboard.
  
  Browsers were still recognizing the certificate, so at first I didn't know there was a problem with the certificate. I needed to move the chain/bundle certificates over to the main SSLCertificateFile file (chain file certificates were deprecated in Apache 2.4). As soon as I fixed the certificate and reloaded Apache, back came the dashboard!
  
  
  ---
  
  ### Answer by username_4 on 2015-07-01. Score: 1
  
  I faced this issue and had to reinstall (not duplicate) the wordpress site using the following procedure:
  1. exported content using wordpress export
  2. copied theme folder and uploads
  3. clean install of wordpress
  4. install civicrm
  5. enabled theme
  6. import of content
  
  This was not due to active plugins. Something must of become corrupted in WordPress.
  
  
  ---
  
  