Server Problems, Post Here!

Discussion in 'Empire Help & Support' started by chickeneer, Nov 3, 2014.

  1. tried to join without mods, no difference.
    rebooting the router, same.
    I get dropped after less than a minute of joining the server.
    My SO keeps being able to play normally, despite being on my same internet connection :confused::confused:
    607 likes this.
  2. I've been able to stay online for the last 20 minutes, but the lag is intense. Fluctuating wildly, and everything is teleporting around.
  3. Today, same thing. Takes 3+ minutes to connect to SMP3, and then I instantly get disconnected. My internet is perfectly fine.

  4. But the servers are in the US. I can't pretend to know how the pipes of the internet work. It is worth noting that the only two people that had the issue are both in Europe.
    With that being said, I'll ask around to see what can be done.
    607 likes this.
  5. It was just smp1 for me but my ping would go upwards of 700 on it Utopia was better would only go up to 150ish

    I'm in the good ol US of A
  6. In Germany even.

    Anyway, I ran a few times traceroute, and I always hit a snag once I reach 216.66.0.214, the hop just before the server:

    Code:
     6    37 ms    16 ms    16 ms  port-channel9.core3.fra1.he.net [184.104.231.45]
     7    *        *        *    Request timed out.
     8    32 ms    27 ms    27 ms  100ge0-36.core2.par3.he.net [184.105.81.166]
     9    94 ms    *        *    100ge0-33.core1.orf2.he.net [184.104.197.78]
    10    *      115 ms    *    port-channel13.core2.atl1.he.net [184.105.80.162]
    11  122 ms  120 ms  122 ms  100ge0-35.core2.tpa1.he.net [184.105.223.234]
    12  162 ms  176 ms  165 ms  216.66.0.214
    13    *        *        *    Request timed out.
    14    *        *        *    Request timed out.
    15    *        *        *    Request timed out.
    16    *        *        *    Request timed out.
    17    *        *        *    Request timed out.
    18    *        *        *    Request timed out.
    19  167 ms    *        *    game3.emc.gs [162.252.83.26]
    20  167 ms    *        *    game3.emc.gs [162.252.83.26]
    21  168 ms  163 ms  167 ms  game3.emc.gs [162.252.83.26]
    Code:
     6    12 ms    14 ms    15 ms  port-channel9.core3.fra1.he.net [184.104.231.45]
     7    *        *        *    Request timed out.
     8    28 ms    29 ms    *    100ge0-36.core2.par3.he.net [184.105.81.166]
     9    *        *        *    Request timed out.
    10    *        *        *    Request timed out.
    11  134 ms  125 ms  120 ms  100ge0-35.core2.tpa1.he.net [184.105.223.234]
    12  160 ms    *        *    216.66.0.214
    13    *        *        *    Request timed out.
    14    *        *        *    Request timed out.
    15    *        *        *    Request timed out.
    16    *        *        *    Request timed out.
    17    *        *        *    Request timed out.
    18    *        *        *    Request timed out.
    19  166 ms    *      166 ms  game3.emc.gs [162.252.83.26]
    UltiPig and 607 like this.
  7. Keep getting : Java.net.Socket.Exception: Connection reset. This has been happening since yesterday.
  8. Wow. The connection issues are hitting a bunch of us in game the last hour or so.
    Seems to be lagging out or just connection reset.

    Also getting intermittent Mojang "couldn't connect to our services" issues
  9. I'm not logged in, but my tracert has the same behaviour as the other day.
  10. It's happening again: very laggy, dropped connections, and same tracert symptom
  11. Again problem with "Java.net.Socket.expeption".
  12. Note: we are aware of smp5 being down at the moment. We will bring it up. The server's upgrade to 1.19.2 will also be imminent in the next day or two.
    607, ThaKloned, UltiPig and 3 others like this.
  13. Keep getting the "Kicked whilst joining: You're using the wrong client version!" error. Has something changed? This is the same version I have been using for weeks up to even last night. Tried 1.19.1 & 1.19.2.
    We3_MPO, Cervuz and Merek_Shadower like this.
  14. Having the same issues
    We3_MPO likes this.
  15. Overnight update went funky. We'll get it fixed when possible.

    Edit: to clarify right now you can connect only with 1.19. After we fix it, it will be only 1.19.1/1.19.2.
    I'll make an update post this afternoon with what changed.
  16. Same. I dropped back to 1.19 and was able to connect.
    We3_MPO likes this.
  17. Ok thanks, I'll use that version.
    We3_MPO likes this.
  18. I hope I am safe to assume that this unexpected need to update won't spark a waste reset.
    We3_MPO and KatydidBuild like this.
  19. Nope. That would be announced ahead of time
    We3_MPO, Dreacon78 and ThaKloned like this.
  20. I can't seem to connect with any version right now. Any advice?