> For the complete documentation index, see [llms.txt](https://docs.owkin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.owkin.com/help-center/troubleshooting/403-forbidden-error.md).

# "403 Forbidden" error when opening K-Pro

{% hint style="info" %}
**What this article covers** This article explains why K-Pro can show a "403 Forbidden" page when you open it, and what to do.
{% endhint %}

A **"403 Forbidden"** page means that your request reached K-Pro but was not allowed. For your organisation's K-Pro instance, a common reason is that it only accepts connections from approved network addresses, for example your company VPN.

### What to do

1. Connect to your company VPN and try again.
2. If you are on the VPN and still see the page, find your public IP address: with the VPN switched on, open a website that shows your IP address (for example whatismyipaddress.com).
3. Send us your public IP address, the email address you use for K-Pro, and a screenshot of the page.

### What happens next

We check whether the address of your network is on the list of approved addresses for your organisation, and ask for it to be added if needed. We will let you know when you can try again.

{% hint style="info" %}
This error is about the network you connect from. It does not mean that your account is blocked, and your data is not affected.
{% endhint %}

***

**✉️ Need more help?**\
If this article did not answer your questions, please [contact our support team](https://k-pro.zendesk.com/hc/en-us/requests/new?ticket_form_id=33609591380241) and we will be happy to help.


---

# 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.owkin.com/help-center/troubleshooting/403-forbidden-error.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.
