So, I was attempting to turn on my server this morning, and I was unable to connect to it even over a LAN connection. I looked at the console, and there were a few messages aftger the server began running saying "Unable to connect to Metrics" and "server returned HTTP Response code : 502 for URL: http://mcstats.org/report/ <Several Plugin Names>" Also it keeps displaying the same as above to http://metrics.griefcraft.com/report/ <Several Plugin Names> This has never happened to me before, and the server was running perfectly last night. Any idea what's causing this error and how to fix it?
I'm having this same error too. It's caused by all plugins that use Metrics, (list here) It's causing us lag on our server...
In the "PluginMetrics" folder, change the config.txt entry to opt-out: true And it will stop the errors, and lag.
Well, I just tried that, and still nothing... I get timed out each time I try to connect to my server. Oh, fixed it. Apparently my power-outage somehow changed my LAN IP. EDIT by Moderator: merged posts, please use the edit button instead of double posting.
That can totally happen when power is lost to a router or something is disconnected for a while due to how something called DHCP works. If you don't want it to happen again, try to find out how to reserve an address in DHCP on your router.
When using a dynamic IP a power lossage can change your server's IP address. Usually when using a static IP this will not happen. However, the only downside is you normally have to pay you ISP to have a static IP.
Actually guys, I have a reserved DHCP spot on all my networked devices, and I have a DynDns static IP. I also haven't had any recent power outages or network resets. The "opt-out" set to true fixes this, whether those aforementioned things are set dynamically or static.
Glad I found this thread. I had no idea that one of the plugins I use used a remote metrics site. When I first saw the 502's popping up the first thing I did was add rules to my firewalls blocking all traffic to the IP and DNS entry. Then I started searching here to find out what was going on. I really think if a plugin is going to use something like this it should be fully disclosed so that admins can allow or deny it with foreknowledge.