#Wings does not trust my panels SSL cert

17 messages · Page 1 of 1 (latest)

weary badge
#

i should add that logging into the panel works without issue and this is the wings config file

debug: false
uuid: uuid
token_id: example token_id
token: example token
api:
host: 0.0.0.0
port: 443
ssl:
enabled: false
cert: /etc/letsencrypt/live/panel.example.com/fullchain.pem
key: /etc/letsencrypt/live/panel.example.com/privkey.pem
upload_limit: 100
system:
data: /var/lib/pterodactyl/volumes
sftp:
bind_port: 2022
allowed_mounts: []
remote: 'https://panel.example.com'

novel isleBOT
weary badge
#

I should not need to create a cert if im supplying them myself via the reverse proxy. I have a wildcard cert for my domain

mental timber
#

This has nothing to do with the certificate you are supplying wings.
Its unable to verify the certificate at https://panel.example.com/

#

Is this wings running in docker ?

weary badge
#

yes using the docker compose from the link in my post

mental timber
#

comment out the - "/etc/ssl/certs:/etc/ssl/certs:ro" line and restart/rebuild the containers

#

See if that helps you

weary badge
#

ok!

#

now the error changed a little bit:

INFO: [Apr 18 23:00:07.683] loading configuration from file config_file=/etc/pterodactyl/config.yml

INFO: [Apr 18 23:00:07.683] configured wings with system timezone timezone=Europe/Stockholm

INFO: [Apr 18 23:00:07.684] configured system user successfully gid=988 uid=988 username=pterodactyl

INFO: [Apr 18 23:00:07.687] fetching list of servers from API

FATAL: [Apr 18 23:00:36.151] failed to load server configurations error=http: request creation failed: Get "https://panel.example.com/api/remote/servers?page=0&per_page=50": tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2025-04-18T23:00:36+02:00 is before 2025-04-18T21:24:47Z

novel isleBOT
weary badge
#

Is this the wings container that has the wrong time or is it the host machine running the wings docker container?

#

i synced the time on the host machine and now its not throwing any errors but when i checked in the panel this error is getting spammed in the console:

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https:/node.example.com/api/system. (Reason: CORS request did not succeed). Status code: (null).

novel isleBOT
#

@weary badge; Make sure that your Wings are running and reachable. This error usually happens when your browser can't reach Wings to verify the CORS headers. Click on the URL in the CORS error to verify it can be connected to without any errors.

weary badge
#

i can brows from the machine running the panel to the node no issue

#

does wings need to be behind a proxy as well since i can only brows using http to wings but do i need https?