So - I'm the head admin of SpecialAttack.net Freebuild (and SMP), a server that has been up since April.
After the Minecraft.net server switch it seems to be getting delisted - like, it appears on the server list for like 5 minutes then disappears and players can't connect - their accounts are not being verified either, from what I see in the logs.
I just want to know if ANYBODY knows anything about this - I am fully familiar with all the server-administrative stuff, so I'm 110% sure our config is correct - heck, it didn't change and reverted to older revisions too (we're running fCraft - just like i.e. Team9000.net, which is merrily sitting on the server list) - not to mention flushed DNS caches everywhere I could, double-tested with our machine's second IP, various ports and so on.
Is there any possibility this could come through to Notch and he could check what is wrong? i.e. I strongly suspect it could be the DDoS protection mass-blacklisting IPs since I know that our ISP, Leaseweb, ended up on a public blacklist once for some reason.
Our IPs are 85.17.60.103 (the one Freebuild is running off) and 85.17.102.2 - our tech admin checked the IPs and they don't figure on any public blacklist, though I don't know what Notch is using on the new server.
War does not determine who is right - only who is left. - Bertrand Russell fCraft.net Freebuild Official - Official server of the fCraft custom server software
Solved the problem. Apparently Notch changed the heartbeat handler without telling anyone - it now requires people to read all responses till the end, while fCraft was reading only the first one to save bandwidth.
War does not determine who is right - only who is left. - Bertrand Russell fCraft.net Freebuild Official - Official server of the fCraft custom server software
Lim-Dul, I am running v0.494 r297, and using the fCraft.dll you provided actually prevents fCraftUI, fCraftConsole, and the ConfigTool from even starting.
However, using this one from the latest revision (r298) seems to have fixed the heartbeat issue on my end.
After the Minecraft.net server switch it seems to be getting delisted - like, it appears on the server list for like 5 minutes then disappears and players can't connect - their accounts are not being verified either, from what I see in the logs.
I just want to know if ANYBODY knows anything about this - I am fully familiar with all the server-administrative stuff, so I'm 110% sure our config is correct - heck, it didn't change and reverted to older revisions too (we're running fCraft - just like i.e. Team9000.net, which is merrily sitting on the server list) - not to mention flushed DNS caches everywhere I could, double-tested with our machine's second IP, various ports and so on.
Is there any possibility this could come through to Notch and he could check what is wrong? i.e. I strongly suspect it could be the DDoS protection mass-blacklisting IPs since I know that our ISP, Leaseweb, ended up on a public blacklist once for some reason.
Our IPs are 85.17.60.103 (the one Freebuild is running off) and 85.17.102.2 - our tech admin checked the IPs and they don't figure on any public blacklist, though I don't know what Notch is using on the new server.
Our play URL is http://www.minecraft.net/play.jsp?serve ... fd7250b459
fCraft.net Freebuild Official - Official server of the fCraft custom server software
Here's a fixed fcraft.dll:
http://www.mediafire.com/?2wrebxdt7l6pt3a
fCraft.net Freebuild Official - Official server of the fCraft custom server software
However, using this one from the latest revision (r298) seems to have fixed the heartbeat issue on my end.