Mykola

I'm not sure if I should create a separate issue, but it seems like the unix socket isn't working at all. For example, I tried to set up a jabber...

> Interesting, I see `Start accepting TCP connections at unix:/run/ejabberd/s2s.socket for ejabberd_s2s_in` in my log, but this file doesn't exist (but my version is 23.10, maybe this is fixed in...

> (when using `/tmp`, note that the systemd option `PrivateTmp=yes` can create a separate mountpoint and you will never see files from ejabberd's `/tmp`, that's why I use `/run` instead)...

Here is a 99% default service file that comes with the package in Arch Linux. The only change I made in this case is removing **AmbientCapabilities=CAP_NET_BIND_SERVICE**, as it is simply...

So, dear developers, will there be any investigation, clarifying questions, etc.?

> The accumulated problem description in this issue involves ejabberd 23.10, recent ejabberd, nginx, tor, systemd and all their configuration files. That is spread in several consecutive comments that add...

> Yes, there is a working example, fully published and 100% reproducible: [this PR](https://github.com/processone/ejabberd/pull/4340) uses unix domain socket and curl. I mean for s2s and c2s