ERROR Failed to get a response

Technical Support
5

@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.

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:

==> /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:

    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. The fix was to add it back so it looks like this:

    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.