search

revoltchat / self-hosted

Deploy Revolt using Docker.
904 stars 116 forks source link

bug: serving pterodactyl behind reverse proxy causes DOMException: The operation is insecure. #71

Closed KenwoodFox closed 6 months ago

KenwoodFox commented 10 months ago

What happened?

I am getting an issue really similar to https://github.com/revoltchat/self-hosted/issues/10 , when loading a web page, I cant control or really.. do anything, server controls don't work and I get the The operation is insecure. error.

I think its because I'm hosting the pterodactyl server over HTTP, and then proxying it + adding my SSL cert afterward. I looked around, and the cause makes sense. because I actually am hosting the server over HTTP, it confuses the server and doesn't accept URLs beginning with https?

I'm thinking maybe I'll self sign some certs and just host it over https internally? it sounds kinda silly but i could do that? Is there an easier way? a config setting for when you're using a reverse proxy?

let me know if there is any more info i can provide.

KenwoodFox commented 10 months ago

Ah... using chrome produces some more helpful debug. image that IP, 10.85.3.103 is the direct connection to the wing. It cant do that, I'm surprised. I had thought I had forbidden that path.

Is this how pterodactyl works? Do I need to make my wings accessible externally too? that would certainly make it more involved for me to provide a subdomain for every wing..

new discovery: path is blocked, it couldn't connect even if it wanted to, that's a local IP. image

KenwoodFox commented 10 months ago

Behind proxy is set... but still same error? im struggling to setup a self-signed cert haha.. this is why i centralize all my certs on my reverse proxy in the first place, https://pterodox.com/guides/reverse-proxy.html#for-wings

insertish commented 6 months ago

Sir, this is Revolt

Closing out for unrelated issue