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 parkervcp/steamcmd
Digest: sha256:57b6e170d1745adfb323c641f73f13e3e714d130d8e897bba33c4e6094a2aca2
Status: Image is up to date for ghcr.io/parkervcp/steamcmd:debian
[Pterodactyl Daemon]: Finished pulling Docker container image
container@pterodactyl~ Server marked as offline...
container@pterodactyl~ Error Event [9cde6f92-0c26-466a-adab-ba0c48d0a74b]: environment/docker: failed to start container: Error response from daemon: driver failed programming external connectivity on endpoint 707ea0fe-31a0-4c6a-a705-e28bd37f4bda (f2544f8e36308d64a1fb326bd072ac01e50079299ddd172e3efb907cf43078f3): Error starting userland proxy: listen tcp4 13.201.44.155:25570: 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.
#Can Someone help me with this error i cant fix it
reef hornet
formal coralBOT
At your service, @reef hornet!
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 "
reef hornet
still cant fix it
wide knot
Show the error again with the IP u use now then
reef hornet
actaully i delete that node and trying to install it again but its not working now
@wide knot
thats the problem i am facing
honest sail
Read what the bot told you
reef hornet
yeah i also allocate the ports in internal ip
honest sail
What
reef hornet
honest sail
And?
You need to actually assign the allocation the server
And remove the old allocation with the wrong ip
wide knot
How to say u used a script without actually saying it
reef hornet
its working now