# Insufficient access permissions error after upgrade to pmm 3.5.0 **URL:** \ **Category:** PMM 3.x\ **Created:** [November 25, 2025, 1:05pm UTC](https://forums.percona.com/t/insufficient-access-permissions-error-after-upgrade-to-pmm-3-5-0/39783 "2025-11-25T13:05:51Z")\ **Posts on this page:** 10\ **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:** [November 25, 2025, 1:05pm UTC](https://forums.percona.com/t/insufficient-access-permissions-error-after-upgrade-to-pmm-3-5-0/39783/1 "2025-11-25T13:05:51Z")
Hi! PMM was automatically updated to version 3.5.0. After the upgrade, the dashboard was not accessible — we only saw the “Upgrade in progress” screen. After restarting, the dashboard became accessible again, but both Failed Advisors and the Upgrade Panel show the message “Insufficient access permissions” (logged in as admin). Additionally, the update page (/pmm-ui/updates) is not accessible. Instead, we receive a 500 error with the following server response: {“error”: “Internal server error.”, “code”: 13, “message”: “Internal server error.”, “details”: {}} In the dashboard, the DevTools show the following errors: Response from /v1/platform/server and /v1/platform/user: { “error”: “unknown service platform.v1.PlatformService”, “code”: 12, “message”: “unknown service platform.v1.PlatformService”, “details”: {} } Response from /v1/server/settings: { “error”: “Internal server error.”, “code”: 13, “message”: “Internal server error.”, “details”: {} } The updates page did work right after the 3.5.0 update, before updating the clients. Is this a known issue, and is there any fix available? ![grafik](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/3X/b/f/bfcbfbcc46237e1c424f7b9959b7d75fa19f2bc8.png) ---
**Author:** ![Michael\_Okoko](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/michael_okoko/32/5688_2.png) [@Michael\_Okoko](https://forums.percona.com/u/Michael_Okoko)\ **Post date:** [November 25, 2025, 8:29pm UTC](https://forums.percona.com/t/insufficient-access-permissions-error-after-upgrade-to-pmm-3-5-0/39783/2 "2025-11-25T20:29:36Z")
Yeah this is weird, is the server logs accessible (either from the UI or from /srv/logs)? And is there anything in there that might help? ---
**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:** [November 26, 2025, 3:07pm UTC](https://forums.percona.com/t/insufficient-access-permissions-error-after-upgrade-to-pmm-3-5-0/39783/3 "2025-11-26T15:07:02Z")
I found this error in the log (docker exec -it pmm-server cat /srv/logs/pmm-managed.log | tail -100), cut to essentials: level=error msg="RPC /server.v1.ServerService/GetSettings panic: runtime error: index out of range [0] with length 0 [github.com/percona/pmm/managed/services/server.(\*Server).getInternalPgQANAgent](http://github.com/percona/pmm/managed/services/server.(*Server).getInternalPgQANAgent) server.go:756 [github.com/percona/pmm/managed/services/server.(\*Server).GetSettings](http://github.com/percona/pmm/managed/services/server.(*Server).GetSettings) server.go:533 Also, under Nodes the pmm-server shows “No clients”. I remember there were always a client listed here before. Is this expected or related to the issue? ![grafik](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/3X/e/7/e729922de661008bfd7889948770ee6e6257674d.png) ---
**Author:** ![Michael\_Okoko](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/michael_okoko/32/5688_2.png) [@Michael\_Okoko](https://forums.percona.com/u/Michael_Okoko)\ **Post date:** [November 26, 2025, 6:08pm UTC](https://forums.percona.com/t/insufficient-access-permissions-error-after-upgrade-to-pmm-3-5-0/39783/4 "2025-11-26T18:08:07Z")
Yeah, pmm-server not having any service attached to it is likely related to your issue. Can you confirm that the pmm-agent is connected to the pmm server? e.g with `pmm-admin status`. Also can you help review pmm-agent logs too (in /srv/logs). ---
**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:** [November 27, 2025, 1:03pm UTC](https://forums.percona.com/t/insufficient-access-permissions-error-after-upgrade-to-pmm-3-5-0/39783/5 "2025-11-27T13:03:34Z")
pmm-admin status output: Agent ID : ```auto Agent ID : pmm-server Node ID : pmm-server Node name: pmm-server PMM Server: URL : https://127.0.0.1:8443/ Version: 3.5.0 PMM Client: Connected : true Time drift : 39.174µs Latency : 193.893µs Connection uptime: 100 pmm-admin version: 3.5.0 pmm-agent version: 3.5.0 Agents: d331c1ec-f698-48xx2-b6b1-9xd19779cc89 node_exporter Running 42000 ``` and /srv/logs doesn’t contain anything that could be relevant. ---
**Author:** ![Michael\_Okoko](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/michael_okoko/32/5688_2.png) [@Michael\_Okoko](https://forums.percona.com/u/Michael_Okoko)\ **Post date:** [December 3, 2025, 10:20pm UTC](https://forums.percona.com/t/insufficient-access-permissions-error-after-upgrade-to-pmm-3-5-0/39783/6 "2025-12-03T22:20:46Z")
Hi, sorry about this - for the panic, it was a case we didn’t handle correctly and the fix is merged/slated for the next release - though it’s still weird that it renders advisors and updates page inaccessible. ---
**Author:** ![Michael\_Okoko](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/michael_okoko/32/5688_2.png) [@Michael\_Okoko](https://forums.percona.com/u/Michael_Okoko)\ **Post date:** [December 19, 2025, 12:36pm UTC](https://forums.percona.com/t/insufficient-access-permissions-error-after-upgrade-to-pmm-3-5-0/39783/7 "2025-12-19T12:36:19Z")
Hi @Marvin_Stelter btw are you able to share how the upgrade was performed? ---
**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:** [January 7, 2026, 10:06am UTC](https://forums.percona.com/t/insufficient-access-permissions-error-after-upgrade-to-pmm-3-5-0/39783/8 "2026-01-07T10:06:30Z")
Automatically, I only saw the notification in the morning that an upgrade was currently taking place.But the notification didn’t go away, the process probably got stuck. I then restarted the container, at that point everything was still working, only a day later did the errors mentioned above occur. ---
**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:** [February 9, 2026, 9:12am UTC](https://forums.percona.com/t/insufficient-access-permissions-error-after-upgrade-to-pmm-3-5-0/39783/9 "2026-02-09T09:12:31Z")
Error has been fixed with the 3.6.0 update, thanks! ---
**Author:** ![Ivan\_Groenewold](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ivan_groenewold/32/6299_2.png) [@Ivan\_Groenewold](https://forums.percona.com/u/Ivan_Groenewold)\ **Post date:** [February 9, 2026, 5:24pm UTC](https://forums.percona.com/t/insufficient-access-permissions-error-after-upgrade-to-pmm-3-5-0/39783/10 "2026-02-09T17:24:07Z")