Page MenuHomePhabricator

"Phabricator is not configured to serve cluster addresses" when not running in a cluster
Closed, InvalidPublic

Description

I just upgraded Phabricator, and now my Phabricator instance responds with:

pasted_file (228×1 px, 21 KB)

This is my local configuration (I censored the sensitive information):

{
  "amazon-s3.endpoint": "s3-us-west-2.amazonaws.com",
  "amazon-s3.region": "us-west-2",
  "amazon-ses.endpoint": "email.us-west-2.amazonaws.com",
  "amazon-ses.secret-key": ".......",
  "amazon-ses.access-key": ".......",
  "amazon-ec2.access-key": ".......",
  "security.alternate-file-domain": "https://rpcdn.com.au",
  "phd.user": "git",
  "security.require-https": false,
  "phabricator.allowed-uris": [
    "https://code.redpointsoftware.com.au/"
  ],
  "phabricator.base-uri": "https://code.redpointgames.com.au/",
  "mysql.pass": ".......",
  "mysql.user": ".......",
  "mysql.port": ".......",
  "mysql.host": "......."
}

Looking at the actual code, this exception comes from isClusterAddress in PhabricatorEnv, but all the call sites that call that method look to be checking to see if cluster.addresses is set in the configuration, which it clearly is not.

I am really confused as to why this would start happening. I'm going to dig through the code a bit more and find out what it thinks cluster.addresses is set to :/

Event Timeline

Looks like this was caused because my upgrade didn't upgrade all the way to HEAD (for some unknown reason :S ).