Please explain the issue you're experiencing in as much detail as possible. Preferably with error messages in a text format or paste link to logs. Nobody can assist you without information that helps to understand the issue. Help us help you. Messages such as "doesn't work" or "i need help" will most likely be ignored.
#Problem binding IP - Docker
sacred oysterBOT
forest violet
Send the error as text
desert jewel
Error Event [78084139-8818-42df-b8a7-568dac20c3ce]: environment/docker: failed to start container: Error response from daemon: driver failed programming external connectivity on endpoint 113827bd-e51a-4dc1-b3cd-88896e0fadba (e1d2104efa09ffcfb04629dd73f3f773641e93d6d32d3f218719a865ec23a04a): Error starting userland proxy: listen tcp4 31.42.4.52:27015: bind: cannot assign requested address
sacred oysterBOT
At your service, @desert jewel!
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 "
desert jewel
It still doesn't allow me to change it to my local IP.
desert jewel
It still doesn't allow me to change it to my local IP.
you need to set in allocation
and then change allocation
Okay I managed to fix it, but here's the catch:
When getting into the panel everything works fine, but my friend sees "We're having some trouble connecting to your server, please wait..."
sacred oysterBOT
@desert jewel; It looks like your browser is unable to reach the Wings.
Make sure that your wings are running using systemctl status wings and that your Wings ports (by default 8080/2022) are open in your firewall or router. This website can check your ports https://dnschecker.org/port-scanner.php
Browser console errors can also provide additional debugging information. More troubleshooting steps can be found at https://pterodactyl.io/panel/1.0/troubleshooting.html#cannot-connect-to-server-errors
Should the panel and wings be located on the same network, you might experience NAT reflection issues. In that case, type .nat for more information.
desert jewel
When visiting the panel via browser using my pub ip.
then you need to forward the ports etc
and read what bot said about troubleshooting
They are forwarded, point is, my server adress uses local IP (192.168.0.11).
Everytime i try to set it to my Pub, the previous problem comes back.
set to pub
keep allocation as LOCAL
everything else public
So
Nodes -> Allocation -> make a new allocation there using my pub IP?
.............
LOCAL FOR ALLOC
pub for everything else
you dont get it and i cant explain this to you that allocation = docker expose
look up what docker expose does, it binds to an address on the system
and since you are in a NAT you will NOT have a public ip on your system
..........
No, that's not what I'm asking, maybe I worded it wrong.
Look
My GAME PORT is set to my local IP address
and thats normal
and everything works until somebody get on the browser via my PUB IP
then you have a network issue
and thus they can't check the console or anything else because " "We're having some trouble connecting to your server, please wait..."
Support Bot
APP
— Today at 13:41"
sacred oysterBOT
@desert jewel; It looks like your browser is unable to reach the Wings.
Make sure that your wings are running using systemctl status wings and that your Wings ports (by default 8080/2022) are open in your firewall or router. This website can check your ports https://dnschecker.org/port-scanner.php
Browser console errors can also provide additional debugging information. More troubleshooting steps can be found at https://pterodactyl.io/panel/1.0/troubleshooting.html#cannot-connect-to-server-errors
Should the panel and wings be located on the same network, you might experience NAT reflection issues. In that case, type .nat for more information.