# PMM 3.6 Remote MySQL service on Windows connects successfully but remains Down (mysql\_up = 0

**URL:** <https://forums.percona.com/t/pmm-3-6-remote-mysql-service-on-windows-connects-successfully-but-remains-down-mysql-up-0/41065>\
**Category:** PMM 3.x\
**Created:** [July 15, 2026, 8:16am UTC](https://forums.percona.com/t/pmm-3-6-remote-mysql-service-on-windows-connects-successfully-but-remains-down-mysql-up-0/41065 "2026-07-15T08:16:02Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![smitha](https://avatars.discourse-cdn.com/v4/letter/s/f08c70/32.png) [@smitha](https://forums.percona.com/u/smitha)\
**Post date:** [July 15, 2026, 8:16am UTC](https://forums.percona.com/t/pmm-3-6-remote-mysql-service-on-windows-connects-successfully-but-remains-down-mysql-up-0/41065/1 "2026-07-15T08:16:02Z")

</div>

Environment

- PMM Server 3.6
- Oracle Linux 8
- Podman
- MySQL 5.7.13 Enterprise on Windows Server

Problem

I am adding a Windows-hosted MySQL instance using:

Inventory → Add Service → MySQL (Remote)

The service is created successfully.

Observations

- PMM can connect successfully.
- ServiceInfo returns MySQL version 5.7.13.
- performance\_schema = ON.
- Network connectivity is confirmed.
- MySQL user authenticates successfully.
- mysql\_up remains 0.
- Service Status remains Down.
- Built-in dashboards show No Data.

Relevant PMM log

CheckConnection response  
ServiceInfo response: version:“5.7.13-enterprise-commercial-advanced-log”

Later I see:

Agent with ID not found.

Question

Is this a known limitation or bug with PMM 3.6 remote monitoring of Windows-hosted MySQL, or is there an additional configuration step required after the service is created?

---

<div class="post-metadata">

**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\
**Post date:** [July 15, 2026, 12:45pm UTC](https://forums.percona.com/t/pmm-3-6-remote-mysql-service-on-windows-connects-successfully-but-remains-down-mysql-up-0/41065/2 "2026-07-15T12:45:20Z")

</div>

Hi @smitha,  
There should not be any issues monitoring remote MySQL, even on Windows. You’ll need to investigate the PMM logs which are inside the docker container in `/srv/logs` to find out what’s going on.

---

<div class="post-metadata">

**Author:** ![smitha](https://avatars.discourse-cdn.com/v4/letter/s/f08c70/32.png) [@smitha](https://forums.percona.com/u/smitha)\
**Post date:** [July 16, 2026, 8:33am UTC](https://forums.percona.com/t/pmm-3-6-remote-mysql-service-on-windows-connects-successfully-but-remains-down-mysql-up-0/41065/3 "2026-07-16T08:33:30Z")

</div>

> [@matthewb](#):
>
> There should not be any issues monitoring remote MySQL, even on Windows. You’ll need to investigate the PMM logs which are inside the docker container in `/srv/logs` to find out what’sTgoing on.

Thank you very much Matt, for pointing that out. I reviewed the pmm-managed logs and noticed ‘remote error: tls: handshake failure’. It appears I had incorrected added the remote host with the option ' **Skip TLS certificate and hostname validation’** with the assumption it would simply skip tls validation. I unchecked that and readded it and the service status came up and it is able to query the dashboard as expected.