How to configure extra_hosts directives in kobo-docker project

[Ruchi Kansal]

Hi

I am trying to install kobotoolbox on the remote server. I put the entries in 'etc/hosts' directory but did not uncomment the extra-hosts directives in the docker-compose.server.yml file because it was giving me the "yaml.parser.parsererror" error message if i did so. So i kept on moving to the next step. It was working fine when i tried "kc-local.kobotoolbox.org" on the linux system. When i created one form and tried to deploy the form it was giving me the error whose screenshot is attached below. 

I also searched on google about this error and i found that we should add the IP address with the host in 'etc/hosts'. But i have already done it.

So basically my question is that how should i configure the extra-hosts directives.

And also when i tried the url "kc-local.kobotoolbox.org" on another system it was not loading the page.

Thanks and Regards

Ruchi

[Esmail Fadae]

Hi, Ruchi. I'm not so sure you should be using the HTTPS, server configuration. What is certain that you won't be able to do so using the domain kobotoolbox.org, because it's ours and we're the only ones with valid SSL certificates for it. Stick to the local configuration if you're not going to have your own publicly-accessible domain and your own SSL certificates. BTW, your parsing errors are likely due to uncommenting out one of the comments (as opposed to the YML-valid content of the `extra_hosts` directive).

[Ruchi Kansal]

Hi Esmail
Thanks for the solution
I understood the first thing that we can use our own domain name now because you have updated the file recently for that purpose. But what about the error message whose screen shot I have attached.
How to tackle with that one.

Thanks
Ruchi

[Esmail Fadae]

BTW, your parsing errors are likely due to uncommenting out one of the comments (as opposed to the YML-valid content of the `extra_hosts` directive).

Regardless, you probably won't need that if you've already got your own domain; as the documentation states, it's for "testing on a server that is not publicly accessible". If you do choose to use them, be sure not to use the example addresses at our domain.

[Ruchi Kansal]

Hi Esmail,

Thanks a lot for your response !

 I tried it with our own domain name. But still got the same error message(file attached). Can this error be related to the ssl certificate and key? Because my certificate is self-signed wildcard ssl certificate. But the error is related to form as shown in the screenshot. Other all pages are working.

Regards

Ruchi

[Esmail Fadae]

"Name or service not known" indicates to me that the `kpi` container can't resolve the address `kc-local.roversoft.com`. Do you actually have DNS records for that address? It doesn't resolve for me. I'd prefer if you'd try testing with our "local" configuration first and then figure out your server issues on your own. If you don't have previous web server administration experience, I'm not sure this is the place to start and I can't support you with things like setting up DNS and getting CA-signed SSL certificates.