ejabberd - Comments for "enabling mod_proxy65 breaks ejabberd"

Re: Fixed problem but back to earlier problem

zinid — Thu, 11 Jun 2009 11:14:42 +0000

You should not touch auth_type option until you completely sure your clients support SOCKS5 authentication.

Try Psi, Gajim, Tkabber and Jabbim

mfoss — Thu, 11 Jun 2009 09:40:18 +0000

perazim2 wrote:

My question is: is it possible to use Pidgin to use the file transfer proxy in Ejabberd or should I look for another client? If the later, can you recommend another client?

I haven't try file transfer proxy. You could try Psi, Gajim, Tkabber and Jabbim. They are multiplatform and I imagine some of them implement proxied file transfer.

Fixed problem but back to earlier problem

perazim2 — Thu, 11 Jun 2009 08:42:16 +0000

Thanks,

mod_proxy65 was in the modules section.

Changing the proxy host name to another (pointing to the same ip) fixed the reported problem.

Which brings me back to an earlier (unreported) problem that doesn't have to do with Ejabberd:

I am running Pidgin-2.5.6-1.fc10 as the client. After digging through their support files I find that there is limited file transfer support for the Jabber protocol. They state that it will work if the machines can see each other without a firewall in the middle. My configuration is that both clients are behind separate firewalls but connected to the server by a vpn. Indeed I find that if I remove the firewalls, file transfer does work but using the public subnet not the vpn subnet. I have tried various configuration attempts in Pidgin but it still seems to only use the public subnet for file transfers.

My question is: is it possible to use Pidgin to use the file transfer proxy in Ejabberd or should I look for another client? If the later, can you recommend another client?

Thanks again

Set a good Jabber ID for Proxy65 sevice.

mfoss — Wed, 10 Jun 2009 15:01:43 +0000

perazim2 wrote:

In ejabberd.cfg,
{hosts, ["hub"]}.

Ok, then your Jabber service will be available in the Jabber ID: hub

perazim2 wrote:

I enable mod_proxy65 for transferring files with:

{mod_proxy65, [
{host,"hub"},
{name, "File Transfer Proxy"},
{ip, {172, 16, 1, 1}},
{port,7777},
{auth_type, plain}
]},

not only does the file transfer not work but ejabberd drops clients every few seconds requiring them to reconnect. The clients never seem to be fully connected and seeing the server.

There are two reasons that configuration may not work:

1. Remember that mod_proxy65 is an ejabberd module, so you must define it in the 'modules' section of ejabberd.cfg, not in the 'listen' section:

{modules,
 [
  {mod_proxy65, [ ... ]},
  ...
 ]}.

2. You configured the Proxy65 service to have as Jabber ID "hub". That Jabber ID is already assigned for the Jabber server itself, so you are provoking a problem of unknown consequences.
Instead of

  {mod_proxy65,  [
  		  {host,"hub"},
                  ...

you better put:

  {mod_proxy65,  [
  		  {host,"proxy65.hub"},
                  ...