Ivan Kurnosov
Ivan Kurnosov
It is still relevant.
Okay, I finally found the https://github.com/symfony/symfony/issues/24397 which provides [a workaround](https://github.com/symfony/symfony/issues/24397#issuecomment-1165392825), but wondering if the opinion of the core team has changed after 6 years.
In what was is it an improvement?
Where does the `44444` port number come from? Is it intentionally `44444` or confused with `4444`?
Is there anything listening `localhost:44444`? How did you check it?
`netstat -nlp | grep 44444` ?
`telnet localhost 44444` ?
And `phpunit-selenium` connects to it from the same machine?
Did it ever work? I don't see how that error can be possible in your case
Next my step to debug it would be to create a tiny php script that would connect to that port using `fsockopen` as well and see if it succeeds.