#Mixed Content | SSL Protocol Error

1 messages · Page 1 of 1 (latest)

grizzled swan
#

Hello, Running into some issues. The SSL stuff really getting on my nerves, I am setting up a new install and have gotten to Setting up a new node.
I have messed with the setting based on the conversations here and nothing is working. Either running into SSL protocol error - no connection to Node or getting Mixed content error - able to connect but server consoles and other information not working.

https Proxy -> http Pterodactyl -> http Wings
Not Using Cloudflare

Wings and Panel both behind a Proxy but running on same system.
Port 8080 is forwarded to Host system (also tried forwarding to Proxy Host)

Errors:

{SSL OFF}
jquery.min.js?t={cache-version}:4 Mixed Content: The page at 'https://panel.site.com/admin/nodes' was loaded over HTTPS, but requested an insecure 
XMLHttpRequest endpoint 'http://panel.site.com:8080/api/system'. This request has been blocked; the content must be served over HTTPS.

{SSL ON}
GET https://panel.site.com:8080/api/system net::ERR_SSL_PROTOCOL_ERROR

Configs:
wings:

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

.ENV:

APP_ENV=production
APP_DEBUG=false
APP_THEME=pterodactyl
APP_URL="https://panel.site.com"
APP_LOCALE=en
APP_ENVIRONMENT_ONLY=false
DB_CONNECTION=mysql
DB_HOST=127.0.0.1
DB_PORT=3306
DB_DATABASE=panel
DB_USERNAME=pterodactyl
DB_PASSWORD=<REDACTED>
REDIS_HOST=127.0.0.1
REDIS_PASSWORD=null
REDIS_PORT=6379
CACHE_DRIVER=redis
QUEUE_CONNECTION=redis
SESSION_DRIVER=redis
TRUSTED_PROXIES=*
silk wraithBOT
#

There were too many logs to read @grizzled swan. Please post 5 or less. Alternatively, please share larger logs using paste sites, such as pteropaste or hastebin.

grizzled swan
silk wraithBOT
#

I have found the following for: https://pteropaste.com/15f5w9a6ab37
@grizzled swan It looks like you are having issues with connecting to Wings.

Make sure that your wings are running using systemctl status wings and that your Wings ports (by default 8080/2022) are open in your firewall or router. This website can check your ports https://dnschecker.org/port-scanner.php

Browser console errors can also provide additional debugging information. More troubleshooting steps can be found at https://pterodactyl.io/panel/1.0/troubleshooting.html#cannot-connect-to-server-errors

Should the panel and wings be located on the same network, you might experience NAT reflection issues. In that case, type .nat for more information.

#

Suppose you are having trouble connecting to a Panel or Node on the same network as your device, or Panel and Wings can't reach each other on the same network. In that case, you may have to edit your /etc/hosts file to point the domain to the local IP, as some routers don't handle NAT Loopback correctly, if at all. On Windows, this file is at C:\Windows\System32\Drivers\etc\hosts

192.168.1.24 panel.mydomain.com node1.mydomain.com
192.168.1.25 node2.mydomain.com
grizzled swan
silk wraithBOT
#

I have found the following for: https://ptero.co/ecuryzokun
@grizzled swan Your Panel has not been configured to listen on port 443 and use an HTTPS connection, or it's currently unreachable.

If your Panel is running and reachable on HTTPS, try restarting the failed-count systemctl reset-failed wings && systemctl restart wings. Otherwise, look into your web server status and its configuration to ensure SSL configuration is being used.

grizzled swan
#

attempted NAT Hosts suggestion, Caused issues. Wings log showing no errors after reverted. Just Showing Listening

subtle hedge
#

you cannot mix HTTP and HTTPS content, you need to either have both wings and panel on HTTP or on HTTPS

grizzled swan
#

Yes I understand that. But with http on both I get no server control panel.

With both https I get SSL error.

As the proxy is forwarding from https I believe.

Current:
https proxy nginx->http panel->http wings
Results in mixed error, no server panels.