Pterodactel wings a problem with ports for the game server

[sokolov8611]

The bottom line is this, when you start the RageMP game server from the game server product directory, but it will start the server directly with the command ./ragemp-server, the server starts and everything works as expected, the port is registered in the assembly that is responsible for receiving information about the clothing store. When starting and checking.

netstat -tulpen
tcp 0 0 0.0.0.0:22006 0.0.0.0:* LISTEN 0 692671 74701/./ragemp-serv
tcp6 0 0 :::3402 :::* LISTEN 0 691971 74701/./ragemp-serv
tcp6 0 0 :::63222 :::* LISTEN 0 691973 74701/./ragemp-serv
udp 0 0 0.0.0.0:22005 0.0.0.0:* 0 692675 74701/./ragemp-serv
udp 0 0 0.0.0.0:34381 0.0.0.0:* 0 692674 74701/./ragemp-serv
We can see that the port 63222 that I need is open and
udp is working. 0 0 0.0.0.0:34381 0.0.0.0:* 0 692674 74701/./ ragemp-serv
as well as another port appears.

As soon as I start the game server through the pteroactel panel, the output is
tcp 0 0 49.12.133.186:22005 0.0.0.0:* LISTEN 0 690126 75439/docker-proxy
tcp 0 0 49.12.133.186:22006 0.0.0.0:* LISTEN 0 695826 75455/docker-proxy
tcp 0 0 49.12.133.186:63222 0.0.0.0:* LISTEN 0 695833 75472/docker-proxy
udp 0 0 49.12.133.186:22005 0.0.0.0:* 0 696831 75448/docker-proxy
udp 0 0 49.12.133.186:22006 0.0.0.0:* 0 694880 75463/docker-proxy
udp 0 0 49.12.133.186:63222 0.0.0.0:* 0 695838 75482/docker-proxy

I started changing config.yml and edited the following code
name: pterodactyl_nw
ispn: false
driver: bridge
network_mode: host
is_internal: false
enable_icc: true
enable_icc: true
network_mtu: 1500
interfaces:
v4:
subnet: 0.0.0.0/0
gateway: 0.0.0.0
v6:
subnet: ::/0
gateway: '::'

    after that, the output is like this, it's already better, it almost looks like when I run without a panel.
    
     netstat -tulpen

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name
tcp 0 0 0.0.0.0:22006 0.0.0.0:* LISTEN 0 360929 49889/./ragemp-serv
tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 102 22843 689/systemd-resolve
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 0 20874 1208/exim4
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 25779 937/sshd: /usr/sbin
tcp 0 0 0.0.0.0:3306 0.0.0.0:* LISTEN 116 22868 794/mariadbd
tcp 0 0 0.0.0.0:8888 0.0.0.0:* LISTEN 0 25928 1519/docker-proxy
tcp6 0 0 :::63222 :::* LISTEN 0 357160 49889/./ragemp-serv
tcp6 0 0 :::8080 :::* LISTEN 0 356729 48976/wings
tcp6 0 0 :::2022 :::* LISTEN 0 359585 48976/wings
tcp6 0 0 ::1:25 :::* LISTEN 0 20875 1208/exim4
tcp6 0 0 :::22 :::* LISTEN 0 25781 937/sshd: /usr/sbin
tcp6 0 0 :::3402 :::* LISTEN 0 357158 49889/./ragemp-serv
tcp6 0 0 :::8888 :::* LISTEN 0 27703 1530/docker-proxy
udp 0 0 0.0.0.0:22005 0.0.0.0:* 0 360933 49889/./ragemp-serv
udp 0 0 127.0.0.53:53 0.0.0.0:* 102 22842 689/systemd-resolve

    But it still doesn't work as expected. Anyone who can help, please help. It's definitely some kind of problem with Wings.