I have read the wiki info, and i have set the subservers IPs to 127.0.0.1 and in my proxy settings i am refeering to them as 172.18.0.1:PORT but it wont let me connect to my servers. please help
#Requesting help with minecraft proxy server.
mighty mulch
i have fallowed this - https://pterodactyl.io/community/games/minecraft.html#network-configuration - to every single letter, and it everything has been done exactly as it says but it still wont let me connect to my servers.
hallow sentinel
Try using the actual ip of the node/servers instead of 127.0.0.1
It should fix it
@mighty mulch
mighty mulch
Well I followed the guide and set the servers to 127.0.0.1. I was using the actual ip of the node before and was still getting the same exact errors 'failed to connect to server: connection refused'
mighty mulch
yes
im using 25565-25569 and they was opened following the firewall section in that guide
worldly rune
@mighty mulch
127.0.0.1 would point to the container, ie. your proxy.
0.0.0.0 would point to localhost, letting your containers communicate with each other.
mighty mulch
Ok so my backend servers should all be 0.0.0.0:PORT, and my velocity config should point to 0.0.0.0:PORT. And my proxy should be it's regular IP:PORT, correct?
worldly rune
Either 0.0.0.0 or your container's internal ip.
mighty mulch
Ok. But they do get referred to from velocity as 0.0.0.0 also right? Or do I point to them as 172.18.0.1:Port like the wiki above states
I'm just trying to make sure I do this right because so far everything I've done has resulted in it not working
worldly rune
I would follow the documentation. I am not an expert at this.
It's just the Pterodactyl Allocations I would avoid using 127.0.0.1 with, as I'm pretty sure that makes them only able to see themselves and no other containers.
mighty mulch
I would follow the documentation. I am not an expert at this.
It's just the Pter...
ok. ill try again lol. all the servers are on the same node i should mention. so at default they all had the same ip and i assigned them ports from 25565-25570. but that didnt work, so i tried to follow the guide from pterodactyl it said make them 127.0.0.1 but that didnt work either
im just lost at thiis point
worldly rune
For my Bungee config (Not sure if Velocity is the same) I have 0.0.0.0 for all my Pterodactyl Allocations and the node's public ipv4 for the config.yml that points to all the servers.
mighty mulch
i tried bungee at first and was having the same issues i guess im not doing something right. ill try again with bungee. your bungee config point to the servers are you using just 0.0.0.0:PORT? to point towards them?
worldly rune
I'm using public ip:port to point to them
External IP
Yet the only port I have open is the proxy's
mighty mulch
the ip of your node correct
worldly rune
Yes
mighty mulch
For my Bungee config (Not sure if Velocity is the same) I have 0.0.0.0 for all m...
im referring to the 0.0.0.0 for all prerodactyl allocations here
worldly rune
Yes
mighty mulch
so your proxy points to nodes ip and your backend paper servers or whatever are setup with 0.0.0.0? and bungees config points to server: address: 0.0.0.0:PORT?
thats the part thats confusing me i think
or the config is point to the same address as the proxy just with each different port/s
mighty mulch
right so the config points to same address that the proxy is on
worldly rune
In the config.yml the censored IPs are the node's public ip
mighty mulch
ok i get it that actually helped so much thank you
worldly rune
No problem
I'm probably not doing this the right way; I should be using internal ips. Somehow this works for me though even with only the proxy's port open.
mighty mulch
me and the machines owner im trying to set this up for have been trying to do this for like 2 days and all documentation i read told us to use different ips and such
each documentation we found was different lol
worldly rune
Same, I just started using trial and error until it worked.
mighty mulch
I'm probably not doing this the right way; I should be using internal ips. Someh...
like that can anyone connect to your backend servers directly?
worldly rune
I disabled that, they can only connect through the proxy.
mighty mulch
oh is that a setting in bungee or something? i dont think velocity offers that setting
urban bolt
@mighty mulch found the fix ?
worldly rune
Yeah, it's force default server I believe
mighty mulch
yeah ive been using the wrong ips apparently lol
worldly rune
Also a plugin called PreventPortBypass
mighty mulch
is that a bungee proxy plugin or spigot plugin?
urban bolt
Well from our last attempt I was locked out of my terminal 😭😭
And out my machine into recovery cuz of it
worldly rune
is that a bungee proxy plugin or spigot plugin?
Spigot Plugin for each individual server
mighty mulch
Spigot Plugin for each individual server
alright. oh one last question make sure we dont mess this up too
the firewall section of the guide. i think we ran the following command incorrectly - ufw allow in on pterodactyl0 to 172.18.0.1 port <LOCALHOST_PORT> proto tcp
localhost_port would be 0.0.0.0:PORT correct?
or the nodes external ip:port
worldly rune
I'm not sure, I didn't do that part; I don't use ufw anymore.
mighty mulch
what do you suggest for protection?
worldly rune
I didn't have to open anything, but that's probably why I have to use the external ip to connect
I use TCPShield on the Proxy.
If you meant firewall I use firewalld
mighty mulch
ah i see. we're running ubuntu i believe, same concept as firewalld i believe.
worldly rune
The proxy did work for us before I switched our Ubuntu firewall to firewalld, and I never did that step.
mighty mulch
should we change to centos and use firewalld?
worldly rune
No, I would just use iptables directly
Or UFW; anything that can do what your goal is to do
worldly rune
the firewall section of the guide. i think we ran the following command incorrec...
Here would probably just be the port, not 0.0.0.0:port
mighty mulch
ok. im just not familiar with linux too much
worldly rune
Just the port number
mighty mulch
ok we'll try that
worldly rune
Stick with UFW for now, all the firewalls have some issues with docker but they all seem to work; they just give off warnings.
mighty mulch
ok
urban bolt
If you meant firewall I use firewalld
That’s what we use
Firewalld is what I installed
And mid install my whole machine shut down and didn’t respond
@mighty mulch the firewall was unnecessary then
mighty mulch
the wiki says firewalld would use this command to open the firewall to the server firewall-cmd --permanent --zone=public --add-source=172.18.0.1
urban bolt
Fuck the wiki
mighty mulch
im assuming source would = the nodes external ip
worldly rune
172.18.0.1 is the wing's docker network. Internal,
So it wants you to allow traffic from the outside into your container networks.
I never had to do that; I'm not entirely sure what that step is for.
mighty mulch
yeah it says
`If you are using a firewall, additional rules might be required to allow servers to reach each other on the node. In this case the proxy server needs to reach all of the game servers behind it. Therefore we need to allow traffic from the pterodactyl network to the server ports on localhost.
You can use the following commands as an example. 172.18.0.1 is the default address referring to the node within the pterodactyl network. Replace <LOCALHOST_PORT> with the allocated localhost ports of the game servers.`
worldly rune
Ah
mighty mulch
but i dont think the firewall was an issue. i was able to get connection to my proxy the proxy just wouldnt send me to the other servers
worldly rune
I have my wings subnet able to access the entire host internal network. It's not secure if you're a hosting company, but mine is just one network and I don't have to worry about people escaping their containers.
You most likely don't have a firewall between containers by default.
mighty mulch
yeah we only hosting a minecraft network with a few servers, and a discord bot atm
urban bolt
@worldly rune simple question saving hassle u able to show us via call ?
When you’re free
mighty mulch
i got the main part just i dont understand the firewall part.
worldly rune
There is no firewall part. Just open the port of the server you want people to access. If you want them to go through the proxy, only open the proxy.
urban bolt
i got the main part just i dont understand the firewall part.
I’ll figure it out
urban bolt
There is no firewall part. Just open the port of the server you want people to a...
Technically you don’t have to
But do
I’ve opened ports before
Dw about the firewalld I can do that
worldly rune
👍