Port 80 is close and Port 443 is filtered for firstfruitsfarms.com
$ nmap -Pn -p80,443 firstfruitsfarms.com
Starting Nmap 7.94SVN ( https://nmap.org ) at 2025-01-08 19:31 UTC
Nmap scan report for firstfruitsfarms.com (108.51.233.104)
Host is up (0.087s latency).
rDNS record for 108.51.233.104: pool-108-51-233-104.washdc.fios.verizon.net
PORT STATE SERVICE
80/tcp closed http
443/tcp filtered https
Nmap done: 1 IP address (1 host up) scanned in 2.18 seconds
Port 80 & 443 are open for ccaway.net
$ nmap -Pn -p80,443 ccaway.net
Starting Nmap 7.94SVN ( https://nmap.org ) at 2025-01-08 19:31 UTC
Nmap scan report for ccaway.net (3.33.251.168)
Host is up (0.010s latency).
Other addresses for ccaway.net (not scanned): 15.197.225.128
rDNS record for 3.33.251.168: aec037177372cc6cd.awsglobalaccelerator.com
PORT STATE SERVICE
80/tcp open http
443/tcp open https
Nmap done: 1 IP address (1 host up) scanned in 0.20 seconds
@Bruce5051 ccaway (and the others) use a forwarding service that supports HTTPS but only through frames. They will not be able to get a cert on those. But, HTTPS is already supported by that service.
The poster already said port 80 is not available at "farms" and does not support HTTPS so we wouldn't expect port 443 to work
I assume If have to respond to ssl cert verification requests. How do I do that ie. one response to this post says Godaddy is not compatible with DNS-01 host challenges.
Godday is supposed to be able to generate api key. Haven't tried that yet so don't know what the restriction you mention are.
I assume If have to respond to ssl cert verification requests. How do I do that ie. one response to this posts says Gidaddy is not compatible with DNS-01 host challenges.
They do need certs but already have them. Issued by GoDaddy as part of that service. See for yourself with: SSL Checker
Well, maybe. What service will terminate HTTPS at "farms"? If "farms" was a server, like caddy or nginx, you could setup virtual hosts in those to handle the HTTPS and route to your other services (based on port number presumably). Each of those virtual hosts would need to know about cert.
And, you need to change the URL at the forwarding to be an HTTPS URL. Can that be done? I don't use GoDaddy so can't check but I assume so.
There are better ways to structure this. Are you sure your ISP does not support port 80 inbound to you? (does it use CGNAT for example?) Can you get a fixed IP? It would really simplify things in the long run.
What about port 443. Does your ISP allow inbound on that port?
My isp FIOS does seem to support port 80. I have to figure out how to give my server software permission to use port 80 an 443. I can access a port 80 http server via my public ip 108.51.233.104.
I ran a port 443 server without a cert and I can access it locally but not through internet 108.51.233.104:443 makes sense without cert.
And yes I can set my forwarding to https://firstfruitsfarms.com:4000 or any port. I setup the cert for firstfruitsfarms first and then see what issues are left with respomding to challenges.
Is that also behind your router? Because you may need to map port 443 to that server. A failed Certificate will show as a failed certificate. Currently the request is outright blocked like by a firewall