tags 561705 - moreinfo unreproducible + confirmed thanks Thanks for your report. Finally, I could reproduce this.
This bug is causing the following problems: * By default, jabberd only will listen on :: IPv6 address. * If you configure jabberd to explicitly listen on any wildcard address like :: o 0.0.0.0, it will refuse to start. As workaround while this is sorted out, I recommend you to configure your jabberd to explicitly listen on the IPv4 address that you need. <ip port="5222">192.168.32.21</ip> or your public IPv4 address: <ip port="5222">xxx.xxx.xx.xxx</ip> Regards, -- Miguel Landaeta, miguel at miguel.cc secure email with PGP 0x7D8967E9 available at http://keyserver.pgp.com/ "Faith means not wanting to know what is true." -- Nietzsche -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
