HAProxy cannot bind STUN port anymore #240

New Issue

raucao · 2020-11-20T18:29:11Z

raucao commented

2020-11-20 18:29:11 +00:00

After updating the packages on draco, haproxy failed to start with this error:

Starting proxy ejabberd_stun: cannot bind socket [148.251.237.73:58728]

I commented that entry in haproxy.cfg for now, meaning audio/video calls via XMPP signaling are more likely to fail until this is fixed.

After updating the packages on draco, haproxy failed to start with this error: > Starting proxy ejabberd_stun: cannot bind socket [148.251.237.73:58728] I commented that entry in `haproxy.cfg` for now, meaning audio/video calls via XMPP signaling are more likely to fail until this is fixed.

raucao added the

bug

label 2020-11-20 18:29:11 +00:00

raucao commented

2020-11-23 17:16:57 +00:00

I commented that entry in haproxy.cfg for now, meaning audio/video calls via XMPP signaling are more likely to fail until this is fixed.

Actually, we're not using the node on draco in production yet, so there's currently no problem. It only becomes an issue when we roll out the cluster.

> I commented that entry in haproxy.cfg for now, meaning audio/video calls via XMPP signaling are more likely to fail until this is fixed. Actually, we're not using the node on draco in production yet, so there's currently no problem. It only becomes an issue when we roll out the cluster.

greg referenced this issue from a commit

2020-11-25 15:36:26 +00:00

Move TURN port to a different range It landed on a port used by PostgreSQL. Also switch STUN/TURN to TCP because HAProxy does not support UDP. Closes #240

greg referenced a pull request that will close this issue

2020-11-25 15:44:32 +00:00

Enable ejabberd clustering #246

raucao closed this issue

2020-11-25 16:10:14 +00:00

Sign in to join this conversation.