Answers.Body: <p>Check your CiviCRM base URL - the CMS configuration (<code>$base_url</code> in Drupal settings.php), CiviCRM (<code>CIVICRM_UF_BASEURL</code> in civicrm.settings.php) and webserver configuration (canonical location you rewrite to) must all match.</p>
  
  <p>For the dashboard to work, the webserver needs to be able to access the website itself.</p>
  
  <p>If you're hosted at <a href="https://www.example.org" rel="nofollow">https://www.example.org</a> the CiviCRM dashboard needs to be able to retrieve <a href="https://www.example.org/civicrm/report/instance/68" rel="nofollow">https://www.example.org/civicrm/report/instance/68</a> and so forth.</p>
  
  <p>A webserver which can't access itself directly (reverse proxy, SSL, DNS may factor in) will fail loading the dashlets.</p>
  
  <p>Same question, longer answer: <a href="https://civicrm.stackexchange.com/questions/3426/the-dashboard-does-not-render/3430#3430">The dashboard does not render</a></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-08-06T13:57:26.487Z
Answers.Text: I verified all of our settings (went into the config files, can hit something like https://www.example.org/civicrm/report/instance/68 from a browser on the box), and all seems to work.  Still, the dashlet is on a constant load.
Answers.UserDisplayName: Cheryl
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-08-06T19:32:53.150Z
Answers.Text: From here, I'd recommend watching your webserver logs (PHP and webserver if separate) while loading the dashboard, and see if that gives any information. Note that the *lack* of a (successful) request may be information as well!
Answers.UserDisplayName: Chris Burgess
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-08-05T20:08:57.430Z
Answers.LastActivityDate: 2015-08-06T10:24:10.613Z
Answers.LastEditDate: 2015-08-06T10:24:10.613Z
Answers.UserDisplayName: Chris Burgess
Answers.Body: <p>Chris' suggestion to check your Base URL is a good one - I'd also check <strong>Administer menu > System Settings > Resource URLs</strong>, because if they're misconfigured you'll see similar issues.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-08-06T17:35:36.073Z
Answers.Text: All of the settings are correct. But, thanks for your entry because it did lead me to this topic: https://forum.civicrm.org/index.php?topic=6090.0 . I'm getting an error when I use the simple curl request script " Connected to example.org (xxx.xxx.xxx.xxx) port 443 (#0)
  * Initializing NSS with certpath: sql:/etc/pki/nssdb
  * skipping SSL peer certificate verification
  * NSS: client certificate not found (nickname not specified)
  * NSS error -12227 (SSL_ERROR_HANDSHAKE_FAILURE_ALERT)
  ... so, does CiviCRM rely on NSS for a client PKI cert (we have 2way SSL on)
Answers.UserDisplayName: Cheryl
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-08-06T17:46:10.593Z
Answers.Text: Cheryl - that deserves to be asked as its own question so it gets more attention!
Answers.UserDisplayName: Jon G - Megaphone Tech
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-08-06T15:06:14.197Z
Answers.LastActivityDate: 2015-08-06T15:06:14.197Z
Answers.UserDisplayName: Jon G - Megaphone Tech
Answers.Body: <p>There was also the issue <a href="https://issues.civicrm.org/jira/browse/CRM-16035" rel="nofollow">CRM-16035: Dashlet refresh <em>can</em> crash server - replace use of HTTP_Request</a> recently, but what you describe doesn't sound like that.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-08-06T13:59:15.677Z
Answers.Text: Agreed.  Hitting this directly: https://www.example.org/civicrm/ajax/dashboard?op=get_widget&key=fc010d2bf22156d7d81cd385a7dd9954&id=1#overlay-context=user/1 (so shouldn't have a multiple thread issue) fails
Answers.UserDisplayName: Cheryl
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-08-05T20:10:34.447Z
Answers.LastActivityDate: 2015-08-05T20:10:34.447Z
Answers.UserDisplayName: Chris Burgess
Body: <p>We had a CiviCRM installation where the dashlets worked fine...until...we configured Apache to forward all requests over 443 (https).</p>
  
  <p>It seems that now an AJAX callback is failing (going directly to the callback leads to a "Sorry but we are not able to provide this at the moment." error. The error details with debugging turned on state:</p>
  
  <p>$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=""] ) </p>
  
  <p>Which is not terribly helpful for us who are not very familiar with the CiviCRM core.  Any ideas why this issue is occurring and/or what the fix might be?</p>
  
  <p>Thanks!</p>
  
