DDraceNetwork

I have a feeling this is a bug, I'm stuck

even with gravity this low, barring maybe a rounding error, we never should be stuck like that

sounds like a: wont fix till ddnet 2.0

Learath2

I have a feeling this is a bug, I'm stuck

i've already seen that, usually a third tee bumping in allows unstucking

Hey i know i asked this already some time ago ...but maybe you have some new information. My Server on 16.2.2 - 18.0.3 dont get registered. It only works on 16.1 or older. Anyone an idea for a fix? (8303 is open on my firewall + router (otherwise 16.1 wouldnt work either obviously))

Zonsa

Hey i know i asked this already some time ago ...but maybe you have some new information. My Server on 16.2.2 - 18.0.3 dont get registered. It only works on 16.1 or older. Anyone an idea for a fix? (8303 is open on my firewall + router (otherwise 16.1 wouldnt work either obviously))

but can u manually connect via ip in F1 -> connect <ip> ?

öh didnt try yet. Let me take a look

16.2 is the introduction of the https master

19:08

likely an interaction with that

Jupstar ✪

but can u manually connect via ip in F1 -> connect <ip> ?

Yep works

heinrich5991

likely an interaction with that

Anything i can do?

do you get any errors in the console for the newer versions?

ye

19:09

wait i can send

ah, and can you DM me your IP address so I can try connecting?

2024-03-02 20:10:02 I server: starting... 2024-03-02 20:10:02 I server: using port 8303 2024-03-02 20:10:02 I server: server name is 'My DDNet server' 2024-03-02 20:10:02 I git-revision: 75934e16aa4eea3a1f93f3876b6cbc42bd689c54 2024-03-02 20:10:02 I server: version 18.0.3 on win64-steam amd64 2024-03-02 20:10:02 I server: git revision hash: 75934e16aa4eea3a1f93f3876b6cbc42bd689c54 2024-03-02 20:10:02 I register/6/ipv6: registering... 2024-03-02 20:10:02 I register/6/ipv4: registering... 2024-03-02 20:10:02 I sql: [2] load best time done on read database 0 2024-03-02 20:10:18 I register/6/ipv6: registering... 2024-03-02 20:10:18 I register/6/ipv4: registering... 2024-03-02 20:10:18 E register/6/ipv6: ERROR: the master server reports that clients can not connect to this server. 2024-03-02 20:10:18 E register/6/ipv6: ERROR: configure your firewall/nat to let through udp on port 8303. 2024-03-02 20:10:18 E register/6/ipv4: ERROR: the master server reports that clients can not connect to this server. 2024-03-02 20:10:18 E register/6/ipv4: ERROR: configure your firewall/nat to let through udp on port 8303.

I can't connect to the server with your global IP address @Zonsa

19:12

seems like the port forwarding doesn't work

19:12

we can check if I can connect with 16.1, yes

19:13

tell me when you have started the 16.1 server @Zonsa

its on

19:13

[2024-03-02 20:13:29][register]: no firewall/nat problems detected [2024-03-02 20:13:29][register]: server registered

yea, can't connect, still

can you try with my private ip?

I'll try, but I can guarantee it won't work

19:14

does not work either

Or just look for Zonsa in the Internet tab

19:14

;__;

I'll look for zonsa

19:15

aha! I see that

19:15

it seems it's not correctly forwarded for port 8303

wtf XD

because it's port 5591 for me

19:15

(but with your public IP address)

ah okay

this is the following bug: https://github.com/ddnet/ddnet/issues/5593

Masterserver registration does not work if the NAT remaps the port ...

As Tezcan reported on Discord, if a DDNet server is reachable via a different port than it listens on (e.g. because a NAT remaps the port to some other port), the new masterserver registration fail...