mirror of
https://github.com/unshackle-dl/unshackle.git
synced 2026-11-16 14:05:10 +00:00
Compare commits
3
Commits
cfe6d407c0
...
532ceaba46
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
532ceaba46 | ||
|
|
1fbec8c9d5 | ||
|
|
a1e65b3e4b |
@@ -2556,8 +2556,8 @@
|
||||
<p>If a user entry omits <code>playready_devices</code>, the server gives that API key <strong>no</strong> PlayReady access, and logs a warning at startup. You must name the PlayReady devices explicitly for any API key that needs them. Widevine and PlayReady device files themselves are auto-loaded from your WVDs and PRDs directories.</p>
|
||||
</div>
|
||||
<div class="admonition note">
|
||||
<p class="admonition-title">Device lists <em>are</em> the server-side-decryption switch</p>
|
||||
<p>There is no separate tier, capability flag, or permission toggle for whether the server will hand back content keys (<code>KID:KEY</code>) for a remote session download. The presence of devices on the calling API key decides it. With <strong>empty</strong> <code>devices</code> and <code>playready_devices</code>, the server can only proxy CDM challenges, so the client must operate its own CDM. Once those lists are <strong>populated</strong>, the client may request <code>mode:server_cdm</code> and receive content keys back. Do not look for a tier setting. The devices you configure are what enables server-side decryption.</p>
|
||||
<p class="admonition-title">Grants decide whether the server returns content keys</p>
|
||||
<p>The devices on an API key decide which CDM the server can use. Two grants in the same user entry decide whether the server returns content keys (<code>KID:KEY</code>) for a remote session. <code>server_cdm</code> lets the server license with those devices. <code>server_vault</code> lets a remote session that the client's own device licenses read the server vault, and the server then makes no live licence. Without either grant, the server can only proxy CDM challenges, so the client must operate its own CDM. See <a href="../../../reference/configuration/services/"><code>serve</code></a> for both grants.</p>
|
||||
</div>
|
||||
<h3 id="disabling-authentication">Disabling authentication<a class="headerlink" href="#disabling-authentication" title="Permanent link">¶</a></h3>
|
||||
<p>The <code>--no-key</code> flag turns authentication off entirely. The server allows every request, ignores <code>X-Secret-Key</code>, and needs no API key in your configuration.</p>
|
||||
|
||||
@@ -2444,7 +2444,7 @@ but the defaults hold for the overwhelming majority of responses.</p>
|
||||
<tr>
|
||||
<td><code>SERVER_CDM_CAPPED</code></td>
|
||||
<td>403</td>
|
||||
<td>The server CDM does not license live above the <code>server_cdm_max_height</code> of the API key. <code>details.reason</code> is <code>server_cdm_max_height</code> (with <code>details.max_height</code>) or <code>client_device</code>, for a remote session where the client's own device licenses. A remote client licenses the track with its own device.</td>
|
||||
<td>The server CDM does not license live above the <code>server_cdm_max_height</code> of the API key. <code>details.reason</code> is <code>server_cdm_max_height</code> (with <code>details.max_height</code>), <code>client_device</code>, for a remote session where the client's own device licenses, or <code>server_device</code>, for a remote session that runs on the server's device. A remote client licenses the track with its own device, except for <code>server_device</code>: then only its own vaults can supply the key.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>GEOFENCE</code></td>
|
||||
|
||||
@@ -1737,6 +1737,23 @@
|
||||
</span>
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="Server-side vs. proxied CDM">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#your-own-device-identity" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Your own device identity
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
@@ -2214,6 +2231,23 @@
|
||||
</span>
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="Server-side vs. proxied CDM">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#your-own-device-identity" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Your own device identity
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
@@ -2574,7 +2608,8 @@ request returns the updated cache files (for example a refreshed token) and the
|
||||
client saves them locally, so the <strong>next</strong> remote session can skip interactive
|
||||
authentication. The login belongs to the client when the client sent
|
||||
cookies, credentials, or cache files, or answered a login prompt (a device code
|
||||
or an OTP) that led to a successful login. A server-account login never does.
|
||||
or an OTP) that led to a successful login. A server-account login never does,
|
||||
and neither does a remote session on the server's device (see below).
|
||||
The client saves only the returned files that pass the same profile check it
|
||||
applies before it sends them, so a file for another profile cannot overwrite
|
||||
that profile's local file.</p>
|
||||
@@ -2604,6 +2639,10 @@ the raw license bytes come back for your local CDM to parse.</p>
|
||||
<ul>
|
||||
<li>Keeps your CDM local. The server only relays the license request.</li>
|
||||
<li>Used when <code>server_cdm</code> is <code>false</code> (the default).</li>
|
||||
<li>The service on the server sees your device, not the server's: its DRM system,
|
||||
security level, system ID and device type. A CDM call that the service makes
|
||||
(for example a session-key exchange at login) goes to your client as a <code>cdm_call</code>,
|
||||
and your local CDM answers it. See <a href="#your-own-device-identity">Your own device identity</a>.</li>
|
||||
</ul>
|
||||
</div>
|
||||
<div class="tabbed-block">
|
||||
@@ -2640,6 +2679,47 @@ server CDM licence answers <code>403 SERVER_CDM_CAPPED</code> for such a track.
|
||||
licenses those tracks in proxy mode with its own local CDM. See
|
||||
<a href="../../../reference/configuration/services/"><code>server_cdm_max_height</code></a>.</p>
|
||||
</div>
|
||||
<h3 id="your-own-device-identity">Your own device identity<a class="headerlink" href="#your-own-device-identity" title="Permanent link">¶</a></h3>
|
||||
<p>A service can need more than a licence challenge from your device: an ESN, model keys, or a
|
||||
session-key exchange that runs on the CDM. The device never leaves your machine. Only these cross
|
||||
the wire:</p>
|
||||
<ul>
|
||||
<li><strong>Device facts.</strong> When it creates the remote session, the client sends its DRM system, security level,
|
||||
system ID and device type. The service sees a stand-in with these facts.</li>
|
||||
<li><strong>CDM calls.</strong> When the service calls the CDM, the server sends a <code>cdm_call</code> to the client
|
||||
and waits. The client makes the challenge, or parses the licence, on its own CDM. When
|
||||
the service closes a CDM session, the server sends a <code>close</code> call, because a CDM holds
|
||||
only a few sessions. The client polls for calls during login and while one of its own
|
||||
requests runs service code, so an idle remote session sends nothing extra.</li>
|
||||
<li><strong>Session keys only.</strong> A <code>keys</code> call returns Widevine <code>OPERATOR_SESSION</code> and <code>SIGNING</code>
|
||||
keys. It never returns a content key, and the client refuses a PlayReady <code>keys</code> call.
|
||||
So a server cannot use your device to license titles for itself.</li>
|
||||
<li><strong>Identity config.</strong> A service names the config keys a client may send (for example
|
||||
<code>esn</code>, <code>Kpe</code>, <code>Kph</code>, <code>esn_map</code>). The server lists them in the service listing as
|
||||
<code>client_config</code>. The client sends only those keys, from its own <code>services: <TAG>:</code>
|
||||
block in <code>unshackle.yaml</code>. When the client sends an identity, the server drops its own
|
||||
value for each of those keys, so the two identities never mix. A mapping (such as
|
||||
<code>esn_map</code>) merges the client's entries over the server's. A client entry replaces a
|
||||
server entry with the same key, also when the server's key is a number. The server keeps
|
||||
these values in the remote session's memory only.</li>
|
||||
</ul>
|
||||
<p>A service can also offer an option that builds the remote session on the server's own
|
||||
device and identity, for the quality that device reaches. The session then makes no live
|
||||
licence at all: each content key comes from the server vault or the client's own vaults,
|
||||
and a content key that no vault holds stops the download with an error. The create
|
||||
response sets <code>server_device</code> to <code>true</code> for such a remote session. The service then uses
|
||||
the server's own config: the client's identity values do not apply. The client reads the
|
||||
server vault only when the API key has the <code>server_vault</code> grant (or <code>server_cdm</code>); without
|
||||
it, the client reads only its own vaults. The login tokens of such a remote session hold the
|
||||
server's device identity, so the server keeps them: <code>DELETE</code> returns no cache files, and the
|
||||
HTTP session headers and <code>track.data</code> lose their secret-looking keys, as for a server login.</p>
|
||||
<div class="admonition note">
|
||||
<p class="admonition-title">The server vault in a session your device licenses</p>
|
||||
<p>With the <code>server_vault</code> grant (or <code>server_cdm</code>) on the API key, a remote session that your own
|
||||
device licenses still takes content keys from the server vault. The server tries the
|
||||
vault first. A track that no server vault holds goes back to your device. See
|
||||
<a href="../../../reference/configuration/services/"><code>server_vault</code></a>.</p>
|
||||
</div>
|
||||
<hr />
|
||||
<h2 id="remote-session-lifecycle-and-expiry">Remote session lifecycle and expiry<a class="headerlink" href="#remote-session-lifecycle-and-expiry" title="Permanent link">¶</a></h2>
|
||||
<p>Remote sessions live in an <strong>in-memory store on the server</strong> and expire on a timer. You
|
||||
@@ -2799,8 +2879,10 @@ from a browser origin, not when you want only the local HTTP API.</p>
|
||||
<p><code>POST /api/session/create</code> requires <code>service</code> and <code>title_id</code>. It also accepts
|
||||
<code>credentials</code>, <code>cookies</code> (base64 of zlib-compressed Netscape cookie file), <code>proxy</code>,
|
||||
<code>no_proxy</code>, <code>profile</code>, <code>cache</code> (a map of <code>filename → base64(zlib(bytes))</code>),
|
||||
<code>client_region</code>, <code>cdm_type</code>, <code>client</code> (a freeform identity object the dashboard
|
||||
shows as sent), and the track-selection hints <code>range_</code>, <code>vcodec</code>,
|
||||
<code>client_region</code>, <code>cdm_type</code>, <code>cdm_security_level</code>, <code>cdm_relay</code> (<code>true</code> when the client
|
||||
answers CDM calls), <code>cdm_system_id</code> and <code>cdm_device_type</code> (Widevine only), <code>service_config</code>
|
||||
(the identity config keys the service lists in <code>client_config</code>), <code>client</code> (a freeform identity
|
||||
object the dashboard shows as sent), and the track-selection hints <code>range_</code>, <code>vcodec</code>,
|
||||
<code>quality</code>, <code>best_available</code>, plus arbitrary service CLI options
|
||||
(<code>additionalProperties: true</code>).</p>
|
||||
<p><code>dl_params</code> holds the <code>dl</code> track selection: <code>lang</code>, <code>v_lang</code> and <code>a_lang</code>
|
||||
@@ -2823,8 +2905,12 @@ the client sends and gets back belong to that profile. A service can also use
|
||||
the name to select per-profile entries in the server's service config, such as
|
||||
a per-profile ESN.</p>
|
||||
<p>The response returns <strong>before</strong> authentication finishes:</p>
|
||||
<div class="language-json highlight"><pre><span></span><code><span id="__span-6-1"><a id="__codelineno-6-1" name="__codelineno-6-1" href="#__codelineno-6-1"></a><span class="p">{</span><span class="w"> </span><span class="nt">"session_id"</span><span class="p">:</span><span class="w"> </span><span class="s2">"...uuid4..."</span><span class="p">,</span><span class="w"> </span><span class="nt">"service"</span><span class="p">:</span><span class="w"> </span><span class="s2">"EXAMPLE"</span><span class="p">,</span><span class="w"> </span><span class="nt">"status"</span><span class="p">:</span><span class="w"> </span><span class="s2">"authenticating"</span><span class="w"> </span><span class="p">}</span>
|
||||
<div class="language-json highlight"><pre><span></span><code><span id="__span-6-1"><a id="__codelineno-6-1" name="__codelineno-6-1" href="#__codelineno-6-1"></a><span class="p">{</span><span class="w"> </span><span class="nt">"session_id"</span><span class="p">:</span><span class="w"> </span><span class="s2">"...uuid4..."</span><span class="p">,</span><span class="w"> </span><span class="nt">"service"</span><span class="p">:</span><span class="w"> </span><span class="s2">"EXAMPLE"</span><span class="p">,</span><span class="w"> </span><span class="nt">"status"</span><span class="p">:</span><span class="w"> </span><span class="s2">"authenticating"</span><span class="p">,</span>
|
||||
</span><span id="__span-6-2"><a id="__codelineno-6-2" name="__codelineno-6-2" href="#__codelineno-6-2"></a><span class="w"> </span><span class="nt">"server_cdm"</span><span class="p">:</span><span class="w"> </span><span class="kc">false</span><span class="p">,</span><span class="w"> </span><span class="nt">"server_cdm_max_height"</span><span class="p">:</span><span class="w"> </span><span class="kc">null</span><span class="p">,</span><span class="w"> </span><span class="nt">"server_vault"</span><span class="p">:</span><span class="w"> </span><span class="kc">true</span><span class="p">,</span><span class="w"> </span><span class="nt">"server_device"</span><span class="p">:</span><span class="w"> </span><span class="kc">false</span><span class="w"> </span><span class="p">}</span>
|
||||
</span></code></pre></div>
|
||||
<p><code>server_vault</code> tells the client that the server vault serves a remote session its own device
|
||||
licenses. <code>server_device</code> tells it that the service runs on the server's device, so every
|
||||
content key comes from a vault.</p>
|
||||
<p>Authentication runs on a background thread (<code>asyncio.to_thread(authenticate, ...)</code>).
|
||||
The remote session starts in <code>AUTHENTICATING</code>. The client must poll the prompt
|
||||
endpoint until it reaches <code>authenticated</code> (or <code>failed</code>).</p>
|
||||
@@ -2840,6 +2926,10 @@ layer.</p>
|
||||
<li>A prompt after authentication (in <code>get_titles()</code>, <code>get_tracks()</code> or licensing) raises
|
||||
<code>RuntimeError</code> at once. The client polls for prompts only during authentication, so
|
||||
no answer can come.</li>
|
||||
<li>A CDM call (<code>InputBridge.request_cdm</code>) works during and after authentication, because the
|
||||
client also polls while its own requests run. A call that no client fetches within 10 seconds
|
||||
fails then, because no client is listening. A fetched call waits 60 seconds for its answer.
|
||||
The call leaves the auth status as it was. An answer never marks the remote session as client-authenticated.</li>
|
||||
<li><code>AUTH_INPUT_TIMEOUT = 600.0</code> seconds. This is also the TTL granted to
|
||||
<code>AUTHENTICATING</code> / <code>PENDING_INPUT</code> sessions in the store.</li>
|
||||
</ul>
|
||||
@@ -2847,8 +2937,15 @@ layer.</p>
|
||||
<div class="language-json highlight"><pre><span></span><code><span id="__span-7-1"><a id="__codelineno-7-1" name="__codelineno-7-1" href="#__codelineno-7-1"></a><span class="p">{</span><span class="w"> </span><span class="nt">"status"</span><span class="p">:</span><span class="w"> </span><span class="s2">"authenticated"</span><span class="w"> </span><span class="p">}</span>
|
||||
</span><span id="__span-7-2"><a id="__codelineno-7-2" name="__codelineno-7-2" href="#__codelineno-7-2"></a><span class="p">{</span><span class="w"> </span><span class="nt">"status"</span><span class="p">:</span><span class="w"> </span><span class="s2">"authenticating"</span><span class="w"> </span><span class="p">}</span>
|
||||
</span><span id="__span-7-3"><a id="__codelineno-7-3" name="__codelineno-7-3" href="#__codelineno-7-3"></a><span class="p">{</span><span class="w"> </span><span class="nt">"status"</span><span class="p">:</span><span class="w"> </span><span class="s2">"pending_input"</span><span class="p">,</span><span class="w"> </span><span class="nt">"prompt"</span><span class="p">:</span><span class="w"> </span><span class="s2">"Enter code: "</span><span class="w"> </span><span class="p">}</span>
|
||||
</span><span id="__span-7-4"><a id="__codelineno-7-4" name="__codelineno-7-4" href="#__codelineno-7-4"></a><span class="p">{</span><span class="w"> </span><span class="nt">"status"</span><span class="p">:</span><span class="w"> </span><span class="s2">"failed"</span><span class="p">,</span><span class="w"> </span><span class="nt">"error"</span><span class="p">:</span><span class="w"> </span><span class="s2">"...message..."</span><span class="w"> </span><span class="p">}</span>
|
||||
</span><span id="__span-7-4"><a id="__codelineno-7-4" name="__codelineno-7-4" href="#__codelineno-7-4"></a><span class="p">{</span><span class="w"> </span><span class="nt">"status"</span><span class="p">:</span><span class="w"> </span><span class="s2">"pending_input"</span><span class="p">,</span><span class="w"> </span><span class="nt">"prompt"</span><span class="p">:</span><span class="w"> </span><span class="s2">"..."</span><span class="p">,</span><span class="w"> </span><span class="nt">"cdm_call"</span><span class="p">:</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="nt">"op"</span><span class="p">:</span><span class="w"> </span><span class="s2">"challenge"</span><span class="p">,</span><span class="w"> </span><span class="nt">"drm"</span><span class="p">:</span><span class="w"> </span><span class="s2">"widevine"</span><span class="p">,</span><span class="w"> </span><span class="nt">"init_data"</span><span class="p">:</span><span class="w"> </span><span class="s2">"..."</span><span class="p">,</span><span class="w"> </span><span class="nt">"license_type"</span><span class="p">:</span><span class="w"> </span><span class="s2">"OFFLINE"</span><span class="p">,</span><span class="w"> </span><span class="nt">"privacy_mode"</span><span class="p">:</span><span class="w"> </span><span class="kc">true</span><span class="p">,</span><span class="w"> </span><span class="nt">"service_certificate"</span><span class="p">:</span><span class="w"> </span><span class="s2">"..."</span><span class="w"> </span><span class="p">}</span><span class="w"> </span><span class="p">}</span>
|
||||
</span><span id="__span-7-5"><a id="__codelineno-7-5" name="__codelineno-7-5" href="#__codelineno-7-5"></a><span class="p">{</span><span class="w"> </span><span class="nt">"status"</span><span class="p">:</span><span class="w"> </span><span class="s2">"failed"</span><span class="p">,</span><span class="w"> </span><span class="nt">"error"</span><span class="p">:</span><span class="w"> </span><span class="s2">"...message..."</span><span class="w"> </span><span class="p">}</span>
|
||||
</span></code></pre></div>
|
||||
<p>A <code>cdm_call</code> comes first, in any auth state. The client answers it with a JSON object in
|
||||
<code>response</code>: <code>{"session": "...", "challenge": "<base64>"}</code> for <code>challenge</code>,
|
||||
<code>{"keys": [{"kid", "type", "key", "permissions"}]}</code> for <code>keys</code>, <code>{}</code> for <code>close</code>, or
|
||||
<code>{"error": "..."}</code> when its CDM refuses. An older client refuses <code>close</code>, and the server
|
||||
ignores that refusal. An answered call stops being pending at once, so a client that polls again
|
||||
straight away does not see it twice.</p>
|
||||
<p>A missing remote session returns <code>404 SESSION_NOT_FOUND</code>. An IP mismatch returns
|
||||
<code>403 FORBIDDEN</code>. <code>POST /api/session/{id}/prompt</code> takes <code>{ "response": "..." }</code> and
|
||||
returns <code>{ "status": "accepted" }</code>. A post with no pending prompt is an
|
||||
@@ -2929,8 +3026,8 @@ returns <code>{ "status": "accepted" }</code>. A post with no pending prompt is
|
||||
<div class="language-text highlight"><pre><span></span><code><span id="__span-8-1"><a id="__codelineno-8-1" name="__codelineno-8-1" href="#__codelineno-8-1"></a>_sessions/<pbkdf2_hmac(sha256, X-Secret-Key, "unshackle-session-ns", 100000)[:12]>/<session_id>/<service>
|
||||
</span></code></pre></div>
|
||||
<p>The handler writes forwarded <code>cache</code> files into that directory before authentication.
|
||||
On <code>DELETE</code>, when the login belongs to the client (<code>client_auth</code>), the handler
|
||||
harvests updated cache files from the whole directory tree (compressing each
|
||||
On <code>DELETE</code>, when the login belongs to the client (<code>client_auth</code>) and the remote
|
||||
session does not run on the server's device, the handler harvests updated cache files from the whole directory tree (compressing each
|
||||
with zlib and base64-encoding, <strong>excluding</strong> <code>titles_*</code> files) and returns them
|
||||
under a <code>cache</code> field, so the client can keep refreshed tokens. Each cache key
|
||||
is the file path relative to that directory, with <code>/</code> separators and no <code>.json</code>
|
||||
|
||||
@@ -2698,15 +2698,19 @@ them in this order.</p>
|
||||
<ol>
|
||||
<li><strong>An explicit URI.</strong> unshackle uses anything shaped like <code>http://...</code>,
|
||||
<code>https://...</code>, or a <code>socks...</code> URI exactly as you give it. unshackle logs
|
||||
<code>Using explicit Proxy: ...</code> and does no lookup.</li>
|
||||
<code>Using explicit Proxy: ...</code> and does no lookup. A <code>host:port</code> value such as
|
||||
<code>localhost:8080</code> is also an explicit proxy.</li>
|
||||
<li><strong>A provider-prefixed query</strong>: <code>provider:query</code>, for example <code>nordvpn:us</code> or
|
||||
<code>gluetun:windscribe:us</code>. unshackle finds the proxy provider whose name matches
|
||||
the prefix (case-insensitive). It then asks <em>only</em> that proxy provider to find a
|
||||
proxy for the remainder. If unshackle loads no such proxy provider, or if that
|
||||
proxy provider returns no proxy, the download errors.</li>
|
||||
<li><strong>A bare query</strong>: a region like <code>us</code>, <code>gb</code>, <code>us:seattle</code>, or <code>us1234</code>. unshackle
|
||||
asks each loaded proxy provider <strong>in order</strong> and uses the first proxy any of them
|
||||
returns.</li>
|
||||
<li><strong>A bare query</strong>: a region like <code>us</code>, <code>gb</code>, or <code>us1234</code>. unshackle asks each
|
||||
loaded proxy provider <strong>in order</strong> and uses the first proxy any of them returns. A
|
||||
bare city query such as <code>us:seattle</code> does not work: unshackle reads <code>us</code> as a proxy
|
||||
provider name. Use the proxy provider prefix, for example <code>nordvpn:us:seattle</code>.
|
||||
If no proxy provider has a proxy for the query, unshackle stops with
|
||||
<code>No proxy provider had a proxy for <query></code> and does not continue without a proxy.</li>
|
||||
</ol>
|
||||
<p>unshackle compares the query against a region grammar: a country or location code of two
|
||||
to four letters, with an optional <code>_code</code> part (<code>res_yyz</code>), then an optional server
|
||||
@@ -2724,6 +2728,10 @@ resolution:</p>
|
||||
<p>So if you have both Basic and NordVPN configured and use <code>--proxy us</code>, a <code>us</code> entry in
|
||||
your Basic config wins, because unshackle tries Basic first. To skip ahead to a specific
|
||||
proxy provider, prefix the query (<code>--proxy nordvpn:us</code>).</p>
|
||||
<p>If a proxy provider cannot load, for example because its server list cannot be fetched
|
||||
or its config is not valid, unshackle logs a warning and continues with the other proxy
|
||||
providers. A bare query skips the proxy provider that did not load. A query that names it,
|
||||
such as <code>--proxy nordvpn:us</code>, fails and shows the reason it did not load.</p>
|
||||
<div class="admonition note">
|
||||
<p class="admonition-title">A bare region reaches Control D last</p>
|
||||
<p>unshackle asks Control D for a bare region such as <code>--proxy us</code> only when no other
|
||||
@@ -3176,7 +3184,8 @@ the extra throughput.</p>
|
||||
that alias always wins.</li>
|
||||
<li>unshackle changes a <code>us1239</code>-style query (country code + number) with no explicit
|
||||
mapping into a provider-specific server hostname (for example <code>us1239.nordvpn.com</code>
|
||||
for NordVPN, <code>us-1239.prod.surfshark.com</code> for Surfshark).</li>
|
||||
for NordVPN). Surfshark has no numbered servers, so map a Surfshark region to a
|
||||
server name such as <code>us-dal.prod.surfshark.com</code> in <code>server_hostnames</code>.</li>
|
||||
<li>unshackle expands a bare two-letter code to the full country name Gluetun expects.</li>
|
||||
</ol>
|
||||
<p>A few providers (Windscribe, VyprVPN, VPN Secure) select by <strong>region</strong> rather than
|
||||
@@ -3358,7 +3367,7 @@ country-code confusion that <code>uk</code> invites.</p>
|
||||
<td>The specific server <code>us1234</code>.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>us:seattle</code></td>
|
||||
<td><code>nordvpn:us:seattle</code></td>
|
||||
<td>A recommended server in Seattle.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -3471,19 +3480,23 @@ have non-contiguous IDs like <code>#203</code>, <code>#813</code>, and so on. Co
|
||||
previous run's log line (e.g. <code>DE#203</code>) instead.</p>
|
||||
</div>
|
||||
<h2 id="hola">Hola<a class="headerlink" href="#hola" title="Permanent link">¶</a></h2>
|
||||
<p>Hola requires no configuration at all. It uses the
|
||||
<a href="https://github.com/Snawoot/hola-proxy"><code>hola-proxy</code></a> binary, and <strong>auto-loads</strong> whenever
|
||||
that binary is found on your <code>PATH</code>. If you query Hola but the binary is missing, the
|
||||
proxy provider raises an error that tells you to install it.</p>
|
||||
<div class="language-shell highlight"><span class="filename">Install hola-proxy, then just query a country</span><pre><span></span><code><span id="__span-19-1"><a id="__codelineno-19-1" name="__codelineno-19-1" href="#__codelineno-19-1"></a>unshackle<span class="w"> </span>dl<span class="w"> </span>--proxy<span class="w"> </span>hola:us<span class="w"> </span>EXAMPLE<span class="w"> </span><span class="m">81234567</span>
|
||||
<p>Hola requires no configuration at all. It uses the <code>hola-proxy</code> binary, and
|
||||
<strong>auto-loads</strong> whenever that binary is found on your <code>PATH</code>. If you query Hola but the
|
||||
binary is missing, the proxy provider raises an error that tells you to install it.</p>
|
||||
<p>The <code>hola-proxy</code> GitHub repository is no longer online, so build the binary with Go. The
|
||||
Go module proxy still has the source for version 1.18.2. <code>go install</code> puts the binary in
|
||||
<code>$(go env GOPATH)/bin</code>, which must be on your <code>PATH</code>.</p>
|
||||
<div class="language-shell highlight"><span class="filename">Build hola-proxy, then query a country</span><pre><span></span><code><span id="__span-19-1"><a id="__codelineno-19-1" name="__codelineno-19-1" href="#__codelineno-19-1"></a>go<span class="w"> </span>install<span class="w"> </span>github.com/Snawoot/hola-proxy@v1.18.2
|
||||
</span><span id="__span-19-2"><a id="__codelineno-19-2" name="__codelineno-19-2" href="#__codelineno-19-2"></a>unshackle<span class="w"> </span>dl<span class="w"> </span>--proxy<span class="w"> </span>hola:us<span class="w"> </span>EXAMPLE<span class="w"> </span><span class="m">81234567</span>
|
||||
</span></code></pre></div>
|
||||
<p><strong>Query forms:</strong> a two-letter country code (e.g. <code>us</code>, <code>gb</code>). unshackle asks <code>hola-proxy</code>
|
||||
for available proxies in that country and picks one at random, returning an HTTP proxy.</p>
|
||||
<div class="admonition warning">
|
||||
<p class="admonition-title">Temporary bans</p>
|
||||
<p>Hola's free tier can rate-limit or temporarily ban you if queried too aggressively. If
|
||||
you see a <em>temporary ban detected</em> error, wait before retrying. Hola currently uses
|
||||
only datacenter proxies.</p>
|
||||
you see a <em>temporary ban detected</em> error, wait before retrying. While a ban is active,
|
||||
<code>hola-proxy</code> does not stop, so unshackle waits 30 seconds and then reports the ban.
|
||||
Hola currently uses only datacenter proxies.</p>
|
||||
</div>
|
||||
<h2 id="surfshark">Surfshark<a class="headerlink" href="#surfshark" title="Permanent link">¶</a></h2>
|
||||
<p>Surfshark, like NordVPN, uses <strong>Service Credentials</strong> rather than your login. Make
|
||||
@@ -3492,12 +3505,17 @@ them from the <a href="https://my.surfshark.com/vpn/manual-setup/main/openvpn">S
|
||||
</span><span id="__span-20-2"><a id="__codelineno-20-2" name="__codelineno-20-2" href="#__codelineno-20-2"></a><span class="w"> </span><span class="nt">surfsharkvpn</span><span class="p">:</span>
|
||||
</span><span id="__span-20-3"><a id="__codelineno-20-3" name="__codelineno-20-3" href="#__codelineno-20-3"></a><span class="w"> </span><span class="nt">username</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">YOUR_SERVICE_USERNAME</span>
|
||||
</span><span id="__span-20-4"><a id="__codelineno-20-4" name="__codelineno-20-4" href="#__codelineno-20-4"></a><span class="w"> </span><span class="nt">password</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">YOUR_SERVICE_PASSWORD</span>
|
||||
</span><span id="__span-20-5"><a id="__codelineno-20-5" name="__codelineno-20-5" href="#__codelineno-20-5"></a><span class="w"> </span><span class="nt">server_map</span><span class="p">:</span><span class="w"> </span><span class="c1"># optional</span>
|
||||
</span><span id="__span-20-6"><a id="__codelineno-20-6" name="__codelineno-20-6" href="#__codelineno-20-6"></a><span class="w"> </span><span class="nt">us</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">1234</span>
|
||||
</span><span id="__span-20-5"><a id="__codelineno-20-5" name="__codelineno-20-5" href="#__codelineno-20-5"></a><span class="w"> </span><span class="nt">server_map</span><span class="p">:</span><span class="w"> </span><span class="c1"># optional: region -> server name</span>
|
||||
</span><span id="__span-20-6"><a id="__codelineno-20-6" name="__codelineno-20-6" href="#__codelineno-20-6"></a><span class="w"> </span><span class="nt">us</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">us-dal</span>
|
||||
</span><span id="__span-20-7"><a id="__codelineno-20-7" name="__codelineno-20-7" href="#__codelineno-20-7"></a><span class="w"> </span><span class="nt">us:seattle</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">us-sea</span>
|
||||
</span></code></pre></div>
|
||||
<p><strong>Required keys:</strong> <code>username</code>, <code>password</code>, validated with the same 48-character rule as
|
||||
NordVPN (combined username+password must be 48 alphanumeric characters, case-insensitive, no <code>@</code>).
|
||||
<code>server_map</code> optionally pins server IDs per region.</p>
|
||||
<code>server_map</code> optionally pins a server per region. Give the server name from Surfshark's
|
||||
server list, for example <code>us-dal</code>. A full hostname such as <code>us-dal.prod.surfshark.com</code> also
|
||||
works. Surfshark does not use numeric server IDs. unshackle ignores a numeric or empty value
|
||||
and logs a warning. A <code>us:seattle</code> entry applies only to that city query, and it does not
|
||||
fall back to the <code>us</code> entry.</p>
|
||||
<p><strong>Query forms:</strong></p>
|
||||
<table>
|
||||
<thead>
|
||||
@@ -3508,19 +3526,24 @@ NordVPN (combined username+password must be 48 alphanumeric characters, case-ins
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><code>us</code></td>
|
||||
<td>A random US server.</td>
|
||||
<td><code>surfsharkvpn:us</code></td>
|
||||
<td>A random US server. <code>uk</code> and <code>gb</code> both give a UK server.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>us-bos</code></td>
|
||||
<td>A specific server.</td>
|
||||
<td><code>surfsharkvpn:us-bos</code></td>
|
||||
<td>A specific server from Surfshark's server list.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>us:seattle</code></td>
|
||||
<td><code>surfsharkvpn:us:seattle</code></td>
|
||||
<td>A random server in Seattle.</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<p>unshackle ignores case, spaces, hyphens and accents in a city name, so <code>us:new-york</code>
|
||||
matches New York. A city also matches the start of a longer name: <code>de:frankfurt</code> matches
|
||||
Frankfurt am Main. A bare <code>us</code> also reaches Surfshark. A bare <code>us-bos</code> can stop at a
|
||||
proxy provider earlier in the order, and a bare <code>us:seattle</code> does not work, so use the
|
||||
<code>surfsharkvpn:</code> prefix for those forms.</p>
|
||||
<p>The returned proxy is HTTPS on <strong>port 443</strong>.</p>
|
||||
<h2 id="windscribe">Windscribe<a class="headerlink" href="#windscribe" title="Permanent link">¶</a></h2>
|
||||
<p>Windscribe uses <strong>Service Credentials</strong> from its
|
||||
@@ -3554,7 +3577,7 @@ sure that a username and a password are present (there is no 48-character rule).
|
||||
<td>A specific numbered server.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>us:seattle</code></td>
|
||||
<td><code>windscribevpn:us:seattle</code></td>
|
||||
<td>A random server in Seattle.</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
|
||||
+687
-687
File diff suppressed because it is too large
Load Diff
@@ -2345,9 +2345,8 @@ for the full proxy provider guide. Recognised proxy providers and their exit por
|
||||
</table>
|
||||
<div class="admonition note">
|
||||
<p class="admonition-title">Provider loading differs between CLI and REST server</p>
|
||||
<p>The <code>dl</code> CLI loads all providers, including <code>windscribevpn</code> and <code>gluetun</code>. The REST API /
|
||||
remote-client path uses a separate resolver that does <strong>not</strong> load <code>windscribevpn</code> or
|
||||
<code>gluetun</code>. ExpressVPN and ProtonVPN also auto-load when their cached session exists, and Hola
|
||||
<p>The <code>dl</code> CLI loads all providers, including <code>gluetun</code>. The REST API / remote-client path
|
||||
does <strong>not</strong> load <code>gluetun</code>, because it starts a local Docker container. ExpressVPN and ProtonVPN also auto-load when their cached session exists, and Hola
|
||||
auto-loads whenever the <code>hola-proxy</code> binary is present.</p>
|
||||
</div>
|
||||
|
||||
|
||||
@@ -2358,6 +2358,13 @@ the limit it always goes to the client's device. A licence for a lower track can
|
||||
content key of a higher track when the service shares one content key between them. With server
|
||||
accounts enabled, a client that reports a stronger device than it holds makes the server's
|
||||
account request those manifests; the licence server still refuses its challenge.</p>
|
||||
<p><code>server_vault</code> lets a remote session that the client's own device licenses take content keys
|
||||
from the server vault. Set it to <code>true</code> for every service, or to a list of service tags. It is
|
||||
<code>false</code> unless the entry sets it, and <code>server_cdm</code> for a service implies it. The server looks up
|
||||
every KID of the track in its vault and makes no live licence. A track that the vault does not
|
||||
hold goes back to the client's device. When the service runs the remote session on the server's
|
||||
own device (a service option, such as a server-identity flag), the client's own vaults, and the
|
||||
server vault with this grant, are the only source, and a missing content key stops the download.</p>
|
||||
<p><code>admin</code> is a boolean that lets the API key run the maintenance endpoints (clear-cache, clear-temp, refresh-services). It is <code>false</code> unless the entry sets it. Keys that have no <code>users</code> entry, such as <code>api_secret</code>, keep that access.</p>
|
||||
<p>A <code>tier</code> names an entry under <code>serve.tiers</code>, which holds the settings that several API keys
|
||||
share. Today a tier carries <code>rate_limit</code>, the requests per hour that API key may make; an API
|
||||
@@ -2441,6 +2448,9 @@ region; a client that reports none is not blocked.</p>
|
||||
</span><span id="__span-3-20"><a id="__codelineno-3-20" name="__codelineno-3-20" href="#__codelineno-3-20"></a><span class="w"> </span><span class="nt">server_cdm</span><span class="p">:</span><span class="w"> </span><span class="p p-Indicator">[</span><span class="nv">EXAMPLE1</span><span class="p p-Indicator">]</span><span class="w"> </span><span class="c1"># the server licenses only EXAMPLE1; EXAMPLE2 needs a local CDM</span>
|
||||
</span><span id="__span-3-21"><a id="__codelineno-3-21" name="__codelineno-3-21" href="#__codelineno-3-21"></a><span class="w"> </span><span class="nt">server_accounts</span><span class="p">:</span><span class="w"> </span><span class="p p-Indicator">[</span><span class="nv">EXAMPLE1</span><span class="p p-Indicator">]</span><span class="w"> </span><span class="c1"># may authenticate EXAMPLE1 with one of the server's own accounts</span>
|
||||
</span><span id="__span-3-22"><a id="__codelineno-3-22" name="__codelineno-3-22" href="#__codelineno-3-22"></a><span class="w"> </span><span class="nt">server_proxy</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">true</span><span class="w"> </span><span class="c1"># this key may also use the server's proxy providers</span>
|
||||
</span><span id="__span-3-23"><a id="__codelineno-3-23" name="__codelineno-3-23" href="#__codelineno-3-23"></a><span class="w"> </span><span class="nt">f3a4b5c6</span><span class="p">:</span>
|
||||
</span><span id="__span-3-24"><a id="__codelineno-3-24" name="__codelineno-3-24" href="#__codelineno-3-24"></a><span class="w"> </span><span class="nt">services</span><span class="p">:</span><span class="w"> </span><span class="p p-Indicator">[</span><span class="nv">EXAMPLE1</span><span class="p p-Indicator">]</span>
|
||||
</span><span id="__span-3-25"><a id="__codelineno-3-25" name="__codelineno-3-25" href="#__codelineno-3-25"></a><span class="w"> </span><span class="nt">server_vault</span><span class="p">:</span><span class="w"> </span><span class="p p-Indicator">[</span><span class="nv">EXAMPLE1</span><span class="p p-Indicator">]</span><span class="w"> </span><span class="c1"># the client's device licenses; the server vault still serves keys</span>
|
||||
</span></code></pre></div>
|
||||
<div class="admonition note">
|
||||
<p class="admonition-title"><code>dl</code> keys inside <code>serve</code></p>
|
||||
|
||||
File diff suppressed because one or more lines are too long
+38
-38
@@ -2,154 +2,154 @@
|
||||
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
|
||||
<url>
|
||||
<loc>https://docs.unshackle.dev/</loc>
|
||||
<lastmod>2026-09-25</lastmod>
|
||||
<lastmod>2026-09-26</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://docs.unshackle.dev/dev/creating-a-service/</loc>
|
||||
<lastmod>2026-09-25</lastmod>
|
||||
<lastmod>2026-09-26</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://docs.unshackle.dev/dev/service-architecture/</loc>
|
||||
<lastmod>2026-09-25</lastmod>
|
||||
<lastmod>2026-09-26</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://docs.unshackle.dev/dev/rest-api/</loc>
|
||||
<lastmod>2026-09-25</lastmod>
|
||||
<lastmod>2026-09-26</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://docs.unshackle.dev/dev/rest-api/authentication/</loc>
|
||||
<lastmod>2026-09-25</lastmod>
|
||||
<lastmod>2026-09-26</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://docs.unshackle.dev/dev/rest-api/dashboard/</loc>
|
||||
<lastmod>2026-09-25</lastmod>
|
||||
<lastmod>2026-09-26</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://docs.unshackle.dev/dev/rest-api/endpoints/</loc>
|
||||
<lastmod>2026-09-25</lastmod>
|
||||
<lastmod>2026-09-26</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://docs.unshackle.dev/dev/rest-api/errors/</loc>
|
||||
<lastmod>2026-09-25</lastmod>
|
||||
<lastmod>2026-09-26</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://docs.unshackle.dev/dev/rest-api/job-lifecycle/</loc>
|
||||
<lastmod>2026-09-25</lastmod>
|
||||
<lastmod>2026-09-26</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://docs.unshackle.dev/dev/rest-api/quickstart/</loc>
|
||||
<lastmod>2026-09-25</lastmod>
|
||||
<lastmod>2026-09-26</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://docs.unshackle.dev/dev/rest-api/remote-sessions/</loc>
|
||||
<lastmod>2026-09-25</lastmod>
|
||||
<lastmod>2026-09-26</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://docs.unshackle.dev/getting-started/configuration-file/</loc>
|
||||
<lastmod>2026-09-25</lastmod>
|
||||
<lastmod>2026-09-26</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://docs.unshackle.dev/getting-started/installation/</loc>
|
||||
<lastmod>2026-09-25</lastmod>
|
||||
<lastmod>2026-09-26</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://docs.unshackle.dev/getting-started/quickstart/</loc>
|
||||
<lastmod>2026-09-25</lastmod>
|
||||
<lastmod>2026-09-26</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://docs.unshackle.dev/guide/cli-reference/</loc>
|
||||
<lastmod>2026-09-25</lastmod>
|
||||
<lastmod>2026-09-26</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://docs.unshackle.dev/guide/downloading/</loc>
|
||||
<lastmod>2026-09-25</lastmod>
|
||||
<lastmod>2026-09-26</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://docs.unshackle.dev/guide/drm-and-cdm/</loc>
|
||||
<lastmod>2026-09-25</lastmod>
|
||||
<lastmod>2026-09-26</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://docs.unshackle.dev/guide/output-and-naming/</loc>
|
||||
<lastmod>2026-09-25</lastmod>
|
||||
<lastmod>2026-09-26</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://docs.unshackle.dev/guide/proxies-and-vpn/</loc>
|
||||
<lastmod>2026-09-25</lastmod>
|
||||
<lastmod>2026-09-26</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://docs.unshackle.dev/guide/subtitles/</loc>
|
||||
<lastmod>2026-09-25</lastmod>
|
||||
<lastmod>2026-09-26</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://docs.unshackle.dev/guide/troubleshooting/</loc>
|
||||
<lastmod>2026-09-25</lastmod>
|
||||
<lastmod>2026-09-26</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://docs.unshackle.dev/guide/vaults/</loc>
|
||||
<lastmod>2026-09-25</lastmod>
|
||||
<lastmod>2026-09-26</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://docs.unshackle.dev/reference/api/config/</loc>
|
||||
<lastmod>2026-09-25</lastmod>
|
||||
<lastmod>2026-09-26</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://docs.unshackle.dev/reference/api/drm/</loc>
|
||||
<lastmod>2026-09-25</lastmod>
|
||||
<lastmod>2026-09-26</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://docs.unshackle.dev/reference/api/service/</loc>
|
||||
<lastmod>2026-09-25</lastmod>
|
||||
<lastmod>2026-09-26</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://docs.unshackle.dev/reference/api/titles/</loc>
|
||||
<lastmod>2026-09-25</lastmod>
|
||||
<lastmod>2026-09-26</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://docs.unshackle.dev/reference/api/tracks/</loc>
|
||||
<lastmod>2026-09-25</lastmod>
|
||||
<lastmod>2026-09-26</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://docs.unshackle.dev/reference/configuration/</loc>
|
||||
<lastmod>2026-09-25</lastmod>
|
||||
<lastmod>2026-09-26</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://docs.unshackle.dev/reference/configuration/directories/</loc>
|
||||
<lastmod>2026-09-25</lastmod>
|
||||
<lastmod>2026-09-26</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://docs.unshackle.dev/reference/configuration/download/</loc>
|
||||
<lastmod>2026-09-25</lastmod>
|
||||
<lastmod>2026-09-26</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://docs.unshackle.dev/reference/configuration/drm/</loc>
|
||||
<lastmod>2026-09-25</lastmod>
|
||||
<lastmod>2026-09-26</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://docs.unshackle.dev/reference/configuration/example/</loc>
|
||||
<lastmod>2026-09-25</lastmod>
|
||||
<lastmod>2026-09-26</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://docs.unshackle.dev/reference/configuration/misc/</loc>
|
||||
<lastmod>2026-09-25</lastmod>
|
||||
<lastmod>2026-09-26</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://docs.unshackle.dev/reference/configuration/network/</loc>
|
||||
<lastmod>2026-09-25</lastmod>
|
||||
<lastmod>2026-09-26</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://docs.unshackle.dev/reference/configuration/output/</loc>
|
||||
<lastmod>2026-09-25</lastmod>
|
||||
<lastmod>2026-09-26</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://docs.unshackle.dev/reference/configuration/post-scripts/</loc>
|
||||
<lastmod>2026-09-25</lastmod>
|
||||
<lastmod>2026-09-26</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://docs.unshackle.dev/reference/configuration/services/</loc>
|
||||
<lastmod>2026-09-25</lastmod>
|
||||
<lastmod>2026-09-26</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://docs.unshackle.dev/reference/configuration/vaults/</loc>
|
||||
<lastmod>2026-09-25</lastmod>
|
||||
<lastmod>2026-09-26</lastmod>
|
||||
</url>
|
||||
</urlset>
|
||||
Binary file not shown.
Reference in New Issue
Block a user