let’s encrypt props.
Despite the port opening of let’s encryt server firewalls or equipment, I found out why the dusky content of Timeout rolling connection “likely firewall problem” appears.
The problem was ddns.
For domain sites, it does not actually handle all of the tasks because only re-directions proceed. For this part, it is handed over directly to the ddns. ddns become a problem.
We can’t actually hand over the proper information in ddns to let’s encrypt.
Because the IP is not fixed like a domain site, and it generates ddns, it is considered blocked by the firewall of the site that supports the actual ddns.
No matter how much I try to send it to my equipment, I think it’s too much because it won’t actually open.
Allowing for all ports and allowing for all IPs.
It’s too much because there’s no real communication.
First of all, I’ll test it again. I don’t look optimistic.
=====================================================================
–Correction–
//before the test.
I think it will go well if we assign a certificate to the server.
In the direction of not riding the ddns?