@linxd I reproduced your incorrect configuration names and confirmed my assumptions. v2.31.1 does not startup due to the postgis check which will naturally fail in h2 database. v2.29 “appears” to successfully start (but it is not). v2.29 also starts up on an h2 database and if you try to access any endpoint on that instance it will not work.
Simply correct the configuration names as mentioned in the sample reference above. It will work now.
@linxd 2.29 also will not work with your old conf. i confirmed it. 2.29 will only “appear to startup”, the logs does not show any errors or visible startup issue. But its not connecting to postgres.
To confirm whether it is working, after deploying the application, access the dhis2 instance and login using valid credentials. If you are able to see the login page and login correctly, only then it is considered working.