Dashboard link shows error 500 after upgrading to 2.4.3 on Azure

[mcgiga0815]

What happened?

We have upgraded from 1.6.x to 2.4.3 today. When a user logs in and then clicks on "Dashboard", error 500 is displayed. At that moment, the following error appears in the Azure Stream Log:

2026-04-16T10:24:03.3333555Z 10:24:03 web.1 | W, [2026-04-16T10:24:03.327087 #195] WARN -- : [e3e49bdd-1988-4413-9b7f-ba231d1b8700] CSP Violation: {"document-uri" => "https://sub.domain.tld/p", "violated-directive" => "script-src-elem", "blocked-uri" => "inline"}

When an administrator logs in the Dashboard is working. When I create a new user Dashboard is working too. It only seems to not work with existing users so far.

Aside from that here are very much warnings like this:

2026-04-16T10:21:48.6402102Z W, [2026-04-16T10:21:48.210932 #16] WARN -- : Unable to resolve '../flags/4x3/es-pv.svg' for missing asset '../flags/4x3/es-pv.svg' in application.css

🔬 How to reproduce

Login
Click on Dashboard

💻 Code sample

🌍 Which edition

None

🌍 Environment

• pwpush.com (Hosted)
• Docker Image – pwpush
• Docker Image – pwpush-public-gateway
• Docker Image – pwpush-worker
• Docker Image – Custom image
• Digital Ocean – App Platform
• Digital Ocean – Kubernetes Service
• Heroku
• Microsoft Azure – App Service
• Microsoft Azure – Container Instances (ACI)
• Microsoft Azure – Container Apps (ACA)
• Microsoft Azure – Kubernetes Service (AKS)
• Google Cloud – App Engine
• Google Cloud – Cloud Run
• Google Cloud – Kubernetes Engine
• AWS – Elastic Container Service (ECS)
• AWS – Kubernetes Service
• Source Code
• Other (please specify below)

Other Install location

No response

📦 App version

No response

📸 Screenshots

No response

📈 Expected behavior

No response

📎 Additional context

No response

[pglombardo]

Hi @mcgiga0815 - are you upgrading from v1.6 or is that a typo?

[mcgiga0815]

It was 1.63.x. Unfortunately I have lost my note.

[mcgiga0815]

It seems that existing pushes, created before the upgrade, don't work -> error 500.
Pushes I have created today with a user which can't access the dashboard (error 500) are working.

[pglombardo]

Could you run docker compose logs and get the stack trace for the error 500?

[mcgiga0815]

It's running on Azure as a Webservice App. Docker Compose isn't available there, is it?

Is the Webservice App still the recommended way for installation (https://docs.pwpush.com/assets/files/PWPush_Setup_Guide_For_Azure.pdf)?

[pglombardo]

Yes - unfortunately my knowledge is limited with Azure & Webservice app. This answer might help though: https://grok.com/share/bGVnYWN5LWNvcHk_62052f1a-0e1a-4bf5-9c15-8c87469c68c5

But in short summary, I suspect there is something wrong with the records but since you are only updating from v1.63.x, that doesn't make sense since nothing has changed in terms of DB records.

If you were updating from <v1.5x.x, then there is a data migration step required but that doesn't seem to be the case.

The stack trace will tell us exactly where the problem is.

[mcgiga0815]

It seems that log stream is the only possible output. I got this message while clicking on Dashboard:

2026-04-16T10:24:03.3333555Z 10:24:03 web.1 | W, [2026-04-16T10:24:03.327087 #195] WARN -- : [e3e49bdd-1988-4413-9b7f-ba231d1b8700] CSP Violation: {"document-uri" => "https://sub.domain.tld/p", "violated-directive" => "script-src-elem", "blocked-uri" => "inline"}

[pglombardo]

No that CSP error and "missing asset" are non-issues and only cosmetic.

[mcgiga0815]

The assge one okay. but the CSP occured only by users which can't access the Dashboard. When using the administrator or a new user this output was not present.