Hello, what is elol.com error;
2020/01/26 10:16:35 http: TLS handshake error from 126.96.36.199:31365: no certificate available for ‘elol.com’
2020/01/26 10:26:39 http: TLS handshake error from 188.8.131.52:54610: no certificate available for ‘elol.com’
2020/01/26 10:32:11 http: TLS handshake error from 184.108.40.206:51008: no certificate available for ‘elol.com’
2020/01/26 10:38:28 http: TLS handshake error from 220.127.116.11:36486: no certificate available for ‘elol.com’
2020/01/26 10:39:07 http: TLS handshake error from 18.104.22.168:36604: no certificate available for ‘elol.com’
2020/01/26 10:41:26 http: TLS handshake error from 22.214.171.124:52311: no certificate available for ‘elol.com’
It means Caddy received
elol.com in the SNI extension in the request delivered to it. It isn’t serving a website with that name, yet the request was delivered to it. This means
elol.com points at the IP address of your server via DNS record (assuming usage and not especially crafted request). I assume the IP address is shared, a result of DNS cache, or client cache of old DNS result.
This might be related to this issue: V2: Automatic https certificate errors
Because on his website elol.com I receive the same error as on mine.
@HNRK I don’t think so, because in his other threads, he wasn’t trying to configure that domain. See Caddy Windows streaming server - #14 by matrixebiz
In such a case, you can check if the certificate is issued by crt.sh:
It seems that
elol.com certificate has not been issued yet.
Then I looked at WHOIS:
Domain Name: ELOL.COM
Updated Date: 2019-04-08T09:43:13Z
The settings do not seem to have changed. Is the IP address of the server you are operating the same as before?
Otherwise, you have forgotten to set up a name server to build this server.
In order for Let’s Encrypt to issue a certificate, it must be sure that it has reached Caddy when referencing the domain.
If there is no change in the operation server, restart Caddy and check the log immediately after that. Caddy should have gotten some error in issuing the Let’s Encrypt certificate and logging it.
Ahh I see, you are right! Thanks!
Hello, I don’t know what that message is for, does it look like someone is trying to hack my server from those IP’s?
It’s nothing that serious. I think you just inherited the IP address that someone else used to use, and that domain still points to your IP address. I don’t think it’s anything to be concerned about, ultimately. There’s a lack of IPv4 addresses, so this sort of thing is bound to happen.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.