# Upgrade from 3.6 to 3.7 fails

**URL:** <https://forums.percona.com/t/upgrade-from-3-6-to-3-7-fails/40670>\
**Category:** PMM 3.x\
**Tags:** pmm\
**Created:** [April 18, 2026, 4:19pm UTC](https://forums.percona.com/t/upgrade-from-3-6-to-3-7-fails/40670 "2026-04-18T16:19:45Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ks27](https://avatars.discourse-cdn.com/v4/letter/k/c6cbf5/32.png) [@ks27](https://forums.percona.com/u/ks27)\
**Post date:** [April 18, 2026, 4:19pm UTC](https://forums.percona.com/t/upgrade-from-3-6-to-3-7-fails/40670/1 "2026-04-18T16:19:45Z")

</div>

Just pulled pmm 3.7, started as usual, but the container stays “unhealthy” and postgresgl14.log shows _a lot_ of  
2026-04-18 13:06:05.050 UTC [1175] FATAL: password authentication failed for user “pmm-managed”  
2026-04-18 13:06:05.050 UTC [1175] DETAIL: User “pmm-managed” does not have a valid SCRAM secret.  
Connection matched pg\_hba.conf line 91: “host all all 127.0.0.1/32 scram-sha-256”

Reverting to 3.6 is no problem - after editing pg\_hba.conf and change all “scram…” back to “trust”.

How can I upgrade to 3.7 w/o destroying the postgresql database?

FWIW: Upgrade from within the 3.6 container isn’t possible either as the pmm container can’t connect to the watchtower container (they _are_ on the same docker network!) but I see only sync-packets to watchtower:8080 but no answer…

ks27

---

<div class="post-metadata">

**Author:** ![ademidoff](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ademidoff/32/14234_2.png) [@ademidoff](https://forums.percona.com/u/ademidoff)\
**Post date:** [April 18, 2026, 4:41pm UTC](https://forums.percona.com/t/upgrade-from-3-6-to-3-7-fails/40670/2 "2026-04-18T16:41:19Z")

</div>

Hi

Please follow the steps as per this issue - [PMM 3.6 → 3.7.0 Docker upgrade fails: pq: password authentication failed for user "pmm-managed" during DB migration · Issue #5209 · percona/pmm · GitHub](https://github.com/percona/pmm/issues/5209#issuecomment-4183602058).