1. What is the issue? Please be detailed. I have an ODK Central instance hosted on a machine behind a NAT. I've used Rathole to tunnel the ODK Central instance to a public IP (hosted on Digital Ocean) and everything works normally (DNS, form upload, login, project listing, email). However, when t…

Thanks @ktuite , this pointed me in the right direction. I now have the OpenRosa API correctly resolving forms to ODK Collect. I hadn't realized that it would inject the $PORT if the port was non-standard, but it makes sense that it would (e.g., the form list is resolves as $DOMAIN:$HTTPS_PORT/v1/.…

Hi @jniles , I'm not totally sure about your situation but I'll write some thoughts that I hope are useful clues and don't lead you astray... POST /-/transform/xform/[id string] is about Central communicating with Enketo (- is a proxy to the enketo service running in its own container). I expect …

Thanks for the reply @ktuite ! It gives me somewhere to start digging. I'm suspecting somewhere the PORTs are either being used in a way that conflicts with my port-forwarding schemes. I'll do some digging and maybe ping back when I have more details or questions. Thanks!

Hi Niles I am in a similar situation Can you share the relevant portions of ,env and docker-compose for enketo please. How did you rebuild enketo only? Did yo also have to rebuild redis ? Thanks Vivek

[image] jniles: If anyone is also running behind a reverse proxy, the way I solved this issue was to maintain the $HTTPS_PORT and $HTTP_PORT as 443 and 80 respectively, and manually update the docker-compose.yml to use my own non-standard ports (e.g. 8443, 8080). Collect looks for the forms at $…

Hi @nmambre , I retained 80 and 443 in .env for the HTTP_PORT and HTTPS_PORT variables, respectively. However, I modified docker-compose.yml to use the non-standard ports I desired. Here is my only change (generated using git diff): [image] I hope that helps!

Hi Dr. Gupta, I didn't rebuild either service. As mentioned below , the only change made was to the docker-compose ports. This makes the proxy transparent to ODK Central. Hope this helps!

OK @jniles thank you for the explanation. I made a similar change to the docker compose, and now get redirection errors, so I think my problem is now with to reverse proxy configuration. I'll have to read more about that.

So from what I can make out, the docker compose file is not using the .env configuration for nginx container. Now in nginx container, the internal ports 80 has been mapped to host port 5050 and nginx internal port 443 has been mapped to the host port 5051. This means I will need to proxy pass traf…

Did you check Configuring Upstream SSL ? This post helped me with the issues I had, maybe some is relevant for you. [image] ODK Central CI/CD (non default ports) Support Hi Nelson, I was able to deploy ODK Central on Hetzner using Elestio. Here are the steps that I perfor…

Thanks Nmambre My issue is resolved. It was to do with enketo container unable to reach my ODK central domain I have detailed my steps at: [image] Enketo not loading Support I have managed to RESOLVE The Error using various suggestions in the forum Step 1: …

Forms not downloading or rendering on reverse-proxied, tunneled ODK Central server

Support

Dr_Vivek_Gupta June 1, 2024, 6:43am 12

Thanks Nmambre
My issue is resolved. It was to do with enketo container unable to reach my ODK central domain
I have detailed my steps at:

Best Wishes
Vivek