===Background===
In the timespan between week 15 and week18 Aphlict configuration has been changed to support clustering.
I've upgraded our install and reconfigured our installation as specified here: https://secure.phabricator.com/book/phabricator/article/notifications/
- The "Cluster Notification Status" page now shows both the client and admin server up and running.
- I can successfully connect to the websocket endpoint using a standard weboscket client and I can see the connection count going up in the "Cluster Notification Status" page.
===Problem===
Desktop notification are not working anymore within the Phabricator webapp.
I've brought up a test instance on Phacility for comparison and I can see our host is now missing a line similar to this that the test host serves in every page:
```
"aphlict-listen":[{"websocketURI":"wss:\/\/nlb001.phacility.com:443\/~test-ggh2o4cguhyk\/?instance=test-ggh2o4cguhyk"
```
Of course our wss:// URI would be different than this one but any page served by our install is totally missing the "aphlict-listen" field.
To confirm this I've used Chrome developer tools' network tab to check for any WS connection and I can also confirm that on the Phacility Test Host I can see the wss:// request with status 101.
That same line is not present anymore on hour host (websocket notifications were running fine before the upgrade).
==Reproduction steps==
Upgrade a single hosted, Debian based Phabricator instance with working websocket notifications from the old non-clustered configuration type (stable branch 2016 week 15) to the new Aphlict clustered notification configuration (stable branch 2016 week 18).