#Error connecting to node check browser console for details

1 messages · Page 1 of 1 (latest)

proven ginkgoBOT
covert robin
polar hatch
#

Are you using an IP as FQDN for the node?

orchid trout
#

Oh wait nvm

#

Read what the bot said

covert robin
#

I should have explained that the panel is sat behind a caddy reverse proxy

#

This is why I'm using local IPs because caddy handles my certificates

floral crown
#

sign a cert for your wings too ig

ornate vault
# covert robin I'm using a local IP as FQDN for both panel and node

its a bit rudimentary and im sure you could have wings proxied through your reverse proxy, but what I did was I created an unproxied record on my domain to my server (if you dont use cloudflare you can ignore this), and i installed a cert specifically for that subdomain

#

then i think what you do is you set enable ssl in the node settings, change the fqdn to the subdomain, change port to right port, and then you go to the wingws config to make sure that the cert path is in the right spot. if you used certbot it should be right already

#

it might be a bit confusing, feel free to dm me

covert robin
#

Okay so I stopped caddy obtaining certificates and now the certs obtained on the panel/node server. This seems to have fixed the "This request has been blocked; the content must be served over HTTPS. "error I was getting. But now I'm getting an error when I try to make a game server.

proven ginkgoBOT
covert robin
#

This is the error from the browser console "WebSocket connection to '<URL>' failed: WebSocket is closed before the connection is established."