# Pmm v3 update not possible **URL:** \ **Category:** PMM 3.x\ **Created:** [April 2, 2025, 2:39pm UTC](https://forums.percona.com/t/pmm-v3-update-not-possible/37463 "2025-04-02T14:39:38Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![Marvin\_Stelter](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/marvin_stelter/32/11330_2.png) [@Marvin\_Stelter](https://forums.percona.com/u/Marvin_Stelter)\ **Post date:** [April 2, 2025, 2:39pm UTC](https://forums.percona.com/t/pmm-v3-update-not-possible/37463/1 "2025-04-02T14:39:38Z")
Hi, Unfortunately, I can’t update to PMM v3.1.0 via the UI. When I try, I get the following error: **“Failed to check watchtower host”** Both Docker Compose configurations use the same `WATCHTOWER_HTTP_API_TOKEN`. The update page also correctly displays information about my PMM instance. Do you have any idea why this error occurs? Thanks! ![grafik](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/3X/f/2/f2048d89aceb3a144f0914da5ec94c2419b32fe9.png) ---
**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:** [April 2, 2025, 3:10pm UTC](https://forums.percona.com/t/pmm-v3-update-not-possible/37463/2 "2025-04-02T15:10:16Z")
Hey @Marvin_Stelter, I take it you launched a docker container with watchtower? And you did this inside a dedicated docker network? And both watchtower, and pmm-server containers are in the same network? ---
**Author:** ![percona1](https://avatars.discourse-cdn.com/v4/letter/p/5daacb/32.png) [@percona1](https://forums.percona.com/u/percona1)\ **Post date:** [April 9, 2025, 4:40pm UTC](https://forums.percona.com/t/pmm-v3-update-not-possible/37463/3 "2025-04-09T16:40:39Z")
Hi, i have same issue both containers are in the same docker network ```auto [ { "Name": "pmm-network", "Id": "7849d1094a2619158c9ebe398aa132c62a183eef6b596685be925064012f61a3", "Created": "2025-03-12T15:17:13.937447747Z", "Scope": "local", "Driver": "bridge", "EnableIPv4": true, "EnableIPv6": false, "IPAM": { "Driver": "default", "Options": {}, "Config": [ { "Subnet": "172.18.0.0/16", "Gateway": "172.18.0.1" } ] }, "Internal": false, "Attachable": false, "Ingress": false, "ConfigFrom": { "Network": "" }, "ConfigOnly": false, "Containers": { "1620254d7b941e84ce136a6637b2902136f22c60a456a5bd5f00b6e885c44aca": { "Name": "watchtower", "EndpointID": "82f1dc87603da0987328f6121d17aba406aabe60950323696113c18cc615df1e", "MacAddress": "a6:77:64:60:76:a9", "IPv4Address": "172.18.0.2/16", "IPv6Address": "" }, "d1b1e170332524ed97244f6ec55f361481bc8f3c57cc85ea93d3ed373830f8d2": { "Name": "pmm3-server", "EndpointID": "b64b4a6bcfda8976168c8a929ac9b0790e6328afa07cd6d9237d64041d2fbf95", "MacAddress": "62:cd:7a:76:3d:33", "IPv4Address": "172.18.0.3/16", "IPv6Address": "" } }, "Options": {}, "Labels": {} } ] ``` ---
**Author:** ![sunpraveen](https://avatars.discourse-cdn.com/v4/letter/s/77aa72/32.png) [@sunpraveen](https://forums.percona.com/u/sunpraveen)\ **Post date:** [May 19, 2025, 6:20am UTC](https://forums.percona.com/t/pmm-v3-update-not-possible/37463/4 "2025-05-19T06:20:35Z")
I have the same issue. I am trying to upgrade PMM from version 3.0.0 to 3.1.0 but I end up with the same issue - “Failed to check watchtower host”. ```auto # docker inspect pmm-network [ { "Name": "pmm-network", "Id": "65bfb9daa36b5d73c1f9a553ddsdfsfg4252311af6c4edbb236090092abc0e879a83ed730b", "Created": "2025-03-15T14:28:12.851612135Z", "Scope": "local", "Driver": "bridge", "EnableIPv4": true, "EnableIPv6": false, "IPAM": { "Driver": "default", "Options": {}, "Config": [ { "Subnet": "172.20.0.0/16", "Gateway": "172.20.0.1" } ] }, "Internal": false, "Attachable": false, "Ingress": false, "ConfigFrom": { "Network": "" }, "ConfigOnly": false, "Containers": { "83c949821b3f1e27cf7c601eb4fa4e748211960dd7972de87623ffdeb7a88c1d": { "Name": "watchtower", "EndpointID": "29845a6bebc02bfe55796de714060f55b5a324dfsd5398b5c58b17f9e93552d472e2d6e", "MacAddress": "7m:y6:d8:5q:76:6c", "IPv4Address": "172.20.0.2/16", "IPv6Address": "" }, "d005616a8328cc3d836c6124a70cb9f3f83f528ad47a2a6223b3e49f56296503": { "Name": "pmm-server", "EndpointID": "7ab4cf7c923c4e1263f72d677sdddad579d9aa0fg56161f5748293a35b2ccb9f100de420d5b", "MacAddress": "e2:67:04:d0:c9:7b", "IPv4Address": "172.20.0.3/16", "IPv6Address": "" } }, "Options": {}, "Labels": {} } ] ``` ![PMM_Upgrade_Error](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/3X/f/a/faa92bceab9eb43b5a7254cdf548213a688fd0a8.jpeg) ---
**Author:** ![DxT](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/dxt/32/21144_2.png) [@DxT](https://forums.percona.com/u/DxT)\ **Post date:** [May 29, 2025, 3:40pm UTC](https://forums.percona.com/t/pmm-v3-update-not-possible/37463/5 "2025-05-29T15:40:17Z")
Im having the same issue here, both containers pmm-server and watchtower are in the same network , token and watchtower hostname are correctly set , but the update app wizard still complain about it is unable to check watchtower host. I made it manually . Stop and remove ctnr ```auto docker stop pmm-server && docker rm pmm-server ``` percona/pmm-server:3.2.0 ```auto docker run --detach --restart always \ --publish 443:8443 \ --env PMM_WATCHTOWER_HOST=9436f0c11113 \ --env PMM_WATCHTOWER_TOKEN=28955d573bd9f89e267aeb9d0a11111c \ --volume pmm-data:/srv \ --network=pmm-network \ --name pmm-server \ percona/pmm-server:3.2.0 ``` check new version ```auto docker exec -it pmm-server bash -c 'pmm-admin --version' ``` results ```auto ProjectName: pmm-admin Version: 3.2.0 PMMVersion: 3.2.0 Timestamp: 2025-05-23 08:45:18 (UTC) FullCommit: 60c952647f6476f651083dbd9b47f02343636998 ``` ---
**Author:** ![nurlan](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/nurlan/32/1523_2.png) [@nurlan](https://forums.percona.com/u/nurlan)\ **Post date:** [June 2, 2025, 9:27am UTC](https://forums.percona.com/t/pmm-v3-update-not-possible/37463/6 "2025-06-02T09:27:46Z")
Hi, can you run docker inspect pmm-server and docker inspect watchtower and share output, please? Could you also share how did you setup it? ---
**Author:** ![bart.schelstraete](https://avatars.discourse-cdn.com/v4/letter/b/82dd89/32.png) [@bart.schelstraete](https://forums.percona.com/u/bart.schelstraete)\ **Post date:** [June 5, 2025, 11:41am UTC](https://forums.percona.com/t/pmm-v3-update-not-possible/37463/7 "2025-06-05T11:41:15Z")
and same problem over here ---
**Author:** ![nurlan](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/nurlan/32/1523_2.png) [@nurlan](https://forums.percona.com/u/nurlan)\ **Post date:** [June 8, 2025, 2:59pm UTC](https://forums.percona.com/t/pmm-v3-update-not-possible/37463/8 "2025-06-08T14:59:31Z")
Hi, can you run docker inspect pmm-server and docker inspect watchtower and share output, please? Could you also share how did you setup it? ---
**Author:** ![Evgeniy\_Patlan](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/evgeniy_patlan/32/41_2.png) [@Evgeniy\_Patlan](https://forums.percona.com/u/Evgeniy_Patlan)\ **Post date:** [June 11, 2025, 12:37pm UTC](https://forums.percona.com/t/pmm-v3-update-not-possible/37463/9 "2025-06-11T12:37:07Z")
I was trying to reproduce this issue but everything works for me. As Nurlan suggested you can run docker inspect and docker logs. This information would be useful for investigation ---
**Author:** ![nurlan](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/nurlan/32/1523_2.png) [@nurlan](https://forums.percona.com/u/nurlan)\ **Post date:** [June 11, 2025, 2:42pm UTC](https://forums.percona.com/t/pmm-v3-update-not-possible/37463/10 "2025-06-11T14:42:28Z")
> [@DxT](#): > > `--env PMM_WATCHTOWER_HOST=9436f0c11113` PMM\_WATCHTOWER\_HOST value should contain schema://host:port, e.g.: `--env PMM_WATCHTOWER_HOST=http://watchtower:8080` ---
**Author:** ![bart.schelstraete](https://avatars.discourse-cdn.com/v4/letter/b/82dd89/32.png) [@bart.schelstraete](https://forums.percona.com/u/bart.schelstraete)\ **Post date:** [July 10, 2025, 2:48pm UTC](https://forums.percona.com/t/pmm-v3-update-not-possible/37463/11 "2025-07-10T14:48:04Z")
see the inspect output. Same problem with the new 3.3.0 > **[Context – share whatever you see with others in seconds](https://ctxt.io/2/AAB4D0AEFg)** ---
**Author:** ![Naresh9999](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/naresh9999/32/5568_2.png) [@Naresh9999](https://forums.percona.com/u/Naresh9999)\ **Post date:** [July 10, 2025, 5:03pm UTC](https://forums.percona.com/t/pmm-v3-update-not-possible/37463/12 "2025-07-10T17:03:25Z")
@nurlan Here, as per PMM3 documentation, does **your\_watchtower\_host** mean the PMM server hostname? > **[Percona Monitoring and Management - Docker volumes (recommended)](https://docs.percona.com/percona-monitoring-and-management/3/install-pmm/install-pmm-server/deployment-options/docker/run_with_vol.html#installation-steps)** > > Docker volumes provide the recommended storage configuration for PMM Server in production environments. PMM Server Host: **tpmm101** (Docker Setup) docker run --detach --restart always –publish 443:8443 –env PMM\_WATCHTOWER\_HOST=http:// **tpmm101** :8080 –env PMM\_WATCHTOWER\_TOKEN=your\_watchtower\_token –volume pmm-data:/srv –network=pmm-network –name pmm-server percona/pmm-server:3 ---
**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 10, 2025, 7:31pm UTC](https://forums.percona.com/t/pmm-v3-update-not-possible/37463/13 "2025-07-10T19:31:12Z")
@Naresh9999, **your\_watchtower\_host** should be the hostname of the docker container which is running watchtower. Since both watchtower and pmm containers are in the same network, hostnames can be resolved using dockers internal DNS. ---
**Author:** ![Naresh9999](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/naresh9999/32/5568_2.png) [@Naresh9999](https://forums.percona.com/u/Naresh9999)\ **Post date:** [July 11, 2025, 2:41am UTC](https://forums.percona.com/t/pmm-v3-update-not-possible/37463/14 "2025-07-11T02:41:15Z")
Got it @matthewb @nurlan But I have observed the same in my case as well. When we upgrade the PMM from 2.44.0 to 3.1.0 or a higher version, I think the PMM\_WATCHTOWER\_HOST=[http://watchtower:8080](http://watchtower:8080) is like this. But when we install PMM 3.1.0 or a higher version, then we have option that we can enter the host name of the PMM server like this. docker run --detach --restart always –publish 443:8443 –env PMM\_WATCHTOWER\_HOST=http:// **tpmm101** :8080 –env PMM\_WATCHTOWER\_TOKEN=your\_watchtower\_token –volume pmm-data:/srv –network=pmm-network –name pmm-server percona/pmm-server:3 So this time the PMM\_WATCHTOWER\_HOST=http:// **tpmm101** :8080 like this. In this case, while upgrading to 2.44.0 and installing PMM 3.1.0 directly, they are taking different PMM\_WATCHTOWER\_HOST values. May this might be the issue? ---
**Author:** ![Naresh9999](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/naresh9999/32/5568_2.png) [@Naresh9999](https://forums.percona.com/u/Naresh9999)\ **Post date:** [July 11, 2025, 10:53am UTC](https://forums.percona.com/t/pmm-v3-update-not-possible/37463/15 "2025-07-11T10:53:10Z")
@matthewb @nurlan In my case, which one should be correct? PMM\_WATCHTOWER\_HOST=[http://watchtower:8080](http://watchtower:8080) OR PMM\_WATCHTOWER\_HOST=[http://tpmm101:8080](http://tpmm101:8080)