We’ve purchased a domain from AWS Route 53, got a valid SSL certificate for the domain and registered it in Certificate Manager. We also have an ALB deployed and a domain that resolves to the ELB endpoint.
We are trying to deploy a Blockstack Gaia instance with the image: blockstack-gaia_hub-ephemeral-2.5.3-hvm - ami-03e024fda2bc257d9
behind the Application Load Balancer so we can offload the SSL Certificate to the balancer. However, the instance never “resolves” our domain correctly, it always tries to resolve to either the private or public instance IP. We’ve tried several times, even just a single instance with an Elastic IP and we get the same result.
Is there some way to configure Gaia so that we can deploy behind a load balancer?
Here is the error message from journalctl -xe
:
Feb 18 14:36:38 ip-172-31-35-111 bash[1578]: [ datahub.tcpdev.org ] Record (107.23.30.20
Feb 18 14:36:38 ip-172-31-35-111 bash[1578]: 3.216.65.218
Feb 18 14:36:38 ip-172-31-35-111 bash[1578]: 34.225.213.203
Feb 18 14:36:38 ip-172-31-35-111 bash[1578]: 34.231.187.112
Feb 18 14:36:38 ip-172-31-35-111 bash[1578]: 35.171.128.86
Feb 18 14:36:38 ip-172-31-35-111 bash[1578]: 54.156.194.52) doesnt match public IP (54.92.190.45) - sleeping for 70s....
Feb 18 14:36:45 ip-172-31-35-111 systemd[1]: Condition check resulted in LetsEncrypt Init Service being skipped.