Failed to load resource: the server responded with a status of 500 (Internal Server Error)

[dmaritim (Daniel Kiprono Maritim)]

Am get the following error; what could be the problem?

JQMIGRATE: Migrate is installed, version 3.0.0
script:1

Failed to load resource: the server responded with a status of 500 (Internal Server Error)
index.action:1 Refused to execute script from ‘https://url/api/files/script?_rev=483a1a7’ because its MIME type (‘application/json’) is not executable, and strict MIME type checking is enabled.
index.js:26 Initializing Header Bar v28.0.2
form.js?_rev=483a1a7:242 Ouwt loaded
icon.png:1 Failed to load resource: the server responded with a status of 500 (Internal Server Error)

[Gassim (AL-Gassim Sharaf Addin)]

Hi @dmaritim

Thank you for your post! Where are you seeing this issue?

If it’s in the browser only, maybe you need to clear cache in the same way as @kpvandivier suggested for a similar issue:

@kpvandivier

, if you visit the app and perform a “hard reload”, it should fix the app in Chrome for you.

You can hard reload by using Cmd-Shift-R on Mac or Ctrl-Shift-R on other operating systems, or right-clicking on the reload button while the browser developer tools are open, which is how I got this screenshot:

The issue is caused by a stuck service worker that has cached an old version of the app that has that bug and is serving that old version of the app instead of the new one that you see in other browsers – it seems that the old version is only cached in Chrome for you. If that diagnosis is right, the hard reload which bypasses the service worker should fix it Future versions of this app should be able to fix this on their own without needing a hard reload.

Hopefully this works for you – let us know how it goes!

Thanks!

[dmaritim (Daniel Kiprono Maritim)]

@Gassim Thank you for this response. I will tried it out and give you my outcome.

@Gassim it hard reload resolved the issue. Thank you.

[Gassim (AL-Gassim Sharaf Addin)]

Thank you! Glad to hear that, please mark the post as solved.

[Kenyuri (Raphael Kenyuri)]

@Gassim I encountered an issue when trying to access a document with external access enabled in DHIS2 version 2.41.5. Despite having set the document’s sharing settings to external access,

I received the following error when trying to access the document through the direct API link:

HTTP Status 500 – Internal Server Error
Message: Authentication principal is not supported; principal: anonymousUser
...
java.lang.RuntimeException: Authentication principal is not supported; principal:anonymousUser
...

What Works and What Doesn’t:

• Works: In DHIS2 v2.40.8.2, the same configuration with the same document sharing settings works as expected, allowing external access without a login.

• Doesn’t Work: In DHIS2 v2.41.5, despite setting external access correctly, the same API call results in a 500 Internal Server Error caused by a security/authentication issue.

I would appreciate any help on resolving this. Thanks.