Using SSX premium with Pterodactyl panel - ServerSelectorX/ServerSelectorX GitHub Wiki

This guide assumes that you are the panel administrator. If not, contact your server host.

This guide has a lot of different IP addresses and steps. Many people mix them up and wonder why it is not working. Please read this entire wiki page carefully and follow the instructions exactly

First, we need to add an extra allocation to all servers with ServerSelectorX installed (usually just your hub server).

  1. Go to the admin control panel
  2. Go to Nodes
  3. Select your node
  4. Go to the Allocation tab.
  5. On the right, assign a new allocation with the IP address 127.0.0.1 and port 9782 (or something else). You can set the alias to "internal", so you know that this port is not accessible externally.
  6. Still in the admin control panel, go to Servers
  7. Select the server with ServerSelectorX (usually the hub server)
  8. Go to the "Build Configuration" tab.
  9. In the "Allocation Management" section, where it says "Assign Additional Ports", add the allocation you just created
  10. Restart your hub server to finish adding the allocation
  11. You are NOT done! Continue reading below

Configuring ServerSelectorX

Now, open config/api.yml in ServerSelectorX and make sure that the configured port matches the allocation port. If you are using version 2.1.2+, change host to 0.0.0.0 here as well.

In SSX-Connector, use the IP address 172.18.0.1

Troubleshooting

  • Did you enter 127.0.0.1 for the allocation and 172.18.0.1 in the SSX-Connector config? Note the use of 127 and 172.
  • Did you change the host option in api.yml to 0.0.0.0?
  • Did you enter the same port in the allocation and the config files for ServerSelectorX and SSX-Connector?
  • Are all servers on the same machine? If not, these instructions will not work for you.
  • Is the allocation assigned to the server with ServerSelectorX (the hub server)?
  • Is the port not used anywhere else?
  • Is the allocation set as secondary (the primary port is what the Minecraft server runs on)?
  • Is your pterodactyl0 interface using a network different from 172.18.0.0/24? Run the command ip a show dev pterodactyl0 and check inet
  • A firewall on the host may be blocking connections. Using a firewall like iptables in combination with docker is not recommended. Instead, bind your applications to specific interfaces.