Can't setup wings, failed to retrieve server configurations

[enxg]

When I try to start wings I get the following error:

DEBUG: [Jun 11 17:03:30.062] making request to external HTTP endpoint endpoint=https://<domain>/api/remote/servers?page=0&per_page=50 headers=map[Accept:[application/vnd.pterodactyl.v1+json] Authorization:[(redacted)] Content-Type:[application/json] User-Agent:[Pterodactyl Wings/v1.11.6 (id:DZpXcgOR8AAZ2Zhx)]] method=GET
FATAL: [Jun 11 17:03:30.102] failed to load server configurations error=manager: failed to retrieve server configurations: Error response from Panel: _MissingResponseCode: No error response returned from API endpoint. (HTTP/403)

I sent the same request in Insomnia using the token from config.yml and received this

When I tried using auto-deploy from the panel, after running the command I got this

? Override existing configuration file Yes
map[Accept:[application/vnd.pterodactyl.v1+json] Authorization:[Bearer ******] Content-Type:[application/json]]https://<domain>/api/application/nodes/3/configurationThe authentication credentials provided were not valid.

However when I send the same request myself, I get a response

I'm using the docker compose file from this repo for the panel (just changed the ports, 80 is bound to 7000, we removed 443), panel is reverse proxied with nginx using the following config:

server {

  listen 443 ssl;

  ssl on;
  ssl_certificate /etc/ssl/cert.pem;
  ssl_certificate_key /etc/ssl/cert.key;


  server_name <domain>;


  location / {

      proxy_pass http://127.0.0.1:7000;
      # proxy_set_header Host $host;
      client_max_body_size 50m;
      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
      
      proxy_set_header X-Real-IP $remote_addr;
      proxy_set_header Host $host;
      proxy_set_header X-Forwarded-Proto $scheme;
      proxy_redirect off;
      proxy_buffering off;
      proxy_request_buffering off;

  }

}

Wings is running on a VPS from OVH.

I can't figure out what's going on, can you help me with this?

[enxg]

Solved after whitelisting the IP from Cloudflare WAF.