Tags: <dashboard>
Title: SSL enabled CiviCRM with forever loading dashlets?
ThreadText: # SSL enabled CiviCRM with forever loading dashlets?
  
  (Asked by: username_0 on 2015-08-05)
  
  We had a CiviCRM installation where the dashlets worked fine...until...we configured Apache to forward all requests over 443 (https).
  
  It seems that now an AJAX callback is failing (going directly to the callback leads to a "Sorry but we are not able to provide this at the moment." error. The error details with debugging turned on state:
  
  $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=""] )
  
  Which is not terribly helpful for us who are not very familiar with the CiviCRM core. Any ideas why this issue is occurring and/or what the fix might be?
  
  Thanks!
  
  **Tags:** dashboard
  
  
  ---
  
  ## 3 answers
  
  ### Answer by username_1 on 2015-08-05. Score: 3
  
  Check your CiviCRM base URL - the CMS configuration (`$base_url` in Drupal settings.php), CiviCRM (`CIVICRM_UF_BASEURL` in civicrm.settings.php) and webserver configuration (canonical location you rewrite to) must all match.
  
  For the dashboard to work, the webserver needs to be able to access the website itself.
  
  If you're hosted at <https://www.example.org> the CiviCRM dashboard needs to be able to retrieve <https://www.example.org/civicrm/report/instance/68> and so forth.
  
  A webserver which can't access itself directly (reverse proxy, SSL, DNS may factor in) will fail loading the dashlets.
  
  Same question, longer answer: [The dashboard does not render](https://civicrm.stackexchange.com/questions/3426/the-dashboard-does-not-render/3430#3430)
  
  > **Comments:**
  > **username_0**: I verified all of our settings (went into the config files, can hit something like https://www.example.org/civicrm/report/instance/68 from a browser on the box), and all seems to work.  Still, the dashlet is on a constant load.  
  > **username_1**: From here, I'd recommend watching your webserver logs (PHP and webserver if separate) while loading the dashboard, and see if that gives any information. Note that the *lack* of a (successful) request may be information as well!  
  
  ---
  
  ### Answer by username_2 on 2015-08-06. Score: 1
  
  Chris' suggestion to check your Base URL is a good one - I'd also check **Administer menu > System Settings > Resource URLs**, because if they're misconfigured you'll see similar issues.
  
  > **Comments:**
  > **username_0**: All of the settings are correct. But, thanks for your entry because it did lead me to this topic: https://forum.civicrm.org/index.php?topic=6090.0 . I'm getting an error when I use the simple curl request script " Connected to example.org (xxx.xxx.xxx.xxx) port 443 (#0) * Initializing NSS with certpath: sql:/etc/pki/nssdb * skipping SSL peer certificate verification * NSS: client certificate not found (nickname not specified) * NSS error -12227 (SSL_ERROR_HANDSHAKE_FAILURE_ALERT) ... so, does CiviCRM rely on NSS for a client PKI cert (we have 2way SSL on)  
  > **username_2**: username_0 - that deserves to be asked as its own question so it gets more attention!  
  
  ---
  
  ### Answer by username_1 on 2015-08-05. Score: 0
  
  There was also the issue [CRM-16035: Dashlet refresh *can* crash server - replace use of HTTP\_Request](https://issues.civicrm.org/jira/browse/CRM-16035) recently, but what you describe doesn't sound like that.
  
  > **Comments:**
  > **username_0**: Agreed.  Hitting this directly: https://www.example.org/civicrm/ajax/dashboard?op=get_widget&key=fc010d2bf22156d7d81cd385a7dd9954&id=1#overlay-context=user/1 (so shouldn't have a multiple thread issue) fails  
  
  ---
  
  