Teeworlds - general

Teeworlds

discord.gg/teeworlds / general

Teeworlds Discord Server.

Between 2020-01-01 00:00:00Z and 2020-01-02 00:00:00Z

Master servers down or something? I see all servers down on 0.7 and no servers on 0.6

01:04

Forget it, my side problem

HAG joined the server. 2020-01-01 01:04:52Z

zokker13 joined the server. 2020-01-01 12:39:08Z

good day fellow people and happy new year

12:45

I wonder here if somebody encountered some challenges with docker networking and connectivity to the teeworlds master servers? It's possible to have my server open in the wild and connect to it but the registration to the masterserver somehow fails, claiming I need to open ports/configure my firewall for UDP and port 8000. It's the same port I used to connect to the server so I'm a bit puzzled.

@zokker13 hello fellow tee. So you use a custom port for your server

Happy new year people!

6

@Dune yessir. I changed it to external: 8000 and internal 6000. Using the sv_port 6000 and sv_external_port 8000 didn't help. I have everything setup in a docker swarm infrastructure and my network is overlay. That might causes some issues because it's doing some NATting behind the scenes..

https://www.teeworlds.com/?page=docs&wiki=server_settings that's all the engine settings we got

15:38

I never tried to set up a different external and internal port myself, can't help you much

I also had it on the sdame port

15:38

both 8000

15:38

but that didnt help either

15:38

it's a bit weird

15:39

is the master server open source?

Yes

okay I'll have a look there

https://github.com/teeworlds/teeworlds/tree/master/src/mastersrv

but could also be that UDP and docker is weird together with overlay networks

15:39

ty

if you can connect on it on :8000 from another network then the port should be open :/

I can't really understand the issue

15:41

I casn connect to the server

15:41

it's just the masterserver and public listing causing issues

but it is not listed in the masterservers

might be a bug there

There's always the off chance the masterservers blacklisted you, but that shouldn't be your case

15:42

@heinrich5991 is more knowledgeable, maybe he's around

mh..

15:43

why would it blacklist me?

15:43

I got a static IP

being in the IP range of ddosers I imagine, but that is unlikely

15:44

TCP & UDP open?

only udp (edited)

15:44

I need both? (edited)

only udp is fine

no

15:45

perhaps I need tcp for the masterserver

no

mh..

so you can continue to your server on port 8000?

15:46

what does the server tell you about the masters?

15:46

are we talking about a 0.6 or a 0.7 server?

0.6

15:48

The log ist spammed with "the master server reports that clients can no connect to it" <-- a lie

15:48

and: "configure yout firwall/nat to let through udp on port 6000" <-- should be 8000, I guess it's takling the wrong config element

what is your config sv_port, sv_external_port?

https://github.com/teeworlds/teeworlds/blob/27c6f8ae4600308248cdbc8a5edcc16ae142950e/src/engine/server/register.cpp#L277

15:51

it uses sv_port

nice catch

what port is your server listening on, what port mapping do you do between docker and the internet

8000 is external (so sv_external_port) and 6000 internal (sv_port)

is it running right now? what is its IP address?

yes, 37.221.199.214

how are you starting docker? ... -p 6000:8000/udp ... ?

I'm using docker swarm for it

15:55

since it's my entire infrstaructure

15:56

but the port is forwarded if that's what you are asking

does the registration work without docker?

I didnt try that

have you tried to remove the sv_external_port line? i never had problems with that (even with dslite)

yup, I also tried using the same internal and external port without that option

I can connect.

yes yes

15:59

connection is fine

is sv_register 1?

bhut I want other people to connect

it should be by default

yep @a28b

the last thing that's missing is whether it works without docker

15:59

it might simply be the fault of the masters

15:59

they're under constant attack AFAIK

argh

maybe try with a 0.7 server

mh..

just to test

I can try that

or try without docker

yes, sec

okay getting the same message when running on the host itself

16:09

but I cant connect this time

@zokker13 maybe you have malware on your pc? Using some untrustworthy teeworlds clients? Or worse?

unlikely

16:13

wait

16:13

you can't connect. huh?

probably some iptables issue

@heinrich5991 yes unlikely, i didn't finish reading

so now im connected

16:17

lets see what the master server says..

16:17

registered

16:19

mh... it says it's registered but cant find it yet

did it select the same master?

it constantly changes

16:20

actuaslly says the master server is not responding

16:20

thats weird

if it says it's registered it isn't a server issue anymore

I dont think the "registered" message is trustworthy if the servers are changed all the time and telling me its not responding

they are sending heartbeats

if it's "registered" then at that point it's not the fault of the server anymore

16:22

but the master server's

ip and tw version?

they were mentioned

37.221.199.214 and 0.6 for server

thx

happy new year

Yea thats the 0.6 issue everyone has, @zokker13 masterservers are bugged and getting ddos so the servers wont show up (edited)

ohh damn

It may or may not fix itself in some days or weeks, but you are better off opening a 0.7 server instead, 0.7 servers will show up @zokker13 (edited)

I see

17:19

thanks mate

Oh

19:35

Looks like 0.6 server list is working again :D 390+ servers and 481 players

TeriyakiChicken joined the server. 2020-01-01 19:43:35Z

Damn thats around 700 players online now if you combine 0.7

19:59

most I saw in a while lol

nice !

Well it's holidays :)

Gamer joined the server. 2020-01-01 23:05:16Z

fireball joined the server. 2020-01-01 23:28:35Z

Exported 121 message(s)