WARNING: could not connect

[dust]

Same issue here, slots OK unless they just changed the maximum. Guess it's not on our end.

tried with 10 and 12 slots.

I also tried from different boxes with different configs (NAT and non NAT). Same error.

With the default -m not specified in command line I am getting:

[SELECT ALL] Code:

looking up ms.cubers.net:28760...
WARNING: could not connect

When "enforcing" -massault.cubers.net (supposedly default according to doc but does not seem to be in fact) I get:

[SELECT ALL] Code:

looking up assault.cubers.net:28760...
WARNING: could not connect

EDIT:

It must be master server refusing server registration (firewall rule dropping IPs?) as I just tried to change the --masterport to 80 ( --masterport=80 ) and the error is then different:

[SELECT ALL] Code:

looking up ms.cubers.net:80...
WARNING: master server registration failed:

EDIT 2 / users reporting similar issues:
http://forum.cubers.net/thread-7583-post...#pid149322
http://forum.cubers.net/thread-7586.html
http://forum.cubers.net/thread-7585.html