https://livekit.io logo
Join Slack
Powered by
do I need to open port 8080 on my server which hos...
# ask-ai
f
do I need to open port 8080 on my server which hosts the agent
t
Thanks for reaching out, Palwisha. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.
Thanks — good question. Regarding opening port 8080 on the server that hosts the LiveKit agent: • You do not need to open port 8080 for the agent to work. The agent initiates outbound WebSocket connections to the LiveKit server, so no inbound port (like 8080) must be exposed for normal operation. • The agent may optionally expose a health-check HTTP endpoint, but by default that listens on 
<http://0.0.0.0:8081/>
, not 
:8080
. That health endpoint is optional and not required for the agent to function. If you have a custom configuration or another service on the same host that specifically requires port 8080, then opening it would be an application-specific decision — it is not required by LiveKit’s agent itself. Would you like me to check your agent config or show how to verify which ports your agent is listening on? Sources: Self-hosted deployments | LiveKit Documentation
f
sorry I meant 8081
t
Thanks for clarifying — about port 8081: • You do not need to open port 8081 for the LiveKit agent to function. The agent makes outbound WebSocket connections to LiveKit, so it does not require an inbound port to be exposed for normal operation. • The agent may optionally expose a health-check endpoint that by default listens on 
<http://0.0.0.0:8081/>
. That endpoint is optional and only needed if you want external monitoring or health probes to reach the agent. • If you want a load balancer, external monitor, or orchestration system to query the agent’s health endpoint, then you would open or forward port 8081 accordingly. Otherwise, leaving it closed is fine and more secure. Would you like instructions to verify whether your agent is currently listening on 8081 or help configuring a health check for your monitoring system?
2 Views
Open in Slack
PreviousNext
Powered by