Server-Client binding address conflict #390
Replies: 5 comments
-
Hey @BlueKiji77 I think the problem is 8000 is also the default port for Chainlit 😅 try putting |
Beta Was this translation helpful? Give feedback.
-
Doesn't work. I get the same error regardless of the port I set the client and server to listen to. Also assigning different port to both the client and the server (8080, 8005) doesn't work either as one might guess. |
Beta Was this translation helpful? Give feedback.
-
Seems like something on your system must be conflicting with the port though. You get the exact same error even after changing the port? |
Beta Was this translation helpful? Give feedback.
-
Yes. Changed port for both client and server to another one, I also tried to set both to different ports without success. I am working inside Lightning AI Studios |
Beta Was this translation helpful? Give feedback.
-
@BlueKiji77 we can't help much without looking at the logs and the code, can you post any self-contained example I can use to reproduce? |
Beta Was this translation helpful? Give feedback.
-
Trying to launch an app with server-client architecture using llama-deploy but I keep running into port conflict between server and client.
Sorry if this seems obvious, I am new to this.
###LAUNCHING SERVER FROM TERMINAL
###LAUNCHING CLIENT FROM TERMINAL
Server Deployment Code Snippet
Client Code Snippet
Beta Was this translation helpful? Give feedback.
All reactions