Cannot assign Requested Address to Server (Bungeecord)

[wary beacon]

20:43:13 [WARNING] Could not bind to host /217.76.57.119:25565
io.netty.channel.unix.Errors$NativeIoException: bind(..) failed: Cannot assign requested address

if i do assign 127.0.0.1 it wont work cause theres a bug in bungeecord so people can exploit into servers and login as the owner, i need to use PreventPortBypass and it kicks me out if i join on 127.0.0.1 cause it says "Please join directly over frittopia.de"

[visual girder]

Bungee allocation should be your public IP, servers should be 127.0.0.1

In your bungee config and in prevent port bypass the IP for your servers should be the wings subnet, by default 172.18.0.1

When in doubt you can use ppb debug and the plugin will tell you the address players are trying to connect from.

[wary beacon]

but what is if i also use another server i cant just put 127.0.0.1

[visual girder]

No, that would point the container to itself. You need to point the container to another container.

[wary beacon]

wdym

[frail wigeon]

View our minecraft proxy guide https://pterodactyl.io/community/games/minecraft.html

[royal pulsar]

You can use systems like authme bungeecord + authme in all servers so if user enter through another server that is not bungee, will also need to input the password.

Depending on how is set up your network, maybe you need to use 0.0.0.0 in the ip allocation

[dense basin]

No, you shouldn't. Refer to the bots response above or otherwise your proxy does nothing when every server is exposed

[royal pulsar]

? Shouldn’t what?

[visual girder]

You should also use the PreventPortBypass plugin on your non-Bungee servers. The IP to whitelist will be 172.18.0.1, your wings ip. The same IP you'll need to use in your BungeeCord Config for your servers.

[royal pulsar]

Much easier, just using authme in all servers + bungee all connected in same db, if someone try to connect another server that is not set up as main auth server in authme setup, will require to use the login and password. In bungee auth config, enable “allserversareauth” and list all servers in “authservers” then all servers will be auth so if player connect one server because he knows the port will also need to put the password.

[visual girder]

Objectively PreventPortBypass is easier as it just refuses the connection. Essentially "Go through the Proxy or don't go through at all". Either way this is moot, as the non-proxy servers should not be port forwarded or accessible to the outside internet, but these appear to be very similar plugins that accomplish the same goal through different means.

[wary beacon]

thats the sence
so 172.18.0.1 but what on other server? @visual girder

on node 2

[wary beacon]

i think im just not using that

pterodactyl is too complicated and not working well

[wary beacon]

but i cant put

i guess ill keep using things like putty

[visual girder]

If the server is on a separate node it should view the connection as your first node's public ipv4.

[wary beacon]

i need to put public ip into bunee config but how

[visual girder]

Same way you were putting 172.18.0.1 into your config. IP:PORT

[wary beacon]

but someone also could connect with 127.18.0.1

[visual girder]

You could use your bungee container's exact address instead

[wary beacon]

what is a container

[visual girder]

Each Pterodactyl Panel server is a Docker container.

[wary beacon]

someone isntalled me pterodactyl i used putty and pufferpanel

[wary beacon]

what is a docker container

[visual girder]

Your program running in the container can only see the container's files. Everything but /home/container is read only for security.

[wary beacon]

so how do i just allocate my public server ip

if i use soemthing with 0.0.0.0 or 127.#.#.# itll be posssible to bypass

i wanna open a public minecraft network

[visual girder]

Only the Bungee needs to be your public IP or 0.0.0.0

Everything else can be 127.0.0.1

In your bungee config you point to 172.18.0.1 for servers on the same node and the public IP of your 2nd node for the 2nd node.

[wary beacon]

preventportbypass cant be 127.0.0.1 cause the bungee will be passed trough the ip and itll be 127.0.0.1 if using the bungeecord bug

[visual girder]

I don't think you understood what I was trying to convey. Let me try again.

Your Bungee server should have your node's public ip allocated to it in the panel.
Any servers that don't need to see other containers should have 127.0.0.1 allocated to them so they can access the outside internet but not see other containers.

In your Bungeecord Configuration AND in PreventPortBypass's Configuration you'll use 172.18.0.1 as the IP and put the port of the server. You do not use 127.0.0.1 in PreventPortBypass's Configuration. If you have any doubt as to where a connection is coming from you can use the ppb debug command and when a player tries to join it will print the source address they are coming from in console.

If you have a server in your bungee that is on a second node you'll allocate 127.0.0.1 to that server, but in Bungee's Config and in the Server's PreventPortBypass Config you'll use your first node's public ipv4 address as the IP.

[visual girder]

I think it's because I explained it in parts the first time. That message should have all of the information in it.

[cyan bolt]

You need to assign either the local IP of the WAN Interface or 0.0.0.0 to the Egg. The Bind Address itself should be 127.0.0.1 for the Servers and 0.0.0.0 for the bungeecord proxy server in server.properties

[wary beacon]

it definitly cant be local

if you use the bungeecord bug the server will say something like "Player connected [127.0.0.1]"

[visual girder]

What do your allocations for bungee and the servers tied to bungee look like, your bungee config, and your preventportbypass config?

[stone skiff]

Just do this

[visual girder]

^

[wary beacon]

i cant allocate the public one.
preventportbypass with 127.0.0.1 is the dumbest i can do.
i dont look into the console everytime.

[wary beacon]

please i just wanna use a webpanel

or is there and alternate panel?

[wary beacon]

and why da hell 172. thats a very diffrent ip

[visual girder]

Again that's your Pterodactyl0 interface. Youcan allocate the public one to the bungee.

All the info is in that message. If you want to network servers together using Pterodactyl Panel, follow it.

[wary beacon]

i found the solution

[wary beacon]

i cant

it wont accept

the solution is to run the bungeecord server not on pterodactyl

[cyan bolt]

just set the ip of your bugeecord server to 0.0.0.0 wtf

There is no issue in running bungeecord on pterodactyl. We have a cluter of like 5 Paper Servers + Waterfall running on pterodactyl

[wary beacon]

then preventportbypass doesnt owrk

[wary beacon]

luck

[cyan bolt]

what do you mean with that? Just dont assign ports to the server except the bungeecord proxy and use internal docker ips for communication.
As alternative you can just use bugeeguard

[visual girder]

It does work, you have messed up the configuration somewhere. If you want to send your configuration for these I can tell you where you went wrong.

[wary beacon]

ill just use bungeecord on my server

and the other things on pterdodactülul