starred/panel-pelican-dev
1
0
Fork 0
mirror of https://github.com/pelican-dev/panel.git synced 2026-05-04 18:00:48 +03:00
Code Issues 41 Packages Projects Releases 10 Wiki Activity

https://node.yourdomain.com:8443/api/system does not match node token_id ! #365

New Issue
Closed
opened 2026-02-05 17:30:00 +03:00 by OVERLORD · 3 comments
OVERLORD commented 2026-02-05 17:30:00 +03:00
Owner
Copy Link

Originally created by @DubblePumper on GitHub (Jun 23, 2025).

Current Behavior

When the Panel attempts to communicate with a configured node, it consistently throws:
VM6543:3 https://node.yourdomain.com:8443/api/system does not match node token_id !

Even though the token in /etc/pterodactyl/config.yml and the token saved under Nodes → Configuration in the Panel UI are identical, the handshake always fails with this mismatch error.

Expected Behavior

A successful authorization handshake. On an unauthenticated request to /api/system, the node should respond:
{"error":"The required authorization heads were not present in the request."}

And when using the correct Authorization: Bearer header, it should return node statistics rather than an authorization or token-mismatch error.

Steps to Reproduce

  1. Configure a node in the Panel with a valid FQDN (e.g. node.yourdomain.com), port 8443, and a freshly generated token.
  2. On the node server, ensure /etc/pterodactyl/config.yml contains the exact same token_id & token.
  3. Restart Wings (sudo systemctl restart wings) and confirm in the logs that it’s binding on port 844
  4. From the Panel server (or any client), run:
curl -k https://node.yourdomain.com:8443/api/system \
  -H "Authorization: Bearer <your-token>"
  1. Observe the response: it still returns a token mismatch error in the Panel UI and does not return node info.

Panel Version

1.0.0-beta21

Wings Version

1.0.0-beta13

Games and/or Eggs Affected

n/a (node configuration issue)

Docker Image

n/a

Error Logs

wings: https://pastebin.com/KqR9hr9X
panel: https://pastebin.com/c5Tp14uv

Is there an existing issue for this?

  • I have searched the existing issues before opening this issue.
  • I have provided all relevant details, including the specific game and Docker images I am using if this issue is related to running a server.
  • I have checked in the Discord server and believe this is a bug with the software, and not a configuration issue with my specific system.
Originally created by @DubblePumper on GitHub (Jun 23, 2025). ### Current Behavior When the Panel attempts to communicate with a configured node, it consistently throws: VM6543:3 https://node.yourdomain.com:8443/api/system does not match node token_id ! Even though the token in /etc/pterodactyl/config.yml and the token saved under Nodes → Configuration in the Panel UI are identical, the handshake always fails with this mismatch error. ### Expected Behavior A successful authorization handshake. On an unauthenticated request to /api/system, the node should respond: {"error":"The required authorization heads were not present in the request."} And when using the correct Authorization: Bearer <token> header, it should return node statistics rather than an authorization or token-mismatch error. ### Steps to Reproduce 1. Configure a node in the Panel with a valid FQDN (e.g. node.yourdomain.com), port 8443, and a freshly generated token. 2. On the node server, ensure /etc/pterodactyl/config.yml contains the exact same token_id & token. 3. Restart Wings (sudo systemctl restart wings) and confirm in the logs that it’s binding on port 844 4. From the Panel server (or any client), run: ``` curl -k https://node.yourdomain.com:8443/api/system \ -H "Authorization: Bearer <your-token>" ``` 5. Observe the response: it still returns a token mismatch error in the Panel UI and does not return node info. ### Panel Version 1.0.0-beta21 ### Wings Version 1.0.0-beta13 ### Games and/or Eggs Affected n/a (node configuration issue) ### Docker Image n/a ### Error Logs ```bash wings: https://pastebin.com/KqR9hr9X panel: https://pastebin.com/c5Tp14uv ``` ### Is there an existing issue for this? - [x] I have searched the existing issues before opening this issue. - [x] I have provided all relevant details, including the specific game and Docker images I am using if this issue is related to running a server. - [x] I have checked in the Discord server and believe this is a bug with the software, and not a configuration issue with my specific system.
OVERLORD commented 2026-02-05 17:30:04 +03:00
Author
Owner
Copy Link

@notAreYouScared commented on GitHub (Jun 23, 2025):

You using a reverse proxy of any sorts?

@notAreYouScared commented on GitHub (Jun 23, 2025): You using a reverse proxy of any sorts?
OVERLORD commented 2026-02-05 17:30:07 +03:00
Author
Owner
Copy Link

@DubblePumper commented on GitHub (Jun 23, 2025):

You using a reverse proxy of any sorts?

Yes, I run through the Cloudflare proxy (orange cloud) with WAF rules. In doing so, I use the Cloudflare SSL certificate (not Certbot). It worked smoothly for months, but now Cloudflare blocks the connection on port 8443, causing the SSL handshake to fail and the token mismatch.

@DubblePumper commented on GitHub (Jun 23, 2025): > You using a reverse proxy of any sorts? Yes, I run through the Cloudflare proxy (orange cloud) with WAF rules. In doing so, I use the Cloudflare SSL certificate (not Certbot). It worked smoothly for months, but now Cloudflare blocks the connection on port 8443, causing the SSL handshake to fail and the token mismatch.
OVERLORD commented 2026-02-05 17:30:09 +03:00
Author
Owner
Copy Link

@notAreYouScared commented on GitHub (Jun 23, 2025):

Then that's your issue, it's stripping request headers, therefore the panel thinks it's not talking to what it thinks it's talking to.

Sorr,y but this isn't an issue we will be willing to "fix" as it's not an issue with Pelican, it's an issue with your setup. Multiple people have also ran into this issue, please use the search function on the Discord to look at possible solutions.

@notAreYouScared commented on GitHub (Jun 23, 2025): Then that's your issue, it's stripping request headers, therefore the panel thinks it's not talking to what it thinks it's talking to. Sorr,y but this isn't an issue we will be willing to "fix" as it's not an issue with Pelican, it's an issue with your setup. Multiple people have also ran into this issue, please use the search function on the Discord to look at possible solutions.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
not confirmed
pull-request
Mirrored from GitHub Pull Request
 👑 sponsor
💰 fund
🔴 hard
🟡 medium
🟡 medium
🟡 medium
🟢 easy
🟢 easy
🟢 easy
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/panel-pelican-dev#365
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?