# ERROR Failed to get a response

**URL:** <https://forum.communityhealthtoolkit.org/t/error-failed-to-get-a-response/2294>\
**Category:** Technical Support\
**Created:** [November 10, 2022, 6:26pm UTC](https://forum.communityhealthtoolkit.org/t/error-failed-to-get-a-response/2294 "2022-11-10T18:26:22Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![mrjones](https://communityhealthtoolkit.b-cdn.net/user_avatar/forum.communityhealthtoolkit.org/mrjones/32/681_2.png) [@mrjones](https://forum.communityhealthtoolkit.org/u/mrjones)\
**Post date:** [November 14, 2022, 11:03pm UTC](https://forum.communityhealthtoolkit.org/t/error-failed-to-get-a-response/2294/5 "2022-11-14T23:03:58Z")

</div>

@oyierphil - thanks so much for the call earlier today trying to debug this issue. The error you were seeing `ERROR Failed to get a response` was from when you were running [CHT Conf](https://github.com/medic/cht-conf/).

After you and I were looking around, I was able to find this error in your `nginx` logs located in `/srv/storage/medic-core/nginx/logs/startup.log` in the `medic-os` container:

```auto
==> /srv/storage/medic-core/nginx/logs/startup.log <==
nginx: [emerg] invalid number of arguments in "server_name" directive in /srv/software/medic-core/v2.1.1/x64/etc/nginx/nginx.conf:29
nginx: [emerg] invalid number of arguments in "server_name" directive in /srv/software/medic-core/v2.1.1/x64/etc/nginx/nginx.conf:29
nginx: [emerg] invalid number of arguments in "server_name" directive in /srv/software/medic-core/v2.1.1/x64/etc/nginx/nginx.conf:29
nginx: [emerg] invalid number of arguments in "server_name" directive in /srv/software/medic-core/v2.1.1/x64/etc/nginx/nginx.conf:29

```

Looking at the `nginx` config file `/srv/software/medic-core/v2.1.1/x64/etc/nginx/nginx.conf`, on line 29 it looked like this where `server_name` has no argument:

```auto
    server {
        listen 80;
        server_name ;
        error_log /srv/storage/medic-core/nginx/logs/error.log;
        location / {
            return 301 https://$host$request_uri;
        }
    }

```

It was missing the `_` which is used as a [catch all](https://nginx.org/en/docs/http/server_names.html#miscellaneous_names). The fix was to add it back so it looks like this:

```auto
    server {
        listen 80;
        server_name _;
        error_log /srv/storage/medic-core/nginx/logs/error.log;
        location / {
            return 301 https://$host$request_uri;
        }
    }

```

I then rebooted `nginx` inside the container with `/boot/svc-restart medic-core nginx`.

---

_[View the full topic](https://forum.communityhealthtoolkit.org/t/error-failed-to-get-a-response/2294)._