<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Meharab Islam Nibir</title>
    <description>The latest articles on DEV Community by Meharab Islam Nibir (@meharab_islamnibir_9a5b4).</description>
    <link>https://dev.to/meharab_islamnibir_9a5b4</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4094276%2F8a5da834-6751-4264-bc90-787e8e30ec94.jpeg</url>
      <title>DEV Community: Meharab Islam Nibir</title>
      <link>https://dev.to/meharab_islamnibir_9a5b4</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/meharab_islamnibir_9a5b4"/>
    <language>en</language>
    <item>
      <title>Self-hosted LiveKit rooms automatically closing after 2-3 minutes (Phantom API calls from backend)</title>
      <dc:creator>Meharab Islam Nibir</dc:creator>
      <pubDate>Tue, 25 Aug 2026 13:33:01 +0000</pubDate>
      <link>https://dev.to/meharab_islamnibir_9a5b4/self-hosted-livekit-rooms-automatically-closing-after-2-3-minutes-phantom-api-calls-from-backend-2g77</link>
      <guid>https://dev.to/meharab_islamnibir_9a5b4/self-hosted-livekit-rooms-automatically-closing-after-2-3-minutes-phantom-api-calls-from-backend-2g77</guid>
      <description>&lt;p&gt;I am experiencing an unexpected issue with my self-hosted LiveKit server. I am using a Flutter app for the frontend and a Laravel backend for room management and token generation.&lt;/p&gt;

&lt;p&gt;To be honest, I don't know exactly which code is causing the problem, which is why I can't provide a minimal reproducible example (MRE). It seems to be a strange production environment issue rather than a simple code bug.&lt;/p&gt;

&lt;p&gt;The Issue:&lt;br&gt;
My app ran perfectly in production for 4 months without any issues. However, for the past 2 days, any newly created room only stays active for about 2-3 minutes. After this short time, all participants are forcefully removed/disconnected, and the room automatically closes.&lt;/p&gt;

&lt;p&gt;What I have tried &amp;amp; Log observations:&lt;/p&gt;

&lt;p&gt;I completely wiped my VPS, re-uploaded my backend code, and did a fresh installation of the LiveKit server.&lt;/p&gt;

&lt;p&gt;After the fresh install, everything worked perfectly for about 10-12 hours. But after that period, the exact same issue returned.&lt;/p&gt;

&lt;p&gt;I investigated the LiveKit logs and found that API requests for 'remove participant' and 'close room' are being triggered from my backend.&lt;/p&gt;

&lt;p&gt;The confusing part: My Laravel backend has absolutely NO logic or endpoints written by me that trigger these specific API calls to remove participants or close rooms.&lt;/p&gt;

&lt;p&gt;Expected behavior:&lt;br&gt;
The room should remain active as long as there are connected participants or until it is explicitly closed via the backend API. Participants should not be randomly disconnected after a few minutes.&lt;/p&gt;

&lt;p&gt;Steps to reproduce:&lt;/p&gt;

&lt;p&gt;Create a room via the Laravel backend.&lt;/p&gt;

&lt;p&gt;Join the room using the Flutter livekit_client SDK.&lt;/p&gt;

&lt;p&gt;Wait for 2-3 minutes.&lt;/p&gt;

&lt;p&gt;Observe that all participants are suddenly disconnected and the room is closed on the server.&lt;/p&gt;

&lt;p&gt;Since the logs show these calls coming from my backend, but my codebase doesn't initiate them, how can I trace what is making these phantom calls? Could this be related to a token expiration, a background worker, or a compromised server issue? Any guidance on debugging this would be highly appreciated.&lt;/p&gt;

</description>
      <category>livekit</category>
    </item>
  </channel>
</rss>
