0

I'm running ejabberd 17.04, and it keeps trying and failing roughly every three minutes to open an s2s connection to proxy.eu.jabber.org. The attempt fails because not only does proxy.eu.jabber.org not exist, but eu.jabber.org apparently doesn't exist either.

I know this connection is for federation, and I'd like it to work. But I know neither where to configure what it tries to connect to, nor what server I should use in place of the nonexistent proxy.eu.jabber.org. The proxy.eu.jabber.org address does not appear anywhere in its configuration files, not even as a commented-out default.

Can anyone advise?

Phil Stracchino
  • 1

1 Answers1

1

The proxy.eu.jabber.org address does not appear anywhere in its configuration files, not even as a commented-out default.

That address comes from old Pidgin clients, see this ticket: Please, remove "proxy.eu.jabber.org" from default pidgin configuration

it keeps trying and failing roughly every three minutes to open an s2s connection to proxy.eu.jabber.org.

You can prevent those connection attempts in the server adding options like that:

s2s_access: s2s

access_rules:
  ## Do not establish S2S connections with bad servers
  ## If you enable this you also have to uncomment "s2s_access: s2s"
  s2s:
    - deny:
       - server: "proxy.eu.jabber.org"
    - allow
Badlop
  • 580
  • 3
  • 5
  • Pidgin doesn't appear to have anything in its configuration for my own accounts, either. It's possible remote users' configurations have it. I've just implemented the s2s deny; that should resolve the proxy.eu issue. – Phil Stracchino Apr 05 '18 at 12:58