> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/server/knowledge-base/troubleshooting-articles/cannot-read-property-enableinternetaccess-of-null.md).

# Cannot read property 'enableInternetAccess' of null

Resolves a null reference error on the Devolutions Server web page caused by missing read permission on the encryption config file with Integrated Security.

After the creation of a Devolutions Server instance, when trying to open the web page, the following error is displayed in the browser:

```
Cannot read property 'enableInternetAccess' of null
```

### Solution <a href="#solution" id="solution"></a>

This issue normally happens when the Integrated Security option is set in the Database tab of the Devolutions Server settings.

To solve the issue, the service account of the Devolutions Server IIS Application Pool and the service account of the DevolutionsSchedulerService in the services need Read permission on the **encryption.config** file that is located in the App\_Data subfolder of the Devolutions Server web application folder.

To navigate to the web application folder, you can use the ***Explore*** button from the Devolutions Server Console.


---

# 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.devolutions.net/server/knowledge-base/troubleshooting-articles/cannot-read-property-enableinternetaccess-of-null.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.