up vote 5 down vote favorite

I just re-purchased Minecraft (because my old profile stopped working so I bought it) after not playing it for a couple of months. I've added a bunch of servers, but almost every one says "can not connect."

I know its not because the server is not 1.7.2, because I checked that they'd update. It will say "server can't connect" after a long time. I don't know if its me or the servers.

My server screen looks like this (notice the one at the bottom – it's still loading!):

Server Screen Screenshot

share|improve this question
  • 9
    Run-on sentences are bad because it makes it hard to understand them and it's less likely that someone will answer your question when that question is hard to understand and if you don't get an answer because people don't understand your question you'll be disappointed and you might not come back to the site if your first experience with it is disappointment so please use punctuation and don't write run-on sentences. – MBraedley Nov 8 '13 at 2:01
  • 3
    I can't help but notice at least one of those servers explicity says 1.6.4 – Ender Nov 8 '13 at 2:15
  • @MBraedley run-on much? – TheXed Nov 9 '13 at 18:23
  • @TheX take a look at the revision history. I was using satire to make a point. – MBraedley Nov 10 '13 at 2:01
  • @MBraedley I know, I was just pointing out the irony... – TheXed Nov 12 '13 at 15:06
up vote 1 down vote

If you are using Windows, search 'Firewall' and go into 'Windows Firewall with Advanced Security'. On the left click 'Outbound Rules' and right click to create a new rule. Make the rule for a port, which is '25565' and do this twice, once for UDP and once for TCP. This should allow outgoing connections to servers with the default Minecraft port that may not be currently connecting because of your firewall.

share|improve this answer
  • 1
    Pretty sure Windows Firewall would never block those connections by default. – kotekzot Nov 26 '13 at 11:05
up vote 0 down vote

I was just experiencing this issue with my local server, these errors are popping up because the owners of the servers have not looked into the new eula and changed the text to "true". With 1.8 launching, Mojang has made a required eula that each server must agree to in order for the server to come online.

share|improve this answer
  • I just realized this question was from 10 months ago, but is being linked to for questions from today.. interestingly I think these are separate questions with the same issue. My answer should work for current issues with 1.8. – stay Sep 6 '14 at 10:33

protected by Community♦ Dec 9 '13 at 22:34

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged or ask your own question.