I am working with the SVN trunk of ejabberd which I have compiled on an Ubuntu system.
LDAP authentication is working and the server is up, but I cannot get mod_proxy65 file transfer proxy to work. I am monitoring the logs and I see this:
=INFO REPORT==== 2008-03-26 10:50:32 ===
D(<0.1690.0>:ejabberd_c2s:1335) : Send XML on stream = "<iq from='pkrekelberg@MYDOMAIN.com/benedictus' to='pkrekelberg@MYDOMAIN.com/Exodus' id='jcl_316' type='error'>\n<error code='404' type='cancel'>\n<item-not-found xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/>\n</error>\n</iq>"One end is able to begin a transfer, the other end receives confirmation that a transfer has been initiated. When I agree to it on the other end, the initiating end says the other end has refused the transfer. This coincides with the above log line. I have tried setting the mod_proxy65 port to something different, etc. but need some guidance on how this should be done. How does this mod work by default and what ports are used?
Thanks.
I have verified that file
I have verified that file transfers work behind the corporate firewall, but not outside. What ports are used by mod_proxy65?
I have this in my ejabberd.cfg file:
{mod_proxy65, [{port, 5223},{max_connections, 5}]},
5223 is open on the firewall, so it must be using other ports which are not.
Re: mod_proxy65 File Transfer: error code 404
{mod_proxy65, [{port, 5223},{max_connections, 5}]},
5223 is open on the firewall, so it must be using other ports which are not.
5223 is reserved for XMPP SSL. Are you sure this port is free (e.g. ejabberd doesn't listen for SSL connection on 5223)?
BTW, if you have NAT, proxy65 will not work between your users and users from other world.
gotcha
{mod_proxy65, [{port, 5223},{max_connections, 5}]},
5223 is open on the firewall, so it must be using other ports which are not.
5223 is reserved for XMPP SSL. Are you sure this port is free (e.g. ejabberd doesn't listen for SSL connection on 5223)?
BTW, if you have NAT, proxy65 will not work between your users and users from other world.
Ah, OK. Yes, the server is NAT'd behind a corporate firewall and routers. Any other way to enable file transfer for users?