[SPIGOT-1219] CraftBukkit and Spigot do not respond to status or ping requests Created: 02/Oct/15 Updated: 03/Oct/15 Resolved: 03/Oct/15 |
|
| Status: | Resolved |
| Project: | Spigot |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Andrew Shulman | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | Craftbukkit, Spigot, bug | ||
| Environment: |
Vanilla: 1.8.8 |
||
| Description |
|
I noticed with my running server that Dinnerbone's Minecraft Server Status Checker reports that "Unfortunately, we were unable to contact this server." Curious, I downloaded the source for his tool and tried it myself – same result. Thinking it might be a configuration issue, I created a brand new server and tried that, but it was still unpingable. I then realized I was using an old-ish version of Spigot, so I rebuilt from source, but it still didn't work. I downloaded the vanilla MC server, started it up, and the tool was able to talk to it just fine. I tried the CraftBukkit jar that BuildTools creates, but that also did not respond. |
| Comments |
| Comment by Andrew Shulman [ 03/Oct/15 ] |
|
@md_5, I don't believe this is fixed. Your change made it so I am able to use the "ping" command against the server successfully. However, the website still shows a brand new server as offline, and a "status" command from the Python library raises the error "Server did not respond with any information!". |
| Comment by Andrew Shulman [ 02/Oct/15 ] |
|
I did not enable query. From Dinnerbone's documentation: "mcstatus provides an easy way to query Minecraft servers for any information they can expose. It provides three modes of access (query, status and ping), the differences of which are listed below..." Given I did not enable query, I would not expect query to work. However, status and ping do not work either. |
| Comment by Shevchik [ 02/Oct/15 ] |
|
Are use sure that you enabled query? |
| Comment by Andrew Shulman [ 02/Oct/15 ] |
|
In general, I would tend to agree with you which is why I've checked this repeatedly with brand new server folders. I've checked this on both my personal Windows machine and my Linux server box, and I even checked them using 127.0.0.1 instead of their public-facing IP addresses to avoid any firewall shenanigans. If this is a configuration issue, I'll be damned if I can figure out what it is. |
| Comment by Black Hole [ 02/Oct/15 ] |
|
This is some kind of configuration issue on your side. Maybe your firewall or DNS settings? |