My server doesnt connect my local wings daemon | Pterodactyl® | Page 1

onyx pewter Jan 17, 2023, 8:29 PM

#

When I start my server with Public ip it gives me this error:

Error Event [d68ad680-3228-44e9-bbfd-defbc43f230f]: environment/docker: failed to start container: Error response from daemon: driver failed programming external connectivity on endpoint 5af0d763-7e5a-4c73-8591-e9722182850b (fbe2effaf20b9e1aead9dae2c640a75595d7222bf2e3181abcd294c293644a81): Error starting userland proxy: listen tcp4 MYPUBLICIP:25565: bind: cannot assign requested address

When I try with local ip(127.0.0.1) it starts but doesn't connect remotely.

lilac fernBOT Jan 17, 2023, 8:29 PM

#

At your service, @onyx pewter!

The IP address you have assigned to your server is not actually available for use on your machine. Node allocation creation is explained in the Wings install documentation: https://pterodactyl.io/wings/1.0/installing.html#node-allocations

Execute the command hostname -I | awk '{print $1}' and change your Node allocations to use this IP. Yes, it can be your internal/local IP when you're behind NAT. When behind NAT you will allocate the internal IP and connect using the public IP.

If you have added multiple public IPs to your network interface, you can view all of them using the command ip a | grep "inet "

onyx pewter Jan 17, 2023, 8:31 PM

#

lilac fern At your service, <@614067535058436096>! The IP address you have assigned to you...

When I do hostname -I | awk '{print $1}' s ip it gives same error

trail garden Jan 17, 2023, 8:35 PM

#

Provide the output from the command and error in that case for us to compare.

onyx pewter Jan 17, 2023, 8:36 PM

#

#

trail garden Jan 17, 2023, 8:37 PM

#

They are not the same. Read the bots response and fix your allocation

onyx pewter Jan 17, 2023, 8:38 PM

#

its literally the same ip address

#

Look at the first screenshoot's ip

trail garden Jan 17, 2023, 8:38 PM

#

One of us is blind in that case. 172. X and 3.67x are not the same and the system error agrees.

onyx pewter Jan 17, 2023, 8:39 PM

#

So when I run hostname -I | awk '{print $1}' command it outputs 172.x ip adress

#

And when I use that ip it still gives me same error

trail garden Jan 17, 2023, 8:40 PM

#

Ah, your first screenshot contained the error but also the second attempt.

It's not allocation error after that. Something else is making it crash.

#

Refresh, restart and check again. It should output logs unless something is very wrong

onyx pewter Jan 17, 2023, 8:42 PM

#

I refreshed and started still same error

trail garden Jan 17, 2023, 8:42 PM

#

What is the same error

onyx pewter Jan 17, 2023, 8:42 PM

#

container@pterodactyl~ Server marked as offline...
[Pterodactyl Daemon]: Updating process configuration files...
[Pterodactyl Daemon]: Ensuring file permissions are set correctly, this could take a few seconds...
container@pterodactyl~ Server marked as starting...
[Pterodactyl Daemon]: Pulling Docker container image, this could take a few minutes to complete...
Pulling from pterodactyl/yolks 
Digest: sha256:ba880156e2489988f637d10860388201a9b003e46b68e53767c0158d354b94a3 
Status: Image is up to date for ghcr.io/pterodactyl/yolks:java_17 
[Pterodactyl Daemon]: Finished pulling Docker container image
container@pterodactyl~ Server marked as offline...
container@pterodactyl~ Error Event [1c987806-dbea-4443-948a-b141e856fe22]: environment/docker: failed to start container: Error response from daemon: driver failed programming external connectivity on endpoint 5af0d763-7e5a-4c73-8591-e9722182850b (22c9472f6f470ec3357136547c69ac6386aa678327e48e710c356dcde6e68b0d): Error starting userland proxy: listen tcp4 3.67.133.14:25565: bind: cannot assign requested address
[Pterodactyl Daemon]: ---------- Detected server process in a crashed state! ----------
[Pterodactyl Daemon]: Exit code: 128
[Pterodactyl Daemon]: Out of memory: false
[Pterodactyl Daemon]: Aborting automatic restart, last crash occurred less than 60 seconds ago.

lilac fernBOT Jan 17, 2023, 8:42 PM

#

At your service, @onyx pewter!

The IP address you have assigned to your server is not actually available for use on your machine. Node allocation creation is explained in the Wings install documentation: https://pterodactyl.io/wings/1.0/installing.html#node-allocations

Execute the command hostname -I | awk '{print $1}' and change your Node allocations to use this IP. Yes, it can be your internal/local IP when you're behind NAT. When behind NAT you will allocate the internal IP and connect using the public IP.

If you have added multiple public IPs to your network interface, you can view all of them using the command ip a | grep "inet "

trail garden Jan 17, 2023, 8:43 PM

#

That's you changing allocation back to something invalid.

onyx pewter Jan 17, 2023, 8:43 PM

#

I didn't changed anything

trail garden Jan 17, 2023, 8:43 PM

#

You would have to change it to a valid allocation

#

Which you receive by following the instructions provided a couple of times. The allocation for you is the 172.x ip of the interface

onyx pewter Jan 17, 2023, 8:44 PM

#

It was because I didn't deleted the 3.X ip

#My server doesnt connect my local wings daemon