Hosting Server My servers are not appearing in the master list, but direct connect works

[TeKilla]

Hi,

Since today afternoon our MBII servers stopped appearing both in the in-game server list and in the web server list.

Until yesterday they were listed normally. No changes were made on our side.

Current behavior:

• Servers are reachable via direct connect (/connect zonafranga.servegame.com)
• Also reachable directly by IP
• Servers are running on IP 178.132.198.235
• Ports: UDP 29070, 29071, 29072, 29073, 29075
• Ports are open and listening
• Heartbeats are being sent correctly

Master servers configured (default MB2):

// Additional master servers to report to
seta sv_master1 "master.moviebattles.org" // Master servers - do not alter unless you know what you are doing.
seta sv_master2 "master2.moviebattles.org"
seta sv_master3 "master.jkhub.org"
seta sv_master4 "masterjk3.ravensoft.com"
seta sv_master5 ""

Other servers still appear normally, so this does not seem to be a global outage.

Is there any recent change, filtering, rate limit, or policy that could cause IP 178.132.198.235 to be blocked or excluded from the master server list?


Thanks.

 

[Defiant]

Nothing has changed on our end. I can see the last successful contact from those servers was at 22:30:12 on the 14/12/2025. I would suggest if you have the relevent access to the box trying to ping and tracert master.moviebattles.org

 

[TeKilla]

I ran a traceroute from the server to master.moviebattles.org and got the output below. Apparently the route leaves the VPS normally, but then stops responding at an intermediate hop with !N.

traceroute to master.moviebattles.org (57.128.182.29), 30 hops max, 60 byte packets
1 gw-core-cotia.as213920.net (178.132.198.1) 1.443 ms 1.437 ms 4.344 ms
2 ae0.10-200G.EDGE.BR-COA1.infra.bb.srv.br (131.196.196.1) 1.165 ms 1.122 ms 1.062 ms
3 edge-cirion-cotia.bbhost.com.br (8.243.61.213) 1.691 ms 1.820 ms 1.645 ms
4 edge-cirion-cotia.bbhost.com.br (8.243.61.213) 1.717 ms !N 2.400 ms !N 2.402 ms !N

I’m not sure if this could indicate some kind of firewall or filtering on my provider’s side, or if this is simply expected behavior for traceroute.

I can also successfully ping to master.moviebattles.org

PING master.moviebattles.org (57.128.182.29) 56(84) bytes of data.
64 bytes from vps-dd7b737e.vps.ovh.net (57.128.182.29): icmp_seq=1 ttl=48 time=185 ms
64 bytes from vps-dd7b737e.vps.ovh.net (57.128.182.29): icmp_seq=2 ttl=48 time=185 ms
64 bytes from vps-dd7b737e.vps.ovh.net (57.128.182.29): icmp_seq=3 ttl=48 time=185 ms
64 bytes from vps-dd7b737e.vps.ovh.net (57.128.182.29): icmp_seq=4 ttl=48 time=184 ms
64 bytes from vps-dd7b737e.vps.ovh.net (57.128.182.29): icmp_seq=5 ttl=48 time=184 ms
64 bytes from vps-dd7b737e.vps.ovh.net (57.128.182.29): icmp_seq=6 ttl=48 time=185 ms

 

[Bully]

Double check if your dedicated cvar is set correctly at startup:
./mbiided.i386 +set dedicated 2

As far as I know the dedicated cvar works as follows:
0 - Just a regular game client with hosting / playing capabilities
1 - Dedicated server but does not send heartbeats to master server lists (not visible in the server browser)
2 - Dedicated server that sends heartbeats to master server lists (visible in the server browser)

 

[TeKilla]

Interestingly, the servers have started appearing in the lists again, without any changes on my side, so it may have been a temporary issue or some delay/cache on the master side.

 

[TeKilla]

Double check if your dedicated cvar is set correctly at startup:
./mbiided.i386 +set dedicated 2

I’m already starting the server with +set dedicated 2.
However, I’m not using mbiided.i386 specifically; I’m using the latest build from GitHub - JACoders/OpenJK: Community effort to maintain and improve Jedi Academy (SP & MP) + Jedi Outcast (SP only) released by Raven Software

 

[Defiant]

Interestingly, the servers have started appearing in the lists again, without any changes on my side, so it may have been a temporary issue or some delay/cache on the master side.

There is no cache on the master side. If there were, it would show out dated data. If you really want to find out, might be worth trying the tracert again and seeing if you get further hops now. Chances are though, it was a temporary outage/routing problem that got sorted and you'll never know where or why.

 

[TeKilla]

I reran the traceroute and it does indeed go further now compared to before, and the servers are visible again in both the in-game and web lists. So it does look like a temporary routing or connectivity issue that resolved itself.

Appreciate the help.

traceroute to master.moviebattles.org (57.128.182.29), 30 hops max, 60 byte packets
1 gw-core-cotia.as213920.net (178.132.198.1) 7.736 ms 7.689 ms 7.678 ms
2 ae0.10-200G.EDGE.BR-COA1.infra.bb.srv.br (131.196.196.1) 1.027 ms 1.026 ms 0.974 ms
3 170.238.234.154 (170.238.234.154) 2.385 ms 2.618 ms 2.610 ms
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 was1-vin1-vac1-a75-1-firewall.wa.us (178.32.135.117) 131.679 ms 131.582 ms 131.945 ms
10 was1-vin1-vac1-a75-3.wa.us (178.32.135.114) 131.429 ms 131.419 ms 131.374 ms
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 be101.lon1-eri1-g2-nc5.uk.eu (91.121.215.119) 232.748 ms 234.457 ms
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *