> For the complete documentation index, see [llms.txt](https://docs.pritunl.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pritunl.com/kb/vpn/outage.md).

# Outage

Pritunl Server Outage Mode

Pritunl server versions since v1.32.4465.96 have the ability to continue functioning with a full outage of all third party services including the Pritunl application servers and single sign-on services. By default the subscription will remain cached and active for several days. If the server was upgraded to v1.32.4465.96 or later it will retain the subscription even if the host is restarted. Updating the server after the outage has started will require reaching the license server before working.

### Single Sign-On Outage

<figure><img src="https://1783284711-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhDA4eusSNQcv5QfappvI%2Fuploads%2FJjzj7YSdfpwweOjP0z3a%2Fpritunl_sso_bypass.png?alt=media&amp;token=6027c98d-5e12-47b4-bbd4-5341dbe1bb6d" alt="" width="221"><figcaption></figcaption></figure>

The *Bypass Single Sign-On* mode in the server settings will allow users to connect without any validation from the single sign-on provider. This can only be enabled if *Device Authentication* is also enabled, this will allow the system to maintain a high level of authorization during the outage.

<figure><img src="https://1783284711-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhDA4eusSNQcv5QfappvI%2Fuploads%2F0tQKyHewzUqn7WmGpzNI%2Fdevice_auth1.png?alt=media&amp;token=d33ea5cf-8180-4e72-9a86-d1a692aeb379" alt="" width="456"><figcaption></figcaption></figure>

Once this is done users will be shown the prompt above when connecting and will need to provide this code to an administrator. The administrator can then find the device in the Pritunl web console either in the dashboard under *Devices Pending Registration* or if there are a large number of pending devices the user can be searched from the *Users* tab and the pending approval will be shown under the right drop down menu for that user. After the device has been approved they will be able to connect without requiring any third party services.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pritunl.com/kb/vpn/outage.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.