You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can confirm this on self-hosted Umami 3.3.0 (Docker, Postgres 15). Both Edit and Delete are affected, not just Edit.
I dug a bit deeper with browser DevTools and can share what I found in case it helps narrow down the root cause:
No network request for the edit/delete action ever reaches the server (nothing shows up in the Network tab, and server logs show zero activity for the attempted request).
The browser console does show an error, contrary to what's reported above:
Uncaught (in promise) TypeError: Failed to fetch
at ef (_next/static/chunks/1of_q-19x1ugz.js:1:141786)
This is a minified client chunk, so I can't pin down the exact source line, but it's the same stack trace every time, reproducible in a completely clean browser profile (no extensions, incognito).
Alongside it, the console logs repeated net::ERR_BLOCKED_BY_CLIENT for other resources on the page.
Separately (possibly unrelated, possibly not), our instance can't reach api.umami.is from the server's network (telemetry/update-check calls to api.umami.is/v1/updates and a tracking pixel both fail to resolve). Not sure if the user edit/delete action has any dependency on that call succeeding, but flagging the coincidence in case it's relevant.
Ruled out on our end: browser extensions, browser cache (tested in incognito), and stale app state (fully restarted the Umami container, issue persisted identically).
Happy to grab more diagnostics (HAR file, etc.) if useful.
Activity
unLieb commentedon Aug 16, 2026
Can confirm this on self-hosted Umami 3.3.0 (Docker, Postgres 15). Both Edit and Delete are affected, not just Edit.
I dug a bit deeper with browser DevTools and can share what I found in case it helps narrow down the root cause:
net::ERR_BLOCKED_BY_CLIENTfor other resources on the page.api.umami.isfrom the server's network (telemetry/update-check calls toapi.umami.is/v1/updatesand a tracking pixel both fail to resolve). Not sure if the user edit/delete action has any dependency on that call succeeding, but flagging the coincidence in case it's relevant.Happy to grab more diagnostics (HAR file, etc.) if useful.
fix: preserve menu item actions in admin dropdowns. Closes #4453.
bennetgallein commentedon Sep 3, 2026
@mikecao can we get a release to fix this? It's a bit annoying that we cannot edit users & websites.
Upgrade Umami to 3.4.0 for Codex and Grok Bot MCP (#1)
Merge upstream umami v3.4.0 (#6)