Hosting Server Problem with master server

[Pierry]

Hi there,

for the last few hours, I've been trying to figure out why my server isn't showing up on the server list or servers.moviebattles.org.

The server is listed on jkhub's master just fine. Also I found out that whenever I try to ping the master.moviebattles.org with the server, it gets no response.
Already looked into firewall configuration, etc.
Is it possible that the server is somehow blocked by the master?

Specs:
IP: 165.22.89.90:29070 running on linux Ubuntu 16.04.6 x32

Thanks

EDIT: Just noticed the IP was wrong, sorry about that.

 

[[SE] Maren]

Probably something to do with your gayass Linux

 

[Puppytine]

Are you sure it's listed on jkhub?
I can't manually connect it (infinite awaiting connection), though I can ping it and trace it.
My IP is 77.51.145.86, though it's dynamically allocated and will be changed once I restart a router.
Could you please trace and ping master.moviebattles.org from the machine where your server is running, and post the results here?

 

[Pierry]

Are you sure it's listed on jkhub?
I can't manually connect it (infinite awaiting connection), though I can ping it and trace it.
My IP is 77.51.145.86, though it's dynamically allocated and will be changed once I restart a router.
Could you please trace and ping master.moviebattles.org from the machine where your server is running, and post the results here?

Yeah, even now can I see it on the jkhub server list.
Are you sure you got the port right? I can connect to it just fine.
EDIT: For some reason the IP was wrong, edited OP.

Anyways, pinging looks like this:

~# ping master.moviebattles.org
PING master.moviebattles.org (74.91.126.145) 56(84) bytes of data.

--- master.moviebattles.org ping statistics ---
20 packets transmitted, 0 received, 100% packet loss, time 20000ms

and traceroute:

~# traceroute -4 master.moviebattles.org
traceroute to master.moviebattles.org (74.91.126.145), 30 hops max, 60 byte pack ets
1 165.22.80.254 (165.22.80.254) 3.338 ms 165.22.80.253 (165.22.80.253) 3.872 ms 3.868 ms
2 138.197.250.174 (138.197.250.174) 3.535 ms 3.531 ms 138.197.250.168 (138.1 97.250.168) 4.714 ms
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

 

[Puppytine]

Are you sure you got the port right? I can connect to it just fine.

I directly copy-pasted IP and port from your message, it didn't work for me either first time and now too.

and traceroute:

The packets didn't go too far, it seems that the problem is on your side.
Maybe DDoS protection is too strict.
Something stops 77.51.145.86 from connecting port 29070 of 165.25.80.90, as well as it stops 165.25.80.90 from pinging and tracing 74.91.126.145.
Contact your hoster.

 

[Pierry]

I directly copy-pasted IP and port from your message, it didn't work for me either first time and now too.

The packets didn't go too far, it seems that the problem is on your side.
Maybe DDoS protection is too strict.
Something stops 77.51.145.86 from connecting port 29070 of 165.25.80.90, as well as it stops 165.25.80.90 from pinging and tracing 74.91.126.145.
Contact your hoster.

Yeah sorry about that. The OP now contains the correct address.
It does look like a server side issue, although I'm not sure as to what really causes it.
Oh well, guess I'll have to fall down the rabbit hole again on this one.

Thanks for the assistance.

 

[Puppytine]

The OP now contains the correct address.

Now when you corrected the address, I can connect your server, I can ping it and trace it.
You still have to find out why can't you trace master.moviebattles.org, though.

 

[Spaghetti]

I ran a trace from the server and it looks like it's dying when it gets to Digital Ocean's network.

traceroute to 165.22.89.90 (165.22.89.90), 30 hops max, 60 byte packets
 1  internal.e4.router.dallas.nfoservers.com (74.91.126.254)  0.368 ms  0.347 ms  0.320 ms
 2  border6.lt-0-0-0-9.nuclearfallout-63.dal006.pnap.net (107.150.141.1)  1.611 ms  1.596 ms  1.623 ms
 3  core3.pc1-bbnet1.ext1a.dal.pnap.net (216.52.191.41)  2.713 ms core3.pc2-bbnet2.ext1a.dal.pnap.net (216.52.191.106)  2.591 ms core3.pc1-bbnet1.ext1a.dal.pnap.net (216.52.191.41)  2.802 ms
 4  dls-bb1-link.telia.net (213.248.73.193)  2.228 ms  2.307 ms  2.201 ms
 5  atl-b22-link.telia.net (80.91.246.74)  20.192 ms  20.445 ms  20.127 ms
 6  ash-bb4-link.telia.net (62.115.125.129)  37.117 ms  36.924 ms  36.760 ms
 7  prs-bb3-link.telia.net (62.115.112.243)  134.584 ms  136.344 ms prs-bb4-link.telia.net (62.115.122.158)  110.526 ms
 8  ffm-bb3-link.telia.net (62.115.123.12)  143.046 ms ffm-bb4-link.telia.net (62.115.114.99)  118.276 ms  117.787 ms
 9  ffm-b4-link.telia.net (62.115.120.0)  134.163 ms  131.633 ms  134.148 ms
10  * * *

Digging a bit more, it seems as though Digital Ocean is blocking the master server's IP generally (given how your traceroute is dying so fast). Tried some of their diagnostic IPs for speed tests and got nothing.

 

[Pierry]

I ran a trace from the server and it looks like it's dying when it gets to Digital Ocean's network.

traceroute to 165.22.89.90 (165.22.89.90), 30 hops max, 60 byte packets
 1  internal.e4.router.dallas.nfoservers.com (74.91.126.254)  0.368 ms  0.347 ms  0.320 ms
 2  border6.lt-0-0-0-9.nuclearfallout-63.dal006.pnap.net (107.150.141.1)  1.611 ms  1.596 ms  1.623 ms
 3  core3.pc1-bbnet1.ext1a.dal.pnap.net (216.52.191.41)  2.713 ms core3.pc2-bbnet2.ext1a.dal.pnap.net (216.52.191.106)  2.591 ms core3.pc1-bbnet1.ext1a.dal.pnap.net (216.52.191.41)  2.802 ms
 4  dls-bb1-link.telia.net (213.248.73.193)  2.228 ms  2.307 ms  2.201 ms
 5  atl-b22-link.telia.net (80.91.246.74)  20.192 ms  20.445 ms  20.127 ms
 6  ash-bb4-link.telia.net (62.115.125.129)  37.117 ms  36.924 ms  36.760 ms
 7  prs-bb3-link.telia.net (62.115.112.243)  134.584 ms  136.344 ms prs-bb4-link.telia.net (62.115.122.158)  110.526 ms
 8  ffm-bb3-link.telia.net (62.115.123.12)  143.046 ms ffm-bb4-link.telia.net (62.115.114.99)  118.276 ms  117.787 ms
 9  ffm-b4-link.telia.net (62.115.120.0)  134.163 ms  131.633 ms  134.148 ms
10  * * *

Digging a bit more, it seems as though Digital Ocean is blocking the master server's IP generally (given how your traceroute is dying so fast). Tried some of their diagnostic IPs for speed tests and got nothing.

Well damn. That's what I initially thought, too bad it proved to be true.

Thanks for checking on it, you saved me a lot of time.
It's time to confront DO support now.

 

[Pierry]

Things just got a tad more interesting now.
This is the response I received from the DO support:

It looks like the destination IP 74.91.126.145 is not reachable. I suspect ICMP traffic might have been blocked and also i get connection timed out when i open the website master.moviebattles.org. So its definitely an issue with the server where master.moviebattles.org is hosted. Considering the droplet infrastructure settings, i can assure you that we haven't blocked the IP addresses.

Are you sure that NFO servers are not blocking DO?

 

[Spaghetti]

The server isn't running anything web related so a browser test is pointless, and we both know ICMP isn't being blocked generally.

I don't suspect NFO since the trace shouldn't leave their network if the destination IP is being blocked outbound. Definitely not the case. If they are blocking it inbound, that does not explain your traceroute (guessing it doesn't leave DO's network there since it stops after 2 hops).

It's possible the block is at Telia's network (since that seems to be how things are routed on my trace). I'm not well informed on peering arrangements and whether a business like NFO could request blocking of an IP range upstream directly or indirectly through their partners before it gets anywhere near their network.

 

[Pierry]

The server isn't running anything web related so a browser test is pointless, and we both know ICMP isn't being blocked generally.

I don't suspect NFO since the trace shouldn't leave their network if the destination IP is being blocked outbound. Definitely not the case. If they are blocking it inbound, that does not explain your traceroute (guessing it doesn't leave DO's network there since it stops after 2 hops).

It's possible the block is at Telia's network (since that seems to be how things are routed on my trace). I'm not well informed on peering arrangements and whether a business like NFO could request blocking of an IP range upstream directly or indirectly through their partners before it gets anywhere near their network.

Yeah, checking the server through a browser has also confused me. I've never indicated that this was a web site.
Nevertheless I'll keep in contact with the support. Already made it clear for them, so we'll see what happens.
Honestly I never anticipated such a problem would even be possible. I mean why would any of the sides block the connection?

 

[Spaghetti]

Yeah, checking the server through a browser has also confused me. I've never indicated that this was a web site.
Nevertheless I'll keep in contact with the support. Already made it clear for them, so we'll see what happens.
Honestly I never anticipated such a problem would even be possible. I mean why would any of the sides block the connection?

Could be prior spam or abuse from one side or the other, or an overly aggressive IP range ban for something unrelated.