<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>OpenClaw on miti99</title><link>https://miti99.com/en/tags/openclaw/</link><description>Recent content in OpenClaw on miti99</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 16 Nov 2026 17:39:19 +0700</lastBuildDate><atom:link href="https://miti99.com/en/tags/openclaw/index.xml" rel="self" type="application/rss+xml"/><item><title>Fixing 'Pairing Required' When Connecting to OpenClaw via Docker</title><link>https://miti99.com/en/post/2026/04/05/</link><pubDate>Sun, 05 Apr 2026 00:00:00 +0700</pubDate><guid>https://miti99.com/en/post/2026/04/05/</guid><description>&lt;p&gt;If you&amp;rsquo;re self-hosting &lt;a href="https://github.com/open-claw/open-claw" rel="noopener noreferrer"&gt;OpenClaw&lt;/a&gt; with Docker and run into the &lt;strong&gt;&amp;ldquo;disconnected (1008): pairing required&amp;rdquo;&lt;/strong&gt; error when accessing it from your browser, this post will help you fix it quickly.&lt;/p&gt;
&lt;h2 id="problem"&gt;Problem&lt;/h2&gt;&lt;p&gt;After setting up OpenClaw with Docker on Ubuntu, the browser shows:&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;disconnected (1008): pairing required
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Trying to use the CLI to approve the device then fails with &lt;strong&gt;&amp;ldquo;gateway token mismatch&amp;rdquo;&lt;/strong&gt; — the CLI inside the Docker container doesn&amp;rsquo;t properly resolve the authentication token from the config file.&lt;/p&gt;
&lt;h2 id="cause"&gt;Cause&lt;/h2&gt;&lt;p&gt;There is an authentication token mismatch between the host and the Docker container. The CLI inside the container fails to read the right token from &lt;code&gt;openclaw.json&lt;/code&gt;, which prevents it from listing or approving devices.&lt;/p&gt;
&lt;h2 id="how-to-fix"&gt;How to Fix&lt;/h2&gt;&lt;h3 id="step-1-get-the-gateway-token-from-the-host"&gt;Step 1: Get the Gateway Token from the Host&lt;/h3&gt;&lt;div class="highlight"&gt;&lt;div class="chroma"&gt;
&lt;table class="lntable"&gt;&lt;tr&gt;&lt;td class="lntd"&gt;
&lt;pre tabindex="0" class="chroma"&gt;&lt;code&gt;&lt;span class="lnt"&gt;1
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;
&lt;td class="lntd"&gt;
&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;cat ~/.openclaw/openclaw.json &lt;span class="p"&gt;|&lt;/span&gt; grep -A5 &lt;span class="s1"&gt;&amp;#39;&amp;#34;auth&amp;#34;&amp;#39;&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;p&gt;Copy the token value under &lt;code&gt;gateway.auth&lt;/code&gt;.&lt;/p&gt;
&lt;h3 id="step-2-check-the-token-inside-the-container"&gt;Step 2: Check the Token Inside the Container&lt;/h3&gt;&lt;div class="highlight"&gt;&lt;div class="chroma"&gt;
&lt;table class="lntable"&gt;&lt;tr&gt;&lt;td class="lntd"&gt;
&lt;pre tabindex="0" class="chroma"&gt;&lt;code&gt;&lt;span class="lnt"&gt;1
&lt;/span&gt;&lt;span class="lnt"&gt;2
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;
&lt;td class="lntd"&gt;
&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;docker ps &lt;span class="c1"&gt;# Get the CONTAINER_ID of openclaw-gateway&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;docker &lt;span class="nb"&gt;exec&lt;/span&gt; -it &amp;lt;CONTAINER_ID&amp;gt; cat /home/node/.openclaw/openclaw.json &lt;span class="p"&gt;|&lt;/span&gt; grep -A5 &lt;span class="s1"&gt;&amp;#39;&amp;#34;auth&amp;#34;&amp;#39;&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;p&gt;Verify whether the token on the host matches the one inside the container.&lt;/p&gt;
&lt;h3 id="step-3-list-devices-with-a-token-override"&gt;Step 3: List Devices with a Token Override&lt;/h3&gt;&lt;p&gt;Inject the token directly via the &lt;code&gt;-e&lt;/code&gt; environment variable flag when running the command in the container:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;div class="chroma"&gt;
&lt;table class="lntable"&gt;&lt;tr&gt;&lt;td class="lntd"&gt;
&lt;pre tabindex="0" class="chroma"&gt;&lt;code&gt;&lt;span class="lnt"&gt;1
&lt;/span&gt;&lt;span class="lnt"&gt;2
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;
&lt;td class="lntd"&gt;
&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;docker &lt;span class="nb"&gt;exec&lt;/span&gt; -e &lt;span class="nv"&gt;OPENCLAW_GATEWAY_TOKEN&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&amp;lt;YOUR_TOKEN&amp;gt; -it &amp;lt;CONTAINER_ID&amp;gt; &lt;span class="se"&gt;\
&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; openclaw devices list
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;p&gt;This command will display the list of devices waiting for approval along with their &lt;strong&gt;Request ID&lt;/strong&gt;.&lt;/p&gt;
&lt;h3 id="step-4-approve-the-device"&gt;Step 4: Approve the Device&lt;/h3&gt;&lt;div class="highlight"&gt;&lt;div class="chroma"&gt;
&lt;table class="lntable"&gt;&lt;tr&gt;&lt;td class="lntd"&gt;
&lt;pre tabindex="0" class="chroma"&gt;&lt;code&gt;&lt;span class="lnt"&gt;1
&lt;/span&gt;&lt;span class="lnt"&gt;2
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;
&lt;td class="lntd"&gt;
&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;docker compose &lt;span class="nb"&gt;exec&lt;/span&gt; openclaw-gateway &lt;span class="se"&gt;\
&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; openclaw devices approve &amp;lt;REQUEST_ID&amp;gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;h3 id="step-5-verify-the-result"&gt;Step 5: Verify the Result&lt;/h3&gt;&lt;p&gt;Reload &lt;code&gt;http://localhost:18789&lt;/code&gt; in your browser — the pairing error will be gone.&lt;/p&gt;
&lt;h2 id="note"&gt;Note&lt;/h2&gt;&lt;p&gt;The key to this fix is injecting the token via an environment variable (&lt;code&gt;-e OPENCLAW_GATEWAY_TOKEN=...&lt;/code&gt;) rather than passing it as a command-line flag, because the CLI inside Docker doesn&amp;rsquo;t handle the token flag properly.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.linkedin.com/pulse/fixing-openclaw-dockers-pairing-required-dead-end-ubuntu-rik-banerjee-j09de/" rel="noopener noreferrer"&gt;Fixing OpenClaw Docker&amp;rsquo;s &amp;ldquo;Pairing Required&amp;rdquo; Dead End on Ubuntu - Rik Banerjee&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</description></item></channel></rss>