I think this was at least approximately resolved by D21115, which made the default log much quieter and the "debug" log more verbose.

This looks like an edge case that fell out of D19864, which was originally motivated by similar goals (fixing how test notifications work).

This is super old and doesn't have any apparent reproduction instructions.

T13182 was a resurgence of this exact issue, but I'm currently banking on the fix being a move to Ubuntu 16 with T13076 before this breaks again, given that it was stable for ~18 months.

D19384 cleans this up a little bit and mostly fixes the "phantom unread notification" issue in T8953.

The "Notification server not enabled" text should also link to the Aphlict documentation or something.

(These are in the menu.)

This is kind of time-specific since it has a version number, but I got Aphlict working on my server by navigating to phabricator/support/aphlict/server and running npm install ws@2.X (literal X) as root. This installed version 2.3.1 (im assuming the latest stable 2.X version). Upon restarting aphlict, the notifications work without raising exceptions.

See also vaguely related T12171.

Conpherence is repainting after D17713 but notification counts aren't, yet.

This could be prettier, but it's functional and has buttons you can click.

Tried again with node v6.9.4 (current version of node with CentOS7), and still has same problem 😢

This has been live for a while now.

I tried the openssl connection you suggested and it still bombed.

What about Node.js v0.10 and v0.12?

If you're still currently using Node.js v0.10 or v0.12, it is time to begin the transition to v4 or v6. Both v0.10 and v0.12 are considered to be in Maintenance mode currently and will fall off our support plan completely later this year.

I deployed this, seems to have worked properly in production.

Vaguely related: aphlict exited on notify001 with this error:

Hello
I agree with @richardvanvelzen this is very very useful option.
Especially in scenarios like this, for people that like to have important tasks open in tabs.

Note that it is possible to set a path to the websocket for every server as well. This is handy, for example, when your notification websocket is hosted behind the same URL as Phabricator itself. We have https://phabricator.ourcompany.net/ for Phabricator itself, and https://phabricator.ourcompany.net/ws/ for the notifictions websocket. This corresponds to the following client config:

T10402 is the "check client/server agreement about HTTPS" task.

Configuring the Preamble script is important for reverse-proxied configurations (you probably need to set REMOTE_ADDR up as well), and required for many things - which is why it is part of the install guide.

Wow, thanks for your fast and precise answers!! Using the file

We ran into this on a recent install - the fix was to configure the Preamble script to tell Phabricator it was being accessed over HTTPS (else it filtered out the HTTPS notification server) - check to see if "Connected" or "Disconnected" at the bottom of the notification popup (menu at the top of the screen - see this install). If you just get a grey bar at the bottom without either, you're hitting the same case where the client doesn't think it has a valid notification server.

https://hub.docker.com/r/hachque/phabricator/

is not supported by this install

Ah, it makes sense. Thanks!

I am seeing the same, and it makes sense, once you know it only contains waypoints that you click.

Thanks! The intended instruction was just "don't specify ssl.key, ssl.cert, etc.". D15787 should fix it.

I don't have to click "Cluster", it's just a subheader. Are you seeing something different?