> For the complete documentation index, see [llms.txt](https://docs.openappsec.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openappsec.io/troubleshooting/troubleshooting-guides/open-appsec-on-docker-http-transaction-handler-is-set-to-ready.md).

# open-appsec on Docker HTTP Transaction Handler Is Set To Ready

### Issue 

When installing open-appsec with Docker traffic is not inspected, and the Transaction Handler is set to "Ready", as in the following output: 

```
$ Docker exec -it open-appsec-agent open-appsec-ctl -s
---- open-appsec Nano Agent ----
Version: 1.1.0-open-source
Status: Running
Management mode: Cloud management
Policy files:
    /etc/cp/conf/local_policy.yaml
Policy load status: Success
Last policy update: 2023-10-15T10:19:39.607845

---- open-appsec Orchestration Nano Service ----
Type: Public, Version: 1.1.0-open-source, Created at: 2023-10-05T17:46:48+0000
Status: Running

---- open-appsec Attachment Registrator Nano Service ----
Type: Public, Version: 1.1.0-open-source, Created at: 2023-10-05T17:46:48+0000
Status: Running

---- open-appsec Http Transaction Handler Nano Service ----
Type: Public, Version: 1.1.0-open-source, Created at: 2023-10-05T17:46:48+0000
Status: Ready


For release notes and known limitations check: https://docs.openappsec.io/release-notes
For troubleshooting and support: https://openappsec.io/support
```

### Troubleshooting

1. Check that the webserver behind the NGINX reverse proxy is accessible, if not follow the guide here:

{% content-ref url="/pages/M5gRyOv2sORauolIsJba" %}
[Agent Fails to Recognize HTTP Transactions with NGINX](/troubleshooting/troubleshooting-guides/agent-fails-to-recognize-http-transactions-with-nginx.md)
{% endcontent-ref %}

2. Please check the status of the shared memory (`/dev/shm`) in both containers to ensure it is not empty, and make sure both containers can access it.


---

# 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.openappsec.io/troubleshooting/troubleshooting-guides/open-appsec-on-docker-http-transaction-handler-is-set-to-ready.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.