We created and deployed some forms earlier this year and have been collecting data from the users but from last week the forms have not been loading, neither can we upload data from app or deploy new project forms from the Admin console.
Error- 504 Gateway Time-out
Considering that this is a production application, we hope to hear from you as soon as possible.
Hi @incentro,
Welcome to the community! Would you mind sharing with us the server (OCHA or HHI) you are using.
Have a great day!
Hello and thanks @Kal_Lam
We forked a master branch (commit: c4563ed) of the Kobotoolbox and are hosting it on Google cloud - docker.
Hi @incentro,
Would you mind checking your survey project and see if they are archived. You should get an error message when you try to access your survey project when they are archived.
Have a great day!
Hi @Kal_Lam
I can confirm that the projects are not archived as shown in the screenshot below;
Hi @incentro,
The screenshot that you shared shows that you were able to deploy your survey form successfully. Could you confirm that you deployed them today!
If you are able to deploy them successfully, you should also be able to submit your data to the server as well as pull blank forms to your android app successfully. Kindly please ensure the settings of your KoBoCollect android app.
Have a great day!
Hi @Kal_Lam
The survey from today took forever to deploy and one cannot open or download them even using the admin web interface…
There are other surveys from January this year that used to work but they too cannot be accessed.
Operations freeze indefinitely when any of these are clicked on.
@incentro I have kobo toolbox instance in GCP but haven’t encountered such, whats the status of the docker containers?
You can check container logs or restart any of the containers and see if something is not right
docker logs {container_id} will give you log for that specific container
docker ps -a will list all containers, you can check whether they are running or stopped
docker inspect {container_id} Will give you detailed information about the container
docker restart {container_id} Will restart a container
Hi @stephenoduor
Thanks for your response.
We see nothing on our containers/logs … even after restarting, the issue persists.
Any other tips?
Our Client at this point is quite frustrated
Found a solution - there was a problem with assigning SSL certicates and hence getting a healthy status code for kc.kobotoolkit
Thanks for all the help.!
