Gaia nginx container not starting

I’m trying to get a Gaia storage hub working on an t2.medium AWS EC2 instance using these instructions. I’m using the blockstack-gaia_hub-ebs-2.5.3-hvm AMI.

I have an elastic IP 54.173.170.105 linked to registered domain www.tcphub.ga.

/etc/environment:

API_KEY=tcphub
DOMAIN=www.tcphub.ga
STAGING=1

docker ps:

CONTAINER ID        IMAGE                                   COMMAND                  CREATED             STATUS              PORTS                    NAMES
bff17d85599f        quay.io/blockstack/gaia-reader:v2.5.3   "node lib/index.js"      30 minutes ago      Up 29 minutes       0.0.0.0:8008->3000/tcp   gaia-reader
85fad1c8bb2f        quay.io/blockstack/gaia-admin:v2.5.3    "docker-entrypoint.s…"   30 minutes ago      Up 29 minutes       0.0.0.0:8009->3000/tcp   gaia-admin
1f4325cd65fd        quay.io/blockstack/gaia-hub:v2.5.3      "docker-entrypoint.s…"   30 minutes ago      Up 29 minutes       0.0.0.0:3000->3000/tcp   gaia-hub

I tried running sudo systemctl restart reset-ssl-certs.service, but it hangs and never returns.

I tried journalctl -xe but get -- No entries --

I looked for logs, but /var/log/nginx did not even exist. I created it and restarted the instance, but still no logs. I get the impression from watching processes that something is hanging in certbot, but without any logs or output I’m not getting any traction troubleshooting the issue.

Any help is much appreciated!

Hello, I am facing a similar issue, where I am not able to get the nginx.service up and running. I’m using t2.micro with the blockstack-gaia_hub-ephemeral-2.5.3-hvm AMI, without the use of EIP. I have enabled journald logging to get visibility of the error messages against the services. Also I have edited the /etc/resolv.conf by including the google public DNS (8.8.8.8) nameserver. From the logs I have confirm that by DOMAIN is pointing to the publiv IPv4 address associated with the gaia-hub instance running on EC2. However, I am observing the nginx service keeps on restarting. On checking the logs, it is throwing the following warnings/error:

Mar 31 12:27:46 ip-172-31-22-198 docker[5962]: 2021/03/31 12:27:46 [warn] 1#1: the “http2_max_field_size” directive is obsolete, use the “large_client_header_buffers” directive instead in /etc/nginx/ngi>
Mar 31 12:27:46 ip-172-31-22-198 docker[5962]: nginx: [warn] the “http2_max_field_size” directive is obsolete, use the “large_client_header_buffers” directive instead in /etc/nginx/nginx.conf:30
Mar 31 12:27:46 ip-172-31-22-198 docker[5962]: 2021/03/31 12:27:46 [warn] 1#1: the “http2_max_header_size” directive is obsolete, use the “large_client_header_buffers” directive instead in /etc/nginx/ng>
Mar 31 12:27:46 ip-172-31-22-198 docker[5962]: nginx: [warn] the “http2_max_header_size” directive is obsolete, use the “large_client_header_buffers” directive instead in /etc/nginx/nginx.conf:31
Mar 31 12:27:46 ip-172-31-22-198 docker[5962]: 2021/03/31 12:27:46 [warn] 1#1: the “http2_max_requests” directive is obsolete, use the “keepalive_requests” directive instead in /etc/nginx/nginx.conf:32
Mar 31 12:27:46 ip-172-31-22-198 docker[5962]: nginx: [warn] the “http2_max_requests” directive is obsolete, use the “keepalive_requests” directive instead in /etc/nginx/nginx.conf:32
Mar 31 12:27:46 ip-172-31-22-198 docker[5962]: 2021/03/31 12:27:46 [emerg] 1#1: unexpected end of file, expecting “;” or “}” in /etc/letsencrypt/options-ssl-nginx.conf:1
Mar 31 12:27:46 ip-172-31-22-198 docker[5962]: nginx: [emerg] unexpected end of file, expecting “;” or “}” in /etc/letsencrypt/options-ssl-nginx.conf:1

I’m guessing this config file is residing inside the nginx container. When I checked this file on the host instance, it was found on the location /gaia/nginx/certbot/conf/options-ssl-nginx.conf with its contents 404: Not Found.

Besides, all 4 gaia services are in active state. I have tried the workaround mentioned in the “Deploy on Amazon EC2 | Stacks” link, still was not able to get the nginx service up.

Any pointers will be much appreaciated.