The error message is something along the lines of:
couldn't setup local SOCKS5 proxy on port 7777: Address already in use:
I don't think it's Jitsi starting the SOCKS5 proxy "on purpose" - it's
Smack, that does so by default.
Perhaps it starts it only under certain conditions, I'm not sure. I do know
that the continuous restarts stopped immediately after unloading jicofo -
so there's a strong indication that there exists at least some execution
path to that code.
If it's not used by Jitsi, I'll try to create a PR that prevents this from
On 4 September 2017 at 16:32, Damian Minkov <firstname.lastname@example.org> wrote:
Jicofo and jvb just start jetty instances on 8888 or 8080, and nothing
on 7777. At least I haven't seen such thing. Are you sure it is
jicofo, can you attach some logs.
On Mon, Sep 4, 2017 at 9:09 AM, Guus der Kinderen > <email@example.com> wrote:
> Hi all,
> Jicofo launches a SOCKS5 proxy on port 7777. Is this being used by Jitsi
> functionality, or is this a side-product of using Smack (which starts
> by default)? Can it be turned off?
> I've just had a server crash, that uses 7777 for something else
> a SOCKS5 proxy). Jicofo attempts to bind to 7777 over and over again,
> logging the fact on std-err. I had a server where that got logged to a
> non-rotating file, which caused the system to run out of free disk
> dev mailing list
> Unsubscribe instructions and other list options:
dev mailing list
Unsubscribe instructions and other list options: