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.
[Neptune@0rcan0mic conf.d]$ httpd -t -D DUMP_VHOSTS
AH00526: Syntax error on line 18 of /etc/httpd/conf.d/oceanahomes.org-le-ssl.conf:
SSLCertificateFile: file '/etc/letsencrypt/live/www.oceanahomes.org/cert.pem' does not exist or is empty
[Neptune@0rcan0mic conf.d]$ cat oceanahomes.org-le-ssl.conf
Hmm. It is unusual to have the www subdomain point to a different IP than its apex. Can you explain why you do that?
dig +noall +answer www.orcacomputers.com
www.orcacomputers.com. 104 IN A 24.109.185.150
dig +noall +answer orcacomputers.com
orcacomputers.com. 300 IN A 34.102.136.180
Good question. On Godaddy I am setting up subdomains using their control panel to make urls like unifytheminds.thepowerhousemethod.org so Godaddy places the 34.102.136.180
There are a couple problems. The first is you need to fix the DNS for orcacomputers.com and maybe its www. Those IP addresses should point to your server. The IP for www seems correct as an Apache server responds to that domain name. The .180 IP points to some landing page served by openresty.
I'll note the Apache that responds to the www domain is very old. It is version 2.4.6 with PHP version 5. Is this your Apache system?
Let's also look at your Apache config for orca. Please show the contents of these two files. Put 3 backticks before and after the content so we don't lose key info.
Below shows two things. One, that HTTP works to port 443. Also, HTTP to port 80 responds with a redirect but to port 443 shows success. That means the requests are reaching different VirtualHosts in Apache. This may not mean anything to you but it will to other volunteers here.
(this should not work but does)
curl -I http://orcacomputers.com:443
HTTP/1.1 200 OK
Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/5.4.16
(this should work but does not)
curl -I https://orcacomputers.com
curl: (35) error:0A00010B:SSL routines::wrong version number
(this works fine)
curl -I http://orcacomputers.com
HTTP/1.1 301 Moved Permanently
Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/5.4.16
Location: https://orcacomputers.com/
[Neptune@0rcan0mic conf.d]$ curl -I --resolve orcacomputers.com:443:127.0.0.1 https://orcacomputers.com
curl: (35) SSL received a record that exceeded the maximum permissible length.
[Neptune@0rcan0mic conf.d]$ curl -I --resolve thepowerhousemethod.org:443:127.0.0.1 https://thepowerhousemethod.org
curl: (35) SSL received a record that exceeded the maximum permissible length.
That confirms what we see from my curl tests a couple posts back. Basically, your Apache config is not supporting HTTPS
You have been getting certs for a long time and I assume this was working at one time.
What did you change before it went wrong?
One idea from google was to rename your ssl.conf to something like 0-default-ssl.conf. This file has many SSL options in it and possibly needs to be seen by Apache before any other port 443 VirtualHosts. A leading 0 in the name will do that. This seems unlikely but I don't have any other ideas. Your mod_ssl was enabled that was my best guess.
/etc/httpd/conf.d/ssl.conf
You might need to start asking about this on an Apache forum.