I set up an HTTP service on my Runpod, but there are continuous WebSocket connection requests coming in. I want to understand why these requests are occurring and how to stop them. My service is being significantly disrupted by these requests.They seem to share the same internal IP and client ID: INFO: ('', 55730) - "WebSocket /ws?clientId=6d901a86659e4e78bfcc32b69bd5f68f" 403
INFO: connection rejected (403 Forbidden)
INFO: connection closed
INFO: ('100.64.0.32', 39206) - "WebSocket /ws?clientId=6d901a86659e4e78bfcc32b69bd5f68f" 403
INFO: connection rejected (403 Forbidden)
INFO: connection closed
INFO: ('100.64.0.35', 36208) - "WebSocket /ws?clientId=6d901a86659e4e78bfcc32b69bd5f68f" 403
INFO: connection rejected (403 Forbidden)
INFO: connection closed
INFO: ('', 33278) - "WebSocket /ws?clientId=6d901a86659e4e78bfcc32b69bd5f68f" 403
INFO: connection rejected (403 Forbidden)
INFO: connection closed
INFO: ('', 35990) - "WebSocket /ws?clientId=6d901a86659e4e78bfcc32b69bd5f68f" 403
INFO: connection rejected (403 Forbidden)
INFO: connection closed
INFO: ('', 46800) - "WebSocket /ws?clientId=6d901a86659e4e78bfcc32b69bd5f68f" 403
INFO: connection rejected (403 Forbidden)
INFO: connection closed
INFO: ('***********', 33096) - "WebSocket /ws?clientId=6d901a86659e4e78bfcc32b69bd5f68f" 403
INFO: connection rejected (403 Forbidden)
INFO: connection closed
#How to handle these WebSocket connections?
1 messages · Page 1 of 1 (latest)
@trail flare
The thread has been escalated to Zendesk!
maybe you should check with support too, they can check your pods too
Thank you for your concern. I have configured multiple ports, but each service is set up as an HTTP service using FastAPI, and the people calling the services are also invoking them through HTTP.
I have the same concern, but the good news is that, although I don’t know why, there are no more WebSocket requests coming in now.
Oh but when people connect form the external it doesn't appear in the logs like in your pasted text above right?
It comes from external ip? Or is it like above coming from internalnip
But maybe just a thought I think it's best to have runpod behind a proxy ( like you should connect runpod from a backend just to be more secure)