Websocket connection attempt results in 403 about pterojs HOT 5 CLOSED

I ran into similar issue on StackOverflow, however author doesn't seem to use this library:
https://stackoverflow.com/questions/70748325/403-forbidden-when-connecting-to-pterodactyl-websocket

I'm also using node v17, didn't think to test other versions

from pterojs.

If I remember correctly, 403 can mean that the API key is invalid (using an application API key instead of a client API key), or the origin of the websocket request is not whitelisted. The latter is not under PteroJS' control, cross_origin in the Wings configuration needs to include your IP or "*" (allows all origins) for it to work.

from pterojs.

All other methods work just fine, only the websocket one gives 403 error right after connect()ion. Should I go ping Pteroteam then?

from pterojs.

No, if you have access to Wings for the node you're using then set allowed_origins in "config.yml" to this:

allowed_origins:
  - "*"

Otherwise, contact your panel administrator about it.

from pterojs.

Thanks! Didn't think that it works this way, I thought panel is acting like proxy in this case, 403 error is fixed now. However no output is forwarded to my on listener:

However that's a story for another issue if I don't solve the problem myself. Thanks once more!

from pterojs.