On Tuesday, November 25, 2014 16:32 CET, "Martijn Rijkeboer" <mart...@bunix.org> wrote: > Hi, > > > I've just upgrade my server to 5.6 and having trouble starting > > Sogo. When starting Sogo I get the following error: > > > > [ERROR] <0x0x99ae0049590[WOWatchDog]> unable to listen on specified > > port, check that no other process is already using it > > > > I've configured Sogo to use 127.0.0.1:20000 and netstat -na shows that > > that port is not used. I've also removed the configuration of the > > WOPort but getting the same error. Any suggestions on what I'm doing > > wrong? > > I've changed the WOPort to *:20000 and now it works. Too bad it doesn't > work with 127.0.0.1:20000 as that is the default and I like to keep sogo > listening only on the loopback address. Any suggestion what causes this?
as a temporary workaround, I haven't tried it yet, maybe it would help preventing access configure: -WOHttpAllowHost 127.0.0.1 either as command line parameter, or with defaults write or in sogo.conf. whereever you prefer ;) Sebastian > > Kind regards, > > > Martijn Rijkeboer >
