Bncert-tool issue: domain resolves to a different ip address than the one detected

Keywords: WordPress Multisite - AWS - Technical issue - Secure Connections (SSL/HTTPS)

bnsupport ID: 8b8bdba1-75b2-d4d9-223a-e9ce99b44f9c

bndiagnostic output:

? Apache: Found possible issues
? Connectivity: Found possible issues
? Resources: Found possible issues
https://docs.bitnami.com/bch/apps/moodle/troubleshooting/deny-connections-bots-apache/
https://docs.bitnami.com/general/faq/administration/use-firewall/

bndiagnostic failure reason: The suggested guides are not related with my issue

Description:
Configuring Bitnami HTTPS Configuration Tool.

Executing: /opt/bitnami/bncert-tool
Providing Domain List: thefreephonechat.com www.thefreephonechat.com

It throws following warning:

Warning: The domain ‘thefreephonechat.com’ resolves to a different IP address
than the one detected for this machine, which is ‘184.73.56.38’. Please fix its
DNS entries or remove it. For more info see:
https://docs.bitnami.com/general/faq/configuration/configure-custom-domain/
Press [Enter] to continue:
Both Domain(s) are configured under Route-53, having A-record pointed to 52.44.17.177.
Above-Mentioned Elastic IP is associated with Instance Id hosting Bitnami setup.

Verified over https://www.whatsmydns.net/ for both domains, and they are correctly traced.

Ran, “getent hosts thefreephonechat.com” for both domains on the EC2 instance, and received the following:

52.44.17.177 thefreephonechat.com
52.44.17.177 www.thefreephonechat.com
Further ran “Bitnami Diagnostic Tool” - providing code: a8ce6d0b-c5ef-74c7-739b-604057051318

Please check and suggest what is missing in the setup.

Thanks

Hi @dave.das,

Thank you for using Bitnami and the HTTPS configuration tool. The bncert tool uses myip.bitnami.com to get the public IP of your instance and verify that the domain is pointing to the correct IP address. Could you please confirm 52.44.17.177 is the IP of your instance? You have 2 ways to get this info:

  • From the AWS Console: You can get the IP of the instance using the web interface
  • From the instance’s console: Run this command
curl -L myip.bitnami.com

Please ensure the domain is configured with the correct IP address and then run the tool to generate the certificates.

Happy to help!


Was my answer helpful? Click on :heart:

Hello @jota
Please note over AWS Console, it is configured to be 52.44.17.177.
But using “curl -L myip.bitnami.com”, it is showing as 184.73.56.38.

As per my understanding, it is configured correctly.
Additional information
Domain is from GoDaddy;
It is pointed to AWS’s Name Server(s).
AWS is configured to route “A-record” to IP Address: 52.44.17.177 for “www” and “non-www” domain.
52.44.17.177 is the elastic IP Address, and is associated with correct instance (hosting bitnami).

Please suggest what I might be missing.

Hi @dave.das,

That IP belongs to Amazon

https://www.whatismyip.com/ip-whois-lookup/

Could you please confirm if you can access your application using that IP?

  • If you can access your app using that IP, update your DNS records to point to 184.73.56.38 and then use the Bitnami HTTPS configuration tool to generate the SSL certificates
  • If not, follow the alternative approach in our documentation so you generate the SSL certificates manually using the current configuration of your domain.

https://docs.bitnami.com/aws/how-to/generate-install-lets-encrypt-ssl/#alternative-approach

Happy to help!


Was my answer helpful? Click on :heart:

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.