Yes. Don't know if it's related to the current "exploit" released recently. Maybe a Nginx proxy manager issue, which serves everything.
Discussion
If so and on nginx add
proxy_set_header X-Real-IP $remote_addr;
to your websocket location block. If using another reverse-proxy solution, just make sure your setting the X-Real-IP header.
Context: There was an exploit on strfry, this resolves it.
Thanks i'll try it. Do you know how I can test it? To be sure it's fixed? Could make a script after that to help People to troubleshoot easily.