CiviCRM Community Forums (archive)

Just upgraded to CiviCRM 2.0.  Everything went smoothly, except now CiviCRM is warning me "HTTPS is not set up on this machine."  If I go into Admin -> Global Settings -> Resource URLs, I see that "Force Secure URLs" is set to "Yes", but if I try to save those settings, I get an error "You need to set up a secure server before you can enable SSL."

SSL is set up and working for the site -- has been for a while, and was working fine in CiviCRM 1.9.  If I manually change the URL to "https://..." in the address bar of my browser and go into Admin, then the "HTTPS is not set up on this machine" warning disappears, but I still get the other error in the Resource URLs page.  Also, Contribution pages are not work (same "SSL not enabled" error).

I see that there is a CRM_Utils_System::checkURL method that gets called to verify that https is working, but I'm unclear why that check would be failing.  I can visit any https URL on the site in my browser and it works fine.

You are right -- apache is returning 403 for the HEAD requests sent by PEAR/checkURL.  I don't understand why that's the case, because you can see a couple of GET requests from my browser which work fine.


199.5.xxx.xxx - - [15/Mar/2008:10:13:40 -0700] "HEAD /db/ HTTP/1.1" 403 - "-" "PEAR HTTP_Request class ( http://pear.php.net/ )"
199.5.xxx.xxx - - [15/Mar/2008:10:13:41 -0700] "HEAD /db/ HTTP/1.1" 403 - "-" "PEAR HTTP_Request class ( http://pear.php.net/ )"
76.102.xxx.xxx - - [15/Mar/2008:10:34:41 -0700] "GET /db/ HTTP/1.1" 302 - "-" "Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.12) Gecko/20080201 Firefox/2.0.0.12"
76.102.xxx.xxx - - [15/Mar/2008:10:34:42 -0700] "GET /db/civicrm/dashboard?reset=1 HTTP/1.1" 200 12436 "-" "Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.12) Gecko/20080201 Firefox/2.0.0.12"

Okay, figured it out.  I have Drupal access control set so that only authenticated users can access CiviCRM, and I also had the Drupal front page set to /civicrm.  We don't have any content in Drupal other than CiviCRM, so this made sense to me.  With this config, unauthenticated users are prompted to log in as soon as they hit the Drupal base URL.

From a web browser, it's not obvious that the "please authenticate" page returned by Drupal is actually a 403 "error page."  So PEAR was getting 403 when it checked the base URL because it wasn't authenticated.  Of course when I visited the same URL in my browser, my session/login was cached and it seemed to be working fine.

Anyway, I set the Drupal front page to something else (which doesn't require authentication), and it's working fine now.  I'm puzzled now how it was working before under CiviCRM 1.9 though.

We were having the same problem. Come to find out, it was because we had the Drupal site set to offline for maintenance. Once we turned that off, everything was fine.

Just a bit of a pain, since sometimes you need to be able to take down the site for maintenance on CiviCRM.