Frustration (Connection refused)

[iiredfox]

Hi,

I'm using Pterodactyl panel and all i know is if you allocate a port and bind it to a server it will open the port,
The developer made a plugin that Sends a list of the participating clans to the clan war server (from survival server) and used these ports: 25580, 25581 and still closed. even though tried it with external ip.
Bind it to a server and still says connection refuse. Also, we're not using MySQL for this.

Here's the code for the plugin that we're using to connect: https://hastebin.com/ozehiwixet.cs
It has all the documentation that explains the issue.
Error: https://paste.md-5.net/qehecihiya.avrasm

Contacted with Pterodactyl support but they couldn't help me since some of them not familiar with Minecraft, I'm using Bungee and bungee has the external IP and the rest has a local ip.

Any thoughts? Any idea of how to fix this?

 

[O-T]

First of all, let me clear this up: 127.0.0.1 is localhost, yes, but 0.0.0.0 is not localhost, at all. 0.0.0.0 means bind to all interfaces, and so to all IPs, so if you have IP A and IP B and IP C assigned to that server, 0.0.0.0 will basically tell the application that all IPs A, B and C have to be listened to and so the app will be accessible from these three IPs. While if you were to tell the app to listen to IP A only then the app wouldn't be reachable on IPs B and C for example.

Second of all, pterodactyl doesn't accept localhost by default and so it is not resolved, so all you need to do to fix that issue of yours is use the server's external IP in that piece of code, and not either of the two forms for localhost or 0.0.0.0.

 

[Mooselk]

"Also tried using "0.0.0.0" and "localhost", but I believe all are the same thing"

0.0.0.0 will bind to all addresses, localhost is the same as 127.0.0.1 which will only allow connections from the machine it's self or what ever.

 

[iiredfox]

First of all, let me clear this up: 127.0.0.1 is localhost, yes, but 0.0.0.0 is not localhost, at all. 0.0.0.0 means bind to all interfaces, and so to all IPs, so if you have IP A and IP B and IP C assigned to that server, 0.0.0.0 will basically tell the application that all IPs A, B and C have to be listened to and so the app will be accessible from these three IPs. While if you were to tell the app to listen to IP A only then the app wouldn't be reachable on IPs B and C for example.

Second of all, pterodactyl doesn't accept localhost by default and so it is not resolved, so all you need to do to fix that issue of yours is use the server's external IP in that piece of code, and not either of the two forms for localhost or 0.0.0.0.

Already used the external IP but i'm using it on the bungee and it didn't accept it at all.

 

[ItsHoney]

Pterodactyl makes use of Docker containers which may be why It's not allowing, try going into pterodactyl control panel and find a place where we could allocate ports.

I faced a similar issue sometime ago but It was with MySQL

 

[iiredfox]

Pterodactyl makes use of Docker containers which may be why It's not allowing, try going into pterodactyl control panel and find a place where we could allocate ports.

I faced a similar issue sometime ago but It was with MySQL

Already allocated ports but the ports still closed.

 

[zappy2978]

Add me on discord zappy2978#5759 I can try to help...

 

[iiredfox]

Add me on discord zappy2978#5759 I can try to help...

Added.[DOUBLEPOST=1524884743][/DOUBLEPOST]

Add me on discord zappy2978#5759 I can try to help...

I like that 2 mins wait and then boom deleted or blocked.
http://prntscr.com/jb3poo

 

[ItsHoney]

Do you have a self-managed VPS?

If so, try this, to rule out the possibility that pterodactyl may not be at fault here, try running a server using the VPS console and then see if the connection fails that way as well. Also make sure that If you setup a firewall then that specific port is open

 

[Mark]

Try using this ip inside of bungee config: 172.18.0.1

 

[iiredfox]

That won't work unless he's wanting to locally host the server and have it communicate with the host machine, that's just pterodactyl's bridged interface. Using 127.0.0.1 will only work inside of the container since the network is isolated on a per container basis...

The easiest way around this is to use the WAN IP address on eth0 or equivalent interface, docker should take care of all of the networking needs such as opening ports and the such for you.

Do you have any tutorial that would help me out to open ports using docker?

 

[TheMCNote]

Please add me on
TheMCDestroyer -- John#3441
I should be able to help at no cost