It seems to be happening for all tracker programmes.
It also happens for programmes that I built myself.
Event input works without any issues - the error only occurs when using Enrollment input.
I am logged in as a superuser, so it doesn’t appear to be a user authority issue.
The programmes open and work correctly in Capture.
Has anyone seen this before, or have any suggestions for what might be causing it?
Please update the Line Listing app to the latest version by going to the App Management app then when testing again, use the browser’s Guest mode.
Debug and share error from the Network log (F12, DevTools → Network Tab):
a) Select enrollment
b) Select the tracker program
c) Open the Network tab - Click F12 to open the DevTools then select Network tab
d) Select ‘program dimensions’ while monitoring the network tab - check the request for the dimensions and get the error from the response:
(Please note that if we get a generic error - one that could apply to any general issue, then we will need to check the Catalina.out log without the authentication/sensitive info)
e) Please share the error from the response + screenshot with the network tab (request/response)
I checked App Management, but the Line Listing app is not listed there, so I wasn’t able to update it separately. Our instance is running DHIS2 2.41.8.2.
I then tested in a Chrome Incognito window and reproduced the issue.
Here is the Screenshot of the Network log showing the failed request (403) and the Screenshot of the Response from the failed request
Yes, this is a generic issue. It’s not clear why you’re facing this issue on the server side. Let’s please grab the Catalina.out log (without the authentication/sensitive info) then share it here please.
Troubleshooted your images (very helpful!) with Claude which said that it is something that needs to be solved with BAO, not an DHIS2 issue:
In the Response tab of the failing dimensions request, the body is:
403 Forbidden — nginx/1.30.3
That’s an nginx error page, not a DHIS2 error. It means the request is being blocked by the reverse proxy / web application firewall sitting in front of DHIS2, before it reaches the DHIS2 application server.
This is a hosting/infrastructure configuration issue on the instance, so the next step is with BAO - ask them to check the nginx access/error logs and any WAF (e.g. ModSecurity) logs for the request:
GET /api/analytics/enrollments/query/dimensions?...
That will show exactly which proxy/firewall rule is returning the 403 so they can whitelist it. The Event input works because its (near-identical) request isn’t being caught by the same rule.
