Pterodactyl / Pelican

It is best to first review the vendor documentation

This documentation will likely be more up-to-date than mine

Troubleshooting | Pelicanpelican.dev

Troubleshooting | Pterodactylpterodactyl.io

---

This section contains things that I've had to fix on my instance - it may not be helpful for you, but it may be a starting point too.

Can't join Game Server/s

This section is to assist with troubleshooting port forwards, firewall rules and DDNS issues.

This guide is assuming you're hosting the server in your home network, not on a cloud host.

There are multiple areas where this can go wrong. Let's narrow it down, please refer to the below image.

This network map assumes you are hosting your server in the same house / network as your personal PC. You may have additional devices, like network switches, WiFi etc. Generally, these devices won't cause the issue you're seeing, but they may.

The above network map should be relatively similar to your home network. We have 4 devices,

1. Wings Node, where the game server is hosted

2. Your gaming PC

3. A Firewall / Modem / Router

4. friend's computer

Our end goal is for the purple line (friends computer > firewall > pterodactyl node) to work.

There are a few places that this line can fail,

1. Connecting to the Domain (DNS issue) or IP address

2. Bad port forwarding config in the modem / router

3. Bad firewall config in the Pterodactyl node

4. Bad game server installation config

5. ISP blocking the port or port forwarding completely

6. Your ISP uses CGNAT

3 is the easiest to confirm;

To do this, we'll follow the orange line in the network map above

1. Get the LAN IP address for your Wings node. This is likely to start with 192.x.x.x, 10.x.x.x or 172.x.x.x

2. Connect to your game server via the internal IP:port, eg 192.168.1.20:25565

I can join the server

Most likely your port forward or (IF you are using a domain) your Domains DNS is bad.

have your friend connect via your public IP address and server port, eg 1.2.3.4:25565

If your friends are connecting via IP, skip this step. Browse to this website to get your public IP address and ping your domain. If the IP does not match, the DNS is incorrect. If so, you most likely have a dynamic DNS address - refer to for a solution. Alternatively, your ISP may provide a static IP address at an additional cost.

If connecting directly to your public IP fails, confirm your port forward rule applies to the

• correct local IP

• correct port

If it still fails to connect:

your ISP may be blocking port forwards. I would suggest doing some Googling on your router / modem model to confirm your port forward rule has the correct syntax as some modems are awkward. You may have luck searching for my modem model port forward minecraft server but if you have no luck, you will need to ring your ISP.

Your ISP may be using CGNAT. You will need to contact your ISP to have this resolved. I would recommend watching https://www.youtube.com/watch?v=eIpR5ZBCF_g. Port forwarding will NEVER work behind a CGNAT without additional and complex network infrastructure.

Extra: You can use this website to test if a port is open (waiting for connections). Minecraft is a great server to test for this, as there are plenty of tools for testing things, like this

Unable to join the server

Troubleshooting Dynamic DNS

You can skip troubleshooting DDNS by trying to connect to your game server via your public IP instead

1. Navigate to https://whatismyipaddress.com/ and take note of your IP address

2. Launch CMD or the shell of your choice

3. Type ping YOUR.DDNS.ADDRESS.HERE and hit enter eg ping play.reallycoolservers.com

4. Take note of the output and refer to the below table

Successful Ping

C:\Users\you>ping play.reallycoolservers.com

Pinging play.reallycoolservers.com [123.123.123.123] with 32 bytes of data: 
Reply from 123.123.123.123: bytes=32 time<1ms TTL=64 
Reply from 123.123.123.123: bytes=32 time<1ms TTL=64 
Reply from 123.123.123.123: bytes=32 time<1ms TTL=64 
Reply from 123.123.123.123: bytes=32 time<1ms TTL=64

Ping statistics for 123.123.123.123: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms

A server has responded to your pings, great!

1. Confirm that the IP address matches your Google result

   • If it matches, great! Skip to

   • If it doesn't match, there is an issue with your DDNS container. Review the logs for the container

Your DDNS config is correct

Could not find host

Resolves IP but fails to connect

---

Panel Errors

Error 500

Yeah its broken! Post on the Pterodactyl / Pelican discord for assistance.

The MAC key is invalid

