what is this error: error: proto: (line 1:429): un...
# ask-ai
a
what is this error: error: proto: (line 1:429): unknown field \"restartPolicy\""
✅ 1
t
Thanks for reaching out, Sebastián. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.
Thanks — I’m looking at the error "error: proto: (line 1:429): unknown field \"restartPolicy\"". Could you tell me where you saw this error and what you were doing when it occurred? Specifically: • Which file or command produced the error (e.g., a YAML/JSON config, Kubernetes manifest, or a LiveKit config file)? • If it’s a file, can you paste the surrounding 8–12 lines (or the section containing
restartPolicy
)? • Which LiveKit version or deployment method are you using (self-hosted with Helm/docker-compose, or a hosted product)? With that I can identify whether
restartPolicy
is unsupported in the proto/schema you’re using and advise a fix or alternative. Sources: Self-hosted deployments | LiveKit Documentation, with interactive elements
a
is in self hosted and not sure why it started happening
t
Thanks — that helps. To diagnose why
restartPolicy
suddenly became an unknown proto field in your self-hosted setup, I need a couple quick details: • Which file produced the error (Kubernetes manifest, Helm values, docker-compose, or another config)? • Paste the 8–12 lines around where
restartPolicy
appears (or attach the file snippet). • Which LiveKit version and which deployment method (Helm chart version or docker-compose commit) are you running? • Any recent changes or upgrades you made before the error started (chart upgrade, Kubernetes version change, editing configs)? With those I can tell you whether
restartPolicy
is not allowed in that schema and recommend the exact change to fix it. , with interactive elements
a
i have this livekit self hosted unknown field \"restartPolicy\""
t
Thanks — I hear you. To fix this I need one small bit more info so I can point to the exact cause. Please tell me: • Which file or command produced the error (Kubernetes manifest, Helm values.yaml, docker-compose file, or another config)? • Paste the 8–12 lines around the
restartPolicy
entry (or attach the snippet). • Which LiveKit version and which deployment method (Helm chart version or docker-compose commit) are you running? • Any recent changes (chart/LiveKit upgrade, edited config, Kubernetes version change)? Once you share that snippet and the version info I’ll tell you whether
restartPolicy
is invalid for that schema and the exact change to fix it. , with interactive elements