Yeah, you'll want to open one bug report per issue. Also, installations via third party installers are not supported and aren't considered a valid means to reproduce the issue. You may use a Phacility test instance if you want an easy, clean, reproducible installation quickly built.

As the notification is working on this site with the same browser that does not even connect to the web socket on mine, I believe that there is an error in my setup. I'd like to find it and probably that should become part of the documentation as the setup was quite a hassle so far.

Our documentation isn't meant to be a detailed howto for every single os/distribution or setup, just cover the basics as they relate to Phabricator itself. If the issue isn't specific to Phabricator, it's likely better covered by documentation elsewhere on the web.

Yeah, you'll want to open one bug report per issue.

That would be one ticket for each of

• Firefox does not connect
• listeners accumulate
• subscribers are not counted
• live notifications are not displayed

Should each of them have the (same) version and steps to reproduce introduction or should I link to this issue for that?
IMHO, apart from the accumulating listeners the other issue are probably only worth one.

Also, installations via third party installers are not supported and aren't considered a valid means to reproduce the issue. You may use a Phacility test instance if you want an easy, clean, reproducible installation quickly built.

I was under the impression that the docker image actually does a default installation as per installation guide?
I think that image is maintained by @hach-que.

Our documentation isn't meant to be a detailed howto for every single os/distribution or setup, just cover the basics as they relate to Phabricator itself. If the issue isn't specific to Phabricator, it's likely better covered by documentation elsewhere on the web.

There were several issues that have been reported as bugs and are fixed but not published or being worked around but are not mentioned in the documentation. I'd hoped to at least find mentions of these issues in the documentation especially since they sometimes arise directly from steps taken as described in the documentation. I can very well imagine that this is a corner case that is specific to Phabricator's or Aphlict's handling of apache proxied websockets.

Yeah that Docker instance is maintained by me. It's not intended to sit behind any kind of load balancing though (unless you're routing WebSockets directly to the client). Otherwise I have no idea if your Apache load balancer is interfering with the connection.

In T10783#170004, @hach-que wrote:

Otherwise I have no idea if your Apache load balancer is interfering with the connection.

I presume it is. I setup apache to proxy /ws/ to the exposed port 22280 of the phabricator docker container.

Some packet sniffing on the (docker network) bridge between apache and the docker container showed that the websocket is connected and the subscribe request is sent (as documented by the log excerpts above) but no response is made from aphlict even after triggering a test notification that is shown in the log with the correct subscriber ID.

How should I proceed in diagnosing this?

You probably need to configure Apache to correctly route the web sockets.

Alternatively, add another IP to your host and just route the Phabricator container out of a dedicated IP. That's the simplest way of getting this working.

Okay, I found the culprit in the apache configuration after debugging what happens in aphlict.

The problem was this:

<Location "/ws/">
ProxyPass        ws://phabricator.container:22280/ nocanon
</Location>

which should have been

<Location "/ws/">
ProxyPass        ws://phabricator.container:22280/ws/ nocanon
</Location>

(Note the additional ws/ at the end of the URL.)

This resulted in listeners requesting path / while the admin side added the path /ws/ so they got two different listener lists. I did not notice this discrepancy in the logs up until now, maybe it should be more prominent or the log format should be explained in the documentation?

After changing this I get live notifications on Chrome and the warning about too many listeners is gone and the subscribers show up on the /notification/status/ page.

However, on Firefox I still get "Setting Up Client". I will investigate that later.

Today the live notifications work in Firefox as well. I believe that it did not work yesterday due to caching.

I've marked D15705 as fixing this, since it makes our interpretation of the path unambiguous: we would no longer interpret /ws/ as a request for namespace "ws".

It sounds like everything else got sorted out or resolved on its own.