First, admittedly my FTB server is running MCPC+, however I don't believe it's the issue.

Whenever I randomly look at my server's status on a forum signature, or my website itself, it usually shows as "Dead". This is giving me a lot of "false" downtime reported.

To correct this I have to manually come to the Gametracker website, click the "claim server" button, and then manually scan for the server. The scan always goes through and my server again shows as online, with all data (server name, players, etc.) showing perfectly normal. That said, 30 minutes later it'll be showing as "Dead" again. It seems that GameTracker can't scan my server when it's left to do it on it's own, but when I manually click to scan my server it never fails. I don't get it.

As I said, I don't think it's the fault of MCPC+ because logging in to GameTracker and clicking the manual scan works fine and gets all the proper information from my server.

I was able to grab a screenshot of the server in it's "dead" status, and the manual update succeeding. I didn't have to change the port number or anything. I just hit the update button. Why can't GameTracker succeed on it's own?

This type of issue is typically due to some sort of anti-flood mechanism on the server. Basically, it may see subsequent scans as "flooding" and temporarily block them.

burn wrote:
This type of issue is typically due to some sort of anti-flood mechanism on the server. Basically, it may see subsequent scans as "flooding" and temporarily block them.


Hmmm, well I don't think I have any anti-flooding mods installed but I'll check over the config files again.

I've checked the server, there is no anti-flood system in place at the moment. Still can't figure out why the auto-scan won't work when the manual one does.

I just tried to scan your server twice, with the second scan receiving no response.

Anti-flood measures are typically within the server firewall software. I am not aware of Minecraft mods that would do that.

It may help to whitelist the GT scanner IPs in your server firewall:

208.167.241.190
208.167.241.185
208.167.241.186
108.61.78.147
108.61.78.148
108.61.78.149
108.61.78.150

I will have to take a look, considering I don't believe I'm running any firewall software on the server itself. I find it makes things easier when I'm working on my internal network... I may have to look into my router to see if it's causing the issue. As far as I know it shouldn't be stopping anything through both TCP and UDP traffic on the scanning port.

Well, there was no firewall on the server, the firewall on the router was also disabled, and the ports were forwarded. Frankly, the server had absolutely no security what so ever. Not that I really care, there's nothing on it worth protecting...

Changed it so the firewall (Windows) on the server is active, with the proper ports open for both the minecraft server and the scanning server. Both UDP and TCP. Then set the server in the DMZ of the router which, in theory, should make it bypass any kind of security the router has built in.

Have to wait to see if it makes a difference though.