Help, It's driving me crazy. I create new servers they say that they are listening on ports but they never open. I have tried different port, from localhost address and external address.
#Ports Not Being Opened, Cant be Reached Outside
tardy heath
toxic lavaBOT
You'll need to grab error logs for Wings and share the link with us. The following command will help you collect the required information for debugging: sudo wings diagnostics
tardy heath
toxic lavaBOT
I have found the following for: https://ptero.co/adorypadec
At your service, @tardy heath!
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 "
tardy heath
Error Event [61b4e63c-29c2-45cf-a8c4-d6afecf3d7af]: environment/docker: failed to start container: Error response from daemon: driver failed programming external connectivity on endpoint 739abb7c-fb59-42b5-ae8c-1aae958dfa9e (7ed2406bacbf06b5c1753463f1ddcc3237f2cf7570c50b2a1ae31bb1d6dcc7e1): Error starting userland proxy: listen tcp4 172.16.4.6:27018: bind: address already in use
toxic lavaBOT
At your service, @tardy heath!
The IP address you have assigned to your server is not actually available for use on your machine, or something is already running on that port. Use ss -plnt | grep :<port> (replacing <port> with your own) to find what processes might be using it.
If you don't find any service using the port, then refer to the instructions below.
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. You still have to use it as that is your network interface IP.
If you have added multiple public IPs to your network interface, then you can view all of them using the command ip a | grep "inet "