kenzuya/unshackle
1
0
Fork 2
mirror of https://github.com/unshackle-dl/unshackle.git synced 2026-11-13 12:35:05 +00:00
Code Issues Packages Projects Releases Wiki Activity

Deployed 83514d1 with MkDocs version: 1.6.1

Browse Source
This commit is contained in:
2026-10-24 02:23:34 +00:00
parent e7481646f7
commit cafc0c20b8
8 changed files with 676 additions and 681 deletions
Download Patch File Download Diff File Expand all files Collapse all files
dev/rest-api/authentication/index.html
+1 -1
View File
@@ -2509,7 +2509,7 @@
<div class="admonition warning">
<p class="admonition-title">The server will not start without a key</p>
<p>If you start <code>unshackle serve</code> with no <code>api_secret</code> configured, and you have <em>not</em> passed <code>--no-key</code>, the command fails immediately with:</p>
<div class="language-text highlight"><pre><span></span><code><span id="__span-2-1"><a id="__codelineno-2-1" name="__codelineno-2-1" href="#__codelineno-2-1"></a>API secret key is not configured. Please add 'api_secret' to the 'serve' section in your config.
<div class="language-text highlight"><pre><span></span><code><span id="__span-2-1"><a id="__codelineno-2-1" name="__codelineno-2-1" href="#__codelineno-2-1"></a>No 'api_secret' in the 'serve' section of your config
</span></code></pre></div>
<p>Choose a long, unpredictable value. The API key is the only thing standing between the internet and your CDM and download endpoints.</p>
</div>
dev/rest-api/remote-sessions/index.html
+1 -1
View File
@@ -3173,7 +3173,7 @@ remote session API and a good template for any client.</p>
<hr />
<h2 id="troubleshooting">Troubleshooting<a class="headerlink" href="#troubleshooting" title="Permanent link">&para;</a></h2>
<div class="admonition example">
<p class="admonition-title">\"Could not connect to remote server ... Is it running?\"</p>
<p class="admonition-title">\"Could not connect to remote server at ...\"</p>
<p>The client could not reach the URL. Make sure that <code>unshackle serve</code> operates on
the server, the <code>url</code>/port in <code>remote_services</code> are correct (default port <code>8786</code>),
and any firewall or reverse proxy allows the connection.</p>