1. What is the issue? Please be detailed.
I created a new server on AWS with t2.micro for testing purposes only. On this server, I was previously able to log in and now when I am trying to use PostgreSQL backup on my local machine, I am unable to log in on the server URL.
It is showing error 500 on the server.
2. What steps can we take to reproduce this issue?
Please have a look at the screenshot which is attached here.
3. What have you tried to fix the issue?
Follow these steps
One of my research partner is also encountering 500 error code issues with an ODK Central server v1.2.1. The admin told me that it was even difficult to restart the server as the docker-compose command led to the error "cannot create temporary directory", which seems to indicate a storage space issue.
My first instinct is that it may be a general server performance issue (the original server requirements was 4 cores / 12 GB RAM / 300 GB storage) but I am wondering if I should investiga…
I am also having this issue.. but instead when i set up the ustom email config for AWS SES i cant log into central at all. not sure if there is anythign that im doing wrong there.
im changing the standard mail config from:
4. Upload any test forms or screenshots below.
What do your service logs say?
My ODK central_service_1 stat is restarting all the time. Please have look at the screenshot.