Frequently Asked Questions

Mar 28, 2024 - 11:26am

 [F] Frequently Asked Questions  / Support Assistant  / Web Crossing isn't Working...  / Web Crossing is Unresponsive  / Error Messages  / Errors in webx.log  /

webx-go error: could not bind stream socket to ip:port n.n.n.n:nn -- another process may be using this ip:port -- Address already in use

Rate This FAQ
Rating: ***½ (based on 3 votes)

Created On: 15 Sep 2002 2:03 pm
Last Edited: 17 Feb 2003 9:39 am

Question Printer Friendly

See Below.

Answer

Seen when you attempt to launch Web Crossing and there is some other process already binding the indicate port on the indicated IP. For port 25 this is most often sendmail, for 110 another email server, for 80 another web server, and so on. can also indicate that webx was not started a root or su or that port monitoring software has interferred.

Make sure that you have Web Crossing's services bound to its specific IP address (in a shared environment) and that any other servers on the same box are configured to NOT bind to the IP address assigned to Web Crossing.

So for example, rather than just "25" in the SMTP email section, you should have ip:25 (ex: 10.0.0.6:25) Do this for all services that are activated (HTTP, POP, IMAP, SMTP, etc)