Page MenuHomePhabricator

Exception in master (related to cluster functioning)
Closed, ResolvedPublic

Description

Hi everyone,

I'm running phabricator from git master branch (91479e2832817bb7e021d879036caec5672109d2). After tonight's frequently happening upgrade on my server, an Exception is thrown when accessing WebUI:

Exception
Phabricator is not configured to serve cluster requests. Set `cluster.addresses` in the configuration to whitelist cluster hosts before sending requests that use a cluster authentication mechanism.

This is the corresponding log:

[14-Apr-2016 12:57:02 Europe/Berlin] [2016-04-14 12:57:02] EXCEPTION: (Exception) Phabricator is not configured to serve cluster requests. Set `cluster.addresses` in the configuration to whitelist cluster hosts before sending requests that use a cluster authentication mechanism. at [<phabricator>/src/infrastructure/env/PhabricatorEnv.php:799]
[14-Apr-2016 12:57:02 Europe/Berlin] arcanist(head=master, ref.master=737f5c0df976), phabricator(head=master, ref.master=91479e283281), phutil(head=master, ref.master=a46f7b7e5d80)
[14-Apr-2016 12:57:02 Europe/Berlin]   #0 <#2> PhabricatorEnv::isClusterAddress(string) called at [<phabricator>/src/infrastructure/env/PhabricatorEnv.php:793]
[14-Apr-2016 12:57:02 Europe/Berlin]   #1 <#2> PhabricatorEnv::isClusterRemoteAddress() called at [<phabricator>/src/aphront/site/PhabricatorSite.php:11]
[14-Apr-2016 12:57:02 Europe/Berlin]   #2 <#2> PhabricatorSite::shouldRequireHTTPS() called at [<phabricator>/src/aphront/configuration/AphrontApplicationConfiguration.php:346]
[14-Apr-2016 12:57:02 Europe/Berlin]   #3 <#2> AphrontApplicationConfiguration::buildController() called at [<phabricator>/src/aphront/configuration/AphrontApplicationConfiguration.php:205]
[14-Apr-2016 12:57:02 Europe/Berlin]   #4 <#2> AphrontApplicationConfiguration::processRequest(AphrontRequest, PhutilDeferredLog, AphrontPHPHTTPSink, MultimeterControl) called at [<phabricator>/src/aphront/configuration/AphrontApplicationConfiguration.php:145]
[14-Apr-2016 12:57:02 Europe/Berlin]   #5 <#2> AphrontApplicationConfiguration::runHTTPRequest(AphrontPHPHTTPSink) called at [<phabricator>/webroot/index.php:17]
[14-Apr-2016 12:57:02 Europe/Berlin]   #6 phlog(Exception) called at [<phabricator>/src/aphront/response/AphrontUnhandledExceptionResponse.php:20]
[14-Apr-2016 12:57:02 Europe/Berlin]   #7 AphrontUnhandledExceptionResponse::setException(Exception) called at [<phabricator>/webroot/index.php:21]

I tried to setup a fresh install just now and the same happens without anything changed aside from default Setup beside of:

  • mysql.host
  • mysql.user
  • mysql.pass
  • phabricator.base-uri
  • storage.local-disk.path
  • repository.default-local-path

The reproduction steps are:

  1. Make a clean install of Phabricator following official Guide
  2. Try to open the Website

Event Timeline

Judge created this task.Apr 14 2016, 11:02 AM

workaround:

./bin/config set cluster.addresses '["0.0.0.0/0"]'

D11159 seems to be related

Error if cluster.addresses is not set at all:

Phabricator is not configured to serve cluster requests. Set `cluster.addresses` in the configuration to whitelist cluster hosts before sending requests that use a cluster authentication mechanism.

error message if cluster.address is set to 127.0.0.0/8:

Phabricator is configured in cluster mode and the address this request was received on ("$ipaddress") is not whitelisted as a cluster address.
epriestley added a subscriber: epriestley.EditedApr 14 2016, 11:33 AM

This should now be fixed in HEAD.

IMPORTANT: If you set cluster.addresses to ["0.0.0.0/0"], you should revert this change! As the documentation for the option notes, this is a dangerous change, and gives the entire internet elevated access to your install!

just updated, it works now without cluster.addresses set.

thanks!

Sorry about breaking this -- there are a lot of large changes going in this week related to T10751, so master might be a little less stable than usual until the dust settles there.

3c7 added a comment.Apr 14 2016, 11:39 AM

@epriestley Thanks for the quick fix!

I can confirm this is fixed now.
Thanks, @vinzent @epriestley , for this ultra quick fix!