# PMM Agent error **URL:** \ **Category:** PMM 2.x\ **Tags:** pmm\ **Created:** [January 16, 2025, 12:53pm UTC](https://forums.percona.com/t/pmm-agent-error/36186 "2025-01-16T12:53:26Z")\ **Posts on this page:** 1\ **Showing post:** 17
**Author:** ![Agustin\_G](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/agustin_g/32/14111_2.png) [@Agustin\_G](https://forums.percona.com/u/Agustin_G)\ **Post date:** [January 23, 2025, 7:56pm UTC](https://forums.percona.com/t/pmm-agent-error/36186/17 "2025-01-23T19:56:56Z")
Hi @ALFR3D022, Do you have a reverse proxy, load balancer, etc, between the PMM server and client? If so, make sure that GRPC traffic is allowed between them. Check the following discussion for some additional examples and a solution when using nginx: > [@Pmm-agent can not connect to pmm-server when using reverse proxy](https://forums.percona.com/t/pmm-agent-can-not-connect-to-pmm-server-when-using-reverse-proxy/8435): > > What I’m trying to achieve: Run pmm server in docker container on "server", expose port 443 as 127.0.0.1:8443 Use nginx as reverse proxy for 127.0.0.1:8443. This way nginx can handle TLS using certbot and also serve other domains. Connect pmm-agent running on "client" to "server" What I’ve done: deployed pmm-server image on docker like this: docker run --detach --restart always --publish 127.0.0.1:8443:443 --volumes-from pmm-data --name pmm-server percona/pmm-server:2 configured nginx site… --- _[View the full topic](https://forums.percona.com/t/pmm-agent-error/36186)._