I just noticed these errors on our worker host:
```
[21-Jul-2014 05:03:25 UTC] [2014-07-21 15:03:25] EXCEPTION: (HTTPFutureResponseStatusCURL) [cURL/7] (http://localhost:22281/) <CURLE_COULDNT_CONNECT> The cURL library raised an error while making a request. You may be able to find more information about this error (error code: 7) on the cURL site: http://curl.haxx.se/libcurl/c/libcurl-errors.html#CURLECOULDNTCONNECT at [<phutil>/src/future/http/HTTPSFuture.php:363]
[21-Jul-2014 05:03:25 UTC] #0 HTTPSFuture::isReady() called at [<phutil>/src/future/Future.php:39]
[21-Jul-2014 05:03:25 UTC] #1 Future::resolve() called at [<phutil>/src/future/http/BaseHTTPFuture.php:277]
[21-Jul-2014 05:03:25 UTC] #2 BaseHTTPFuture::resolvex() called at [<phabricator>/src/applications/notification/client/PhabricatorNotificationClient.php:49]
[21-Jul-2014 05:03:25 UTC] #3 PhabricatorNotificationClient::postMessage(array) called at [<phabricator>/src/applications/notification/client/PhabricatorNotificationClient.php:34]
[21-Jul-2014 05:03:25 UTC] #4 PhabricatorNotificationClient::tryToPostMessage(array) called at [<phabricator>/src/applications/feed/PhabricatorFeedStoryPublisher.php:182]
[21-Jul-2014 05:03:25 UTC] #5 PhabricatorFeedStoryPublisher::sendNotification(integer) called at [<phabricator>/src/applications/feed/PhabricatorFeedStoryPublisher.php:115]
[21-Jul-2014 05:03:25 UTC] #6 PhabricatorFeedStoryPublisher::publish() called at [<phabricator>/src/applications/repository/worker/PhabricatorRepositoryCommitHeraldWorker.php:383]
[21-Jul-2014 05:03:25 UTC] #7 PhabricatorRepositoryCommitHeraldWorker::publishFeedStory(PhabricatorRepository, PhabricatorRepositoryCommit, PhabricatorRepositoryCommitData) called at [<phabricator>/src/applications/repository/worker/PhabricatorRepositoryCommitHeraldWorker.php:84]
[21-Jul-2014 05:03:25 UTC] #8 PhabricatorRepositoryCommitHeraldWorker::applyHeraldRules(PhabricatorRepository, PhabricatorRepositoryCommit) called at [<phabricator>/src/applications/repository/worker/PhabricatorRepositoryCommitHeraldWorker.php:17]
[21-Jul-2014 05:03:25 UTC] #9 PhabricatorRepositoryCommitHeraldWorker::parseCommit(PhabricatorRepository, PhabricatorRepositoryCommit) called at [<phabricator>/src/applications/repository/worker/PhabricatorRepositoryCommitParserWorker.php:44]
[21-Jul-2014 05:03:25 UTC] #10 PhabricatorRepositoryCommitParserWorker::doWork() called at [<phabricator>/src/infrastructure/daemon/workers/PhabricatorWorker.php:87]
[21-Jul-2014 05:03:25 UTC] #11 PhabricatorWorker::executeTask() called at [<phabricator>/src/infrastructure/daemon/workers/storage/PhabricatorWorkerActiveTask.php:124]
[21-Jul-2014 05:03:25 UTC] #12 PhabricatorWorkerActiveTask::executeTask() called at [<phabricator>/src/infrastructure/daemon/workers/PhabricatorTaskmasterDaemon.php:19]
[21-Jul-2014 05:03:25 UTC] #13 PhabricatorTaskmasterDaemon::run() called at [<phutil>/src/daemon/PhutilDaemon.php:84]
[21-Jul-2014 05:03:25 UTC] #14 PhutilDaemon::execute() called at [<phutil>/scripts/daemon/exec/exec_daemon.php:111]
```
We have two hosts in our Phabricator setup: one app server (running the PHP application + NodeJS server for Aphlict) and one worker server (running the daemons). The worker host is trying to `curl` the NodeJS notifications server (which isn't running on localhost). Am I meant to set `notifications.server-uri` on the worker host?
I'm not sure if this has always been happening (and I haven't realised) or if this is relatively new...