Happy to see that it works.
I don't know. Because my tool sees only a blocking firewall ( https://check-your-website.server-daten.de/?q=ggc.world ):
Domainname | Http-Status | redirect | Sec. | G |
---|---|---|---|---|
• http://ggc.world/ | ||||
37.116.210.18 | -2 | 1.097 | V | |
ConnectFailure - Unable to connect to the remote server No connection could be made because the target machine actively refused it 37.116.210.18:80 | ||||
• http://www.ggc.world/ | ||||
37.116.210.18 | -2 | 1.097 | V | |
ConnectFailure - Unable to connect to the remote server No connection could be made because the target machine actively refused it 37.116.210.18:80 | ||||
• https://ggc.world/ | ||||
37.116.210.18 | -2 | 1.097 | V | |
ConnectFailure - Unable to connect to the remote server No connection could be made because the target machine actively refused it 37.116.210.18:443 | ||||
• https://www.ggc.world/ | ||||
37.116.210.18 | -2 | 1.180 | V | |
ConnectFailure - Unable to connect to the remote server No connection could be made because the target machine actively refused it 37.116.210.18:443 | ||||
Perhaps you should fix that, so you can use http-01 validation, so you don't need --manual
.
/.well-known/acme-challenge/unknown-file has the same blocking answer, but that must answer if you want to use http-01 validation.