# pmm-client cannot communicate server

**URL:** <https://forums.percona.com/t/pmm-client-cannot-communicate-server/6621>\
**Category:** PMM 1.x\
**Created:** [October 10, 2018, 1:41am UTC](https://forums.percona.com/t/pmm-client-cannot-communicate-server/6621 "2018-10-10T01:41:41Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![liangyu5017](https://avatars.discourse-cdn.com/v4/letter/l/82dd89/32.png) [@liangyu5017](https://forums.percona.com/u/liangyu5017)\
**Post date:** [October 10, 2018, 1:41am UTC](https://forums.percona.com/t/pmm-client-cannot-communicate-server/6621/1 "2018-10-10T01:41:41Z")

</div>

pmm-client:172.26.0.149

pmm-server::172.26.0.135

run wget [URL][https://172.26.0.149:42000/metrics[/URL]](https://172.26.0.149:42000/metrics%5B/URL%5D) --no-check-certificate on pmm-client:

- [URL][https://172.26.0.149:42000/metrics[/URL]](https://172.26.0.149:42000/metrics%5B/URL%5D)  
Connecting to 172.26.0.149:42000… connected.  
WARNING: cannot verify 172.26.0.149’s certificate, issued by “/O=PMM Client”:  
Unable to locally verify the issuer’s authority.  
HTTP request sent, awaiting response… 401 Unauthorized  
Authorization failed.

and netstat -antl|grep 42000

tcp 0 0 172.26.0.149:42000 172.17.0.1:46776 SYN\_RECV  
tcp 0 0 172.26.0.149:42000 172.17.0.1:46766 SYN\_RECV  
tcp 0 0 172.26.0.149:42000 172.17.0.1:46768 SYN\_RECV  
tcp 0 0 172.26.0.149:42000 172.17.0.1:46774 SYN\_RECV

why connected to 172.17.0.1?

what should i do now

![photoid=52602](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/2X/7/7d33089bc6c69c21b24d388468a144eb829da358.png)

![photoid=52603](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/2X/6/6bedd47a9d310fb56e94a0b9bca0b4cb8b08b361.png)

 ![photoid=52604](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/2X/0/0eaac92663cacd8e363c5577f13805c86aa42f58.png)

![photoid=52605](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/2X/0/0bea04c61675761f100bd7ddcea2c2a3cfc09996.png)

---

<div class="post-metadata">

**Author:** ![Michael\_Coburn](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/michael_coburn/32/18_2.png) [@Michael\_Coburn](https://forums.percona.com/u/Michael_Coburn)\
**Post date:** [October 10, 2018, 9:16am UTC](https://forums.percona.com/t/pmm-client-cannot-communicate-server/6621/2 "2018-10-10T09:16:40Z")

</div>

Hi [liangyu5017](https://percona.vanillacommunities.com/profile/x/x/34207)  
I’m not positive but is this perhaps related to the docker networking configuration, is this how PMM server NAT’s itself out?

---

<div class="post-metadata">

**Author:** ![liangyu5017](https://avatars.discourse-cdn.com/v4/letter/l/82dd89/32.png) [@liangyu5017](https://forums.percona.com/u/liangyu5017)\
**Post date:** [October 30, 2018, 8:33pm UTC](https://forums.percona.com/t/pmm-client-cannot-communicate-server/6621/3 "2018-10-30T20:33:06Z")

</div>

Thank you. It has been solved. There is no automatic firewall rule after starting docker