> For the complete documentation index, see [llms.txt](https://docs.jentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jentis.com/key-features/cookie-lifetime-extender/cookie-lifetime-extender-webserver-cdn-configurations/plesk-configuration-guide.md).
# Plesk Configuration Guide
### **Introduction**
This guide explains how to configure reverse proxy capabilities in your Plesk setup. A reverse proxy acts as an intermediary for client requests, forwarding them to a designated backend server. This setup enhances **load balancing**, **security**, and **caching** capabilities.
***
### **Prerequisites**
* Admin Access to your Plesk installation
* Your Website is running on Plesk
***
### **Configuration Steps**
**Step 1 - Sign in into your plesk setup:**
#### Step 2 - Configure the directive:
\
Under “Additional nginx directives” add the location from /hash(the first part of the tracking URL) and add the proxy\_pass directive to the JENTIS tracking URL
#### Step 3: Save and apply
After applying the directives, the webserver will restart and activate the new configuration.
***
### **Conclusion**
Your Plesk should now act as a reverse proxy and forward all request to /hash to your tracking domain.
{% hint style="danger" %}
After enabling Cookie lifetime extender, the DCP will give a proxy code that is expected to be setup on `https://domain.*/hash` however, if it is set up on `https://www.domain.*/hash` it will cause a CORS Error on the Cookie Lifetime Extender Requests.
For more details on WWW configuration follow this [guide](https://docs.jentis.com/key-features/cookie-lifetime-extender/configure-your-tracking#www-configuration-guide-optional).
{% endhint %}
***
If you have any questions or feedback, please open a request on our [Helpdesk](https://jentis.atlassian.net/servicedesk/customer/portal/1/group/1/create/220).
---
# 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.jentis.com/key-features/cookie-lifetime-extender/cookie-lifetime-extender-webserver-cdn-configurations/plesk-configuration-guide.md?ask=&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.