Your APP_KEY in the panel .env file has changed. You will need to restore the .env file, or wipe nad rebuild Pelican / Ptero from scratch. You will need to recreate your servers and move files over etc.

If you don't have the key, try the Pelican / Pterodactyl Discord for support before starting again

mountedActionsData.0.files

Your proxy addresses are not correct. Refer to

Wings Errors

Token ID error

If you are using a reverse proxy, it may be stripping the authentication headers.

FATAL: failed to configure docker environment error=Error response from daemon: Pool overlaps with other one on this address space

Wings has defaulted to a docker network range that is in-use. The easiest way to resolve this is to edit your config.yml file, per step Upload Configuration file to Wingsto include the below lines

docker:
  network:
    interfaces:
      v4:
        subnet: 172.31.0.0/24
        gateway: 172.31.0.1

Panel is unable to see Node

1. Start the Wings container if its not running

2. Check your docker logs, you should see something similar to below

   
3. Open your internet browser and navigate to hostname:port, you should see the below error;

   {"error":"The required authorization heads were not present in the request."}

4. Navigate to your admin panel > nodes

5. Right click anywhere and select Inspect

6. Click on the console tab

7. Review the errors

If you have a token_id error, it may be a bad config file.

If you have a ... is not Pelican Wings error, restarting the node, panel and walk away for 15 minutes

If you have an error with cloudflareaccess.com in the url, such as below - your Application bypass policy isn't working. Stop your stack, delete the dockflare volume and start it again. Wait 5 minutes and check again

https://xxx.cloudflareaccess.com/cdn-cgi/access/login/wings.agame…-XzXCXRPPH9zspmqCwhpw7i83VTWfHcc6ne8PFfW5SEGA&redirect_url=%2Fapi%2Fsystem does not match node token_id !
[Alpine] console.error("https://xxx.cloudflareaccess.com/cdn-cgi/access/login/wings.xxx.com?kid=xxx

Pool overlaps with other one on this address space

Wings container logs

failed to configure docker environment error=Error response from daemon: Pool overlaps with other one on this address space
Stacktrace: Error response from daemon: Pool overlaps with other one on this address space

Symptoms

• Servers wont start but containers are running

• Wings node shows as offline in Panel

• Unable to navigate to Wings proxy url

• Error above in logs for Wings container

This one is pretty easy to solve and can be done proactively (straight after installing Wings)

Wings, by default, chooses docker network 172.18.0.0 for its game servers. This is a low range and it only takes pushing 18 stacks to run into this issue.

Per Pterodactyl's doco, the best way to work around this is changing the subnet that Wings uses in the Wings config file. To do so,

1. Log into Portainer and access your Wings node

2. On the left, click on Stacks

3. Click on your Wings stack

4. Scroll down to containers and open the 'Wings' container (not DB)

5. Scroll down and note the volume mapped to /etc/pterodactyl

6. On the left, select Volumes

7. Click on 'browse' next to the volume noted in step 4

8. Download the config file

9. Open it in your editor of choice

10. Locate the 'Docker' section and take note of the highlighted information below

    

    Red = interface IP Yellow - Subnet range Green - Gateway IP
11. Go back to Portainer and select the 'Networks tab

12. Confirm that your v4 subnet (orange) is used by another stack

13. Update the 3 fields to be a range that is not in use

    • Red and Green field will be the same and must be in the same subnet range as orange (eg 172.172.0.1)

    • Orange must be a valid subnet range, with the last 2 digits as 0 (eg 172.172.0.0/16) Aka only change the second IP number ( 123.123.123.123 )

14. Upload the config file back into the relevant volume

15. Restart the Wings stack

Please note:

The example provided above (172.172.0.0/16) clashes with public IP's. You may experience issues with these containers accessing the internet using this subnet. Please refer to this doco for a list of private subnets

I'm personally running 172.172.0.0/16 and haven't encountered issues, as this only affects the docker Wings and game server containers, but your mileage may vary.

Database issues

Create a new database - An unexpected error was encountered while processing this request. please try again

Have you set the HASHID variable per Creating a Panel documentation?

If not, please re-read the documentation as you may have missed other steps too...

Game is unable to connect to server database

Try connecting via IP. This may be a docker DNS issue.