ODK Central not working

Support
1

1. What is the issue? Please be detailed.
ODK Central instance not working. When restarting the container i get this log:

192.168.12.27 - - [02/Jun/2025:08:41:03 +0000] "GET / HTTP/1.1" 301 169 "-" "curl/7.81.0" "-"
172.18.0.1 - - [02/Jun/2025:08:42:51 +0000] "GET / HTTP/1.1" 301 169 "-" "curl/7.81.0" "-"
writing fresh nginx templates...
starting nginx for letsencrypt...
2025/06/02 08:44:26 [warning] Could not find non-zero size keyfile file '/etc/nginx/ssl/nginx.default.key' in '/etc/nginx/conf.d/odk.conf'
2025/06/02 08:44:26 [warning] Could not find non-zero size keyfile file '/etc/letsencrypt/live/${CERT_DOMAIN}/privkey.pem' in '/etc/nginx/conf.d/odk.conf'
2025/06/02 08:44:26 [warning] Could not find non-zero size fullchain file '/etc/nginx/ssl/nginx.default.crt' in '/etc/nginx/conf.d/odk.conf'
2025/06/02 08:44:26 [warning] Could not find non-zero size fullchain file '/etc/letsencrypt/live/${CERT_DOMAIN}/fullchain.pem' in '/etc/nginx/conf.d/odk.conf'
2025/06/02 08:44:26 [warning] Could not find non-zero size chain file '/etc/letsencrypt/live/${CERT_DOMAIN}/fullchain.pem' in '/etc/nginx/conf.d/odk.conf'
2025/06/02 08:44:26 [error] Important file(s) for '/etc/nginx/conf.d/odk.conf' are missing or empty, disabling...
2025/06/02 08:44:26 [warning] Could not find non-zero size keyfile file '/etc/nginx/ssl/nginx.default.key' in '/etc/nginx/conf.d/odk.conf.nokey'
2025/06/02 08:44:26 [warning] Could not find non-zero size keyfile file '/etc/letsencrypt/live/${CERT_DOMAIN}/privkey.pem' in '/etc/nginx/conf.d/odk.conf.nokey'
2025/06/02 08:44:26 [warning] Could not find non-zero size fullchain file '/etc/nginx/ssl/nginx.default.crt' in '/etc/nginx/conf.d/odk.conf.nokey'
2025/06/02 08:44:26 [warning] Could not find non-zero size fullchain file '/etc/letsencrypt/live/${CERT_DOMAIN}/fullchain.pem' in '/etc/nginx/conf.d/odk.conf.nokey'
2025/06/02 08:44:27 [warning] Could not find non-zero size chain file '/etc/letsencrypt/live/${CERT_DOMAIN}/fullchain.pem' in '/etc/nginx/conf.d/odk.conf.nokey'
2025/06/02 08:44:27 [info] Starting the Nginx service
2025/06/02 08:44:27 [info] Running the autorenewal service
2025/06/02 08:44:27 [notice] 125#125: using the "epoll" event method
2025/06/02 08:44:27 [notice] 125#125: nginx/1.25.3

2. What steps can we take to reproduce this issue?
Not sure.

3. What have you tried to fix the issue?
I am thinking of upgrading the version of Central to the latest, but not sure if it is a good idea to do when the current instance is not working.

4. Upload any forms or screenshots you can share publicly below.

2

Hey, it looks like there might be an issue with the SSL certificate in your deployment. I've stumbled across a similar case before - do check out this. A server reboot resolved the problem in his case, so it might be worth trying the same here. Maybe it'll do the trick.

1 Like
3

Thank you @MinimalPotato. I am getting this error message from letsencrypt.log
"acme.messages.Error: urn:ietf:params:acme:error:rejectedIdentifier :: The server will not issue certificates for the identifier :: Invalid identifiers requested :: Cannot issue for "${domain}": Domain name contains an invalid character" And I never changed the Domain name, it has been working. Do you thing i should just upgrade Central?

4

Try deleting the nginx container and rebuilding it.

docker compose stop;
docker compose rm nginx -v;
docker compose build;
docker compose up -d;
5

Thanks Yaw. Rebuilding nginx solved the problem.