Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My web server is (include version):
apache 2.4.6
The operating system my web server runs on is (include version): CentOS7
My hosting provider, if applicable, is:GoDaddy
I can login to a root shell on my machine (yes or no, or I don't know):ye
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):no
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): certbot 1.14.0
Lost what's going on here still trymacnaughton.com, I moved the dns to godaddy renewed teh cert but still not working in browser. Any ideas? Old thread from December 2020
troymacnaughton.com has multiple IP addresses in its DNS records. While they appear to be accessible on the network, we have detected that they produce differing results when sent an ACME HTTP validation request. This may indicate that some of the IP addresses may unintentionally point to different servers, which would cause validation to fail.
[Address=92.205.28.224,Address Type=IPv4,Server=Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/5.4.16 mod_perl/2.0.11 Perl/v5.16.3,HTTP Status=301,Number of Redirects=10,Final HTTP Status=301] vs [Address=184.69.151.38,Address Type=IPv4,Server=Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/5.4.16 mod_perl/2.0.11 Perl/v5.16.3,HTTP Status=301,Number of Redirects=1,Final HTTP Status=404]
Your VirtualHosts are looking good. There are a couple listed below that I question if you really want them active or not. They're defaultish and likely not accessible from the internet (or maybe anywhere).
port 80 namevhost orcacomputers.orcainbox
(/etc/httpd/conf.d/00-default.conf:1)
port 443 namevhost orcacomputers.orcainbox
(/etc/httpd/conf.d/ssl.conf:56)
The actual problem is the extraneous IP address that @Rip astutely observed. It is just an extra A record for troymacnaughton.com in your DNS at GoDaddy that needs to be deleted. You can see it in the dig screenshot below.
I don't think that you want the wrong certificate (and content) to be served for troymacnaughton.com every time the 92.205.28.224 A record is returned to someone's browser though. If you want to use that server as an alternative, you probably want it to have the same configuration (including the certificate) and serve the same content as the primary IP address. If this is intentional, why does www.troymacnaughton.com not have that extra A record?
This is what I see sometimes for troymacnaughton.com:
Were you meaning "intranet" traffic here? Since orcacomputers.orcainbox ends in orcainbox, which isn't a publicly-recognized TLD, rather than orcainbox.com, how do you manage to reach orcacomputers.orcainbox? A hosts file or custom DNS server?
