logo       

Re: [PyICQ-t] Can't login to the web interface: msg#00121

network.jabber.py-transports

Subject: Re: [PyICQ-t] Can't login to the web interface

On Sat, 2006-03-11 at 11:08 -0500, Daniel Henninger wrote:
> > I have see something like this on the mailing list, about allowing
> > non-ssl to the jabber server. I can login to my jabber server with or
> > without ssl. When I try to login to the web interface and do a netstat
> > at the same time, I can't see anything except
> >
> > tcp 0 0 0.0.0.0:12001 0.0.0.0:*
> > LISTEN (I have changed the default port)
>
> Annnnd that would be the problem. ;D It's only going to try 5222
> right now. I'm not sure what the best way to do other ports is.
> What I'm leaning towards is that I would type in:
>
> daniel@xxxxxxxxxxxxxxxxxxxxxx:12001
>
> (and you don't have to specify the :whatever part if you run on
> 5222) If you want to use it in the meantime, edit src/web/
> handler.py, look for 5222, and change it to 12001. =)
>
> Daniel
>
> >
> > Any ideas ?
> >
> > Regards
> >
> > Nicolas
> >
> > _______________________________________________
> > py-transports mailing list
> > py-transports@xxxxxxxxxxxxxxxxx
> > http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
> >
> >

Hi,

I thing I have not been clear in my previous message :) I have changed
the default port of the pyicq web interface, not the jabber one ;) So if
pyicq try to login in my jabber server (ejabberd) using the port 5222,
it should work. What I have tried to explain is when I log the the web
interface with my jid and do a netstat at the same time, I can't see a
connection attempts to my jabber server on port 5222

Nicolas


<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise