issue with websocket (wss) port on runpods
hi there!
i’m working on a real-time sdxl example and have tried several times, but for some reason, the websocket (wss) port never works with runpods. it works fine with http, but not with wss. any help would be appreciated!
15 Replies
Move port from http to tcp as cloudflare proxy not support websocket
can you please elaborate?
move your app port from http ports to tcp ports in your template
yep, i did:
the flask server is running but still i can't connect to wss url
here is my code for a simple wss server:
you need to go to connect button and tcp maping and go to ip:port
thanks, found the ip and port but it doesn't connect via the ws.
and i don't see any error from the flask server
btw, the app works fine with google cloud server, not sure what could be the issue with runpods gpu, or i might be missing something
websocket over tcp should work fine
I found for websocket when using the RunPod proxy HTTP port you have to construct your wss URL like this:
PLEASE note the /ws on the end. Without it this will not work.
If you are using a TCP port then you will have to provide SSL and DNS for your worker to get the benefits of the underlying HTTPS required for wss.
@Encyrption hah I did not know about this one nice find
consider it my going away gift... LOL
going away?
Yeah, it seems RunPod cannot support the application I have been building. I am building an AI marketplace where users can come an run many models. Seems with RunPod I can either have a small amount of fast responding endpoints or I can have a lot of slow responding endpoints. I don't see a path to success with those limitations. 😦
Hmm how so? Fell free to send me some details
Sure, should I send via DM?
ok