> For the complete documentation index, see [llms.txt](https://docs.netmap.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.netmap.dev/troubleshooting/reverse-proxy-problems.md).

# Reverse Proxy Problems

Common causes:

* Wrong `APP_URL`.
* Missing origin in `CORS_ORIGINS`.
* Missing hostname in `TRUSTED_HOSTS`.
* Proxy strips `X-API-Key`.
* Proxy does not pass WebSocket upgrade headers.
* `AUTH_COOKIE_SECURE=true` while using plain HTTP.

Fix proxy headers and restart NetMap after configuration changes.

## Symptoms

* UI loads but API calls fail.
* Login succeeds directly by IP but fails through the domain.
* API keys work against NetMap directly but fail through the proxy.
* WebSocket/live features disconnect.
* Browser console shows CORS errors.

## Required Headers

Forward:

```nginx
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $connection_upgrade;
```

Also preserve `X-API-Key`.

## Configuration To Check

```dotenv
APP_URL=https://netmap.example.com
CORS_ORIGINS=["https://netmap.example.com"]
TRUSTED_HOSTS=["netmap.example.com"]
AUTH_COOKIE_SECURE=true
```

## Verify

```bash
curl --fail https://netmap.example.com/api/health
```

Then test API-key auth through the proxy:

```bash
curl --fail-with-body \
  --url "https://netmap.example.com/api/v1/auth/me" \
  --header "X-API-Key: <api-key>"
```

## Related Pages

* [Reverse Proxy And HTTPS](/installation/reverse-proxy.md)
* [Ports](/reference/ports.md)
* [API-Key Problems](/troubleshooting/api-key-problems.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.netmap.dev/troubleshooting/reverse-proxy-problems.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.