Server Bound to 0.0.0.0

[dante696]

Ar2rJk < Start your server as said above. The server won't recognize the ip binding without the parameters.
All official server had to use these parameters and it never workd without.

Dimmizer Please make sure, that port 9987 UDP is opened for your server and make sure that the ip is correct.

[Dimmizer]

Dimmizer Please make sure, that port 9987 UDP is opened for your server and make sure that the ip is correct.

I've never screwed with IP tables before since I've always had a control panel to do these kinds of things for me. Would you be so kind to provide me with the command to open the 9987 UDP port please .

[Ar2rJke]

I've never screwed with IP tables before since I've always had a control panel to do these kinds of things for me. Would you be so kind to provide me with the command to open the 9987 UDP port please .

sudo iptables -t filter -A INPUT -p udp -m udp --dport 9987 -j ACCEPT
sudo iptables -t filter -A OUTPUT -p udp -m udp --dport 9987 -j ACCEPT

edit by dante
Thank you

[maxi1990]

I checked my server's logs and came upon this errors (Serverversion 3.0.6.1):

2012-08-15 13:12:03.620126|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
2012-08-15 17:06:33.972160|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
2012-08-15 22:15:42.601877|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
2012-08-17 11:58:33.268864|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
2012-08-18 14:06:09.585633|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
2012-08-18 15:00:24.536588|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
2012-08-19 17:32:20.847950|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
2012-08-19 20:18:19.486270|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
2012-08-23 09:58:30.604515|ERROR   |ParamParser   |   | Protocol mismatch, old client or old server?
2012-08-23 09:58:52.467043|ERROR   |ParamParser   |   | Protocol mismatch, old client or old server?
2012-08-23 21:26:45.027493|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
2012-08-24 08:19:08.404707|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
2012-08-24 08:49:00.757839|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
2012-08-24 09:19:02.939241|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
2012-08-24 11:51:38.135232|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead

I replaced my server's wan ip with xxx.xxx.xxx.xxx. (but notice the dot at the end of the string).

Does anyone know why and how this error occurs?

This thread was merged from a moderator

[Ar2rJke]

I still have the same inifile because the answer was not who did not say all that I have written is to edit inifile put ip 0.0.0.0. I tried in the end nothing happened. tried to enter my external IP - all the same. deleted inifile run standard server - all the same. and this is all after version 3.0.6

[maxi1990]

I checked my server's logs and came upon this errors (Serverversion 3.0.6.1):

2012-08-15 13:12:03.620126|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
2012-08-15 17:06:33.972160|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
2012-08-15 22:15:42.601877|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
2012-08-17 11:58:33.268864|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
2012-08-18 14:06:09.585633|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
2012-08-18 15:00:24.536588|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
2012-08-19 17:32:20.847950|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
2012-08-19 20:18:19.486270|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
2012-08-23 09:58:30.604515|ERROR   |ParamParser   |   | Protocol mismatch, old client or old server?
2012-08-23 09:58:52.467043|ERROR   |ParamParser   |   | Protocol mismatch, old client or old server?
2012-08-23 21:26:45.027493|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
2012-08-24 08:19:08.404707|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
2012-08-24 08:49:00.757839|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
2012-08-24 09:19:02.939241|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
2012-08-24 11:51:38.135232|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead

I replaced my server's wan ip with xxx.xxx.xxx.xxx. (but notice the dot at the end of the string).

Does anyone know why and how this error occurs?

This thread was mered from a moderator

Thanks for merging the threads.
However, my server works flawlessly and I did not experience any problems but I still wonder why or how this error appears.
All binding is set to 0.0.0.0 and was never set to anything else.

[Rodax]

Hi, sorry for reactivating the old thread. But I am encountering the same problem with my Ubuntu server. The error message "resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead" continues to appear, although all bindings (voice/query/filetransfer) are set to 0.0.0.0 in the inifile. The external ip xxx.xxx.xxx.xxx isn't mentioned anywhere in my configuration. The .ini is being loaded correctly. It is not a big deal because the server is working properly, but nevertheless it annoys me seeing this error message popping up in the log all the time and being unable to fix it.
Are there any new ideas on how to solve this issue?