# Klai Server Proxy
### Overview
The Klai Proxy can be used to provide a single known IP address to access a given database server. This allows IT professionals to tightly configure access control to their internal network. The current proxy IP is located in North America.
#### PROS
Dev Ops technicians can whitelist only one IP address from the Klai Studio Cloud servers.
#### CONS
Some latency is added depending on your geographic location, this is generally small.
#### Specifications
Fixed IP Address is: **`54.215.158.200`**
Port: **`443`**
Proxy location: **AWS Data Center in Northern California. `US-WEST-1`**
#### Configuring
*The following is a temporary provision until the UI in the Klai editor is built*
Add a new server or change currently used by the app. The host address for the server will be:
Note: Change `YOUR.SERVER.DOMAIN` to point to the FQDN of your FileMaker server.
#### Testing Connection
To test the proxy:
1. Build the full proxy URL using your FileMaker server FQDN:
`http://4yt4c3i6n7tndqe6732fsbgxhq0gsaim.lambda-url.us-west-1.on.aws/YOUR.SERVER.DOMAIN`
2. Open that URL in a browser.
3. Confirm that the request reaches your FileMaker web server through the proxy.
If the proxy is working, you should reach the same kind of response page your FileMaker server would normally return for a direct browser request.
If it does not work, check:
* the server FQDN is correct
* your FileMaker server is reachable on the expected web endpoint
* your network rules allow the published proxy IP
* you did not omit the server domain portion of the proxy URL
Example response:
```html
FileMaker Website
FileMaker Database Server Website
```
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.klai.studio/reference/apis-and-services/core-apis/server-proxy.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.
```
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.klai.studio/reference/apis-and-services/core-apis/server-proxy.md?ask=