#Having issue migrating from no ssl to cloudflare ssl (Getting websocket error)

1 messages · Page 1 of 1 (latest)

vague slate
#

So I recently tried to move my panel into a FDQN domain, and after some hard struggle i managed to get cloudflare ssl to work with my panel and setup nginx correctly.
I can access my panel but now im getting other error.
Im not getting websocket error saying server is trying to connect through ws instead of wss while accessing pterodactyl api

How do i fix this?

hollow token
#

You MUST use SSL (and a domain) for you node since you're using SSL for your panel

vague slate
#

when i go to to do that in admin panel i get 500
Server Error

#

and in config.yml file i enabled ssl

#

and rebooted too

hollow token
main streamBOT
hollow token
vague slate
#

i see

hollow token
#

Fix your log file perms, then you can change the nodes settings to enable SSL

vague slate
#

uhh idk if im being dumb
but even after i set connection to ssl
it says this
The daemon configuration has been updated, however there was an error encountered while attempting to automatically update the configuration file on the Daemon. You will need to manually update the configuration file (config.yml) for the daemon to apply these changes.

and in the configuration tab it shows ssl disabled

#

ok i was being dumb its setup but now uhh im getting this error ;-;

bundle.9ec609ab.js:95 WebSocket is already in CLOSING or CLOSED state.
bundle.9ec609ab.js:95 WebSocket connection to 'wss://pi.sharkdev.us.to:8080/api/servers/7bde87e4-a805-44dc-9422-050e05420cb5/ws' failed: 
bundle.9ec609ab.js:95 WebSocket is already in CLOSING or CLOSED state.
bundle.9ec609ab.js:95 WebSocket connection to 'wss://pi.sharkdev.us.to:8080/api/servers/7bde87e4-a805-44dc-9422-050e05420cb5/ws' failed: 
bundle.9ec609ab.js:95 WebSocket is already in CLOSING or CLOSED state.
bundle.9ec609ab.js:95 WebSocket connection to 'wss://pi.sharkdev.us.to:8080/api/servers/7bde87e4-a805-44dc-9422-050e05420cb5/ws' failed: WebSocket is closed before the connection is established.
hollow token
#

You put cloudflare in front of a service without knowing how to use it properly, or reading our docs

#

This also isn't Jexactyl support

vague slate
vague slate
hollow token
#

Clearly missed the docs that specifically call out configuration behind cloudflare....