Related

Tool [NEW] Bandwidth Pricing Calculator Tool
Is possible to connect a DO K8s cluster with a DO Droplet private network? Question Question
Are there free accounts for non-profits? Question Question

Question

Minecraft - Connecting to my server takes a long time

Posted October 20, 2019 1.7k views
NetworkingJava

I have a 3GB droplet with a minecraft server. connecting to it through minecraft takes ~10-15 seconds compared to ~1-3 seconds for every other server. Once I’m connected, it runs great but the long connect time makes players think the server doesn’t exist. How do i fix this?
If you would like to try, the IP is 157.230.202.26

Add a comment
18odegardl
By:
18odegardl
Add a comment
1 comment
  • ForYourIT October 20, 2019
    Reply Report

    Probably some issue with either

    • Your network configuration (open ports, anti-attack services etc.)
    • Your resource limit
    • Any other service

    We can’t figure out where this comes from without logs, configurations etc.
    I don’t have that magic yet ;)

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
1 answer
techflow October 24, 2019

Hello, @18odegardl

To add more on this.

Could you please let me know if you were able to replicate the issue when testing from different ISPs?

What you can do is to perform a traceroute to your server and see if there is a packet loss on some of the hops, as this will help you to determinate if there is a networking issue. Keep in mind that a lot of ISPs will block ICMP requests and those are used from traceoute so if there is packet loss this doesn’t mean that there is a “real” issue as the requests made by your traceroute command can be blocked intentionally.

I’ve performed a mtr (my traceroute) for a short period of time and I can see that there is a packet loss on this IP - 129.250.6.203 which seems to be associated with NTT America INC, You can see the copy of my traceroute:


 3. 83.217.227.49                                                                                                                                            0.0%   390    6.6   5.1   3.0  11.2   1.2

 4. ae-3.r24.frnkge08.de.bb.gin.ntt.net                                                                                                                                  0.0%   390   30.1  29.7  26.9  57.2   2.5
 5. ae-3.r24.frnkge08.de.bb.gin.ntt.net                                                                                                                                 74.1%   390   29.5  51.1  27.4 166.6  37.9
    ae-11.r21.nwrknj03.us.bb.gin.ntt.net
 6. ae-11.r01.nycmny17.us.bb.gin.ntt.net                                                                                                                                 0.0%   390  120.9 120.5 118.1 125.2   1.1
 7. ce-0-13-0-2.r01.nycmny17.us.ce.gin.ntt.net                                                                                                                           0.0%   390  120.0 121.0 118.3 157.5   3.7
 8. ???
 9. ???
10. ???
11. 157.230.202.26                                                                                                                                                       0.0%   389  129.3 128.7 126.5 140.6   1.2

You can check if your traffic goes through this IP address as well and check for any packet loss.

Let me know how it goes.

Reply Report
Submit an Answer

Related

Looking for something else?

Ask a new question Search for more help