Connection always times out with 0.11.3
Vasili Sviridov
after doing that I can no longer connect to MSN. I get messages about
connection timeouts, even though the switchboard server address and
port are correct and I can telnet to the switchboard no problem. After
rolling back to 0.11.2-dev connectivity resumed.
mercurial snapshot seems to behave the same.
Any advice is appreciated...
Kelly Hays
I had this problem last week. It turns out that the meaning of one of
the lines in the config file has changed slightly.
The part I had to change is below.
<!-- The public IP or DNS name of the machine the transport is running on -->
<!-- This is needed for file transfer!! This is also used as the IP
address for
outgoing connections -->
<host>127.0.0.1</host>
My server is behind a NAT firewall and I had the Host set to my public
IP address. After the upgrade I had to change it to my internal
RFC1918 address (192.168.x.x.)
> >
>
Hope that helps.
--
Kelly Hays
XMPP:kelly...@jkhfamily.org
Vasili Sviridov
127.0.0.1 in it. Cause my transports run at same machine as server
(ejabberd 2.0.0)
On Feb 22, 3:12 pm, "Kelly Hays" <j.kelly.h...@gmail.com> wrote:
Vasili Sviridov
server... Is that the transport cannot connect to MSN server.
Vasili Sviridov
Failed to connect to MSN servers: [Failure instance: Traceback
(failure with no frames): <type 'exceptions.Exception'>: Timeout]
Kelly Hays
>
> Hmm, i'm reusing config file from previous instance, and it has
> 127.0.0.1 in it. Cause my transports run at same machine as server
> (ejabberd 2.0.0)
If you look at the comment above the <host>127.0.0.1</host> line you
can see the following sentence has been added: "This is also used as
the IP address for outgoing connections"
If you don't change that address then the transport will try to talk
to the MSN servers using the loopback address (127.0.0.1) which is not
possible.