Enketo Web Form failing to load

Support
1

No

Self-hosted Ubuntu

1. What is the issue? Please be detailed.
I have an XLSform that is successfully validating, but does not load in Enketo during the testing in Central. Gives an error. See screenshot below:

image
image744×418 11.6 KB

2. What steps can we take to reproduce this issue?
Try open it from this link: https://crr.health.gov.za/-/PWL5m9D3lpVPqeBrmWw8MSvN3KkVKlb

3. What have you tried to fix the issue?
Disabled firewall on Ubuntu Server. But i still get the error.

4. Upload any forms or screenshots you can share publicly below.
See attached XLSForm.
Web CRR_20250514_version 1.0 (2).xml (2.1 MB)
Web CRR_20250514_version 1.0.xlsx (554.0 KB)

2

I notice your form has 16,482 options on the choices tab, which is probably more than the average form. And the browser shows a 504 time-out error.

Screenshot 2025-05-16 at 10.24.56 AM
Screenshot 2025-05-16 at 10.24.56 AM1080×182 26 KB

What are the specifications of your server? Do other forms work as expected?

1 Like
3

Thanks for getting back to me.

What server specifications should I check? RAM, firewall?

Thanks once again

4

What can I use to manage these long list choices better?

5

It's not the number of choices that are the problem. You can confirm that at https://getodk.org/xlsform.

I bet there is some networking issue that is preventing the form from loading. Does a simple one question form work on the server?

Try running commands at Form Loading Error when using Enketo on ODK Central - #4 by yanokwa to check what's happening inside the Enketo container.

6

Thanks Yaw,

I ran those commands and I am getting zero(0). What could be the problem /cause? I need this to work so that non-Android users can make submissions using enketo forms.

7

Good day Yaw,

I am also seeing this error :

image.png
image.png1341×660 53 KB

Thanks

8

Those commands test whether Enketo can go out on the Internet and access your own domain (https://crr.health...). It's failing because of how your network is configured. It's usually because of a DNS issue. That's something you'll need to talk with your IT team about.

1 Like