Website (or cloudflare?) connectivity problem

CF Status page says that there is no problem, but i can’t reach my website through CF.
But the website\server is online and accessible directly (not thru CF).

There is no way to report this problem with free account? :slight_smile:

And, no, there is no CF error page. Just a HTTP request timeout:

:~$ curl -v https://vladsol.tk

  • Trying 195.20.40.47:443…
  • TCP_NODELAY set
  • connect to 195.20.40.47 port 443 failed: Connection timed out
  • Failed to connect to vladsol.tk port 443: Connection timed out
  • Closing connection 0
    curl: (28) Failed to connect to vladsol.tk port 443: Connection timed out
  1. vladsol.tk does not appear to be a registered domain.
  2. Most importantly, your server is not configured for HTTPS. You need to do that with a valid certificate, otherwise your site cannot be secure.

Well, You’re wrong. And, as you see above, it successfully resolved to 195.20.40.47
~$ dig +short -t A vladsol.tk @will.ns.cloudflare.com
172.67.173.217
104.18.34.196
104.18.35.196

Also, there is no problem with SSL.

The registry appears to agree with me :wink:

There obviously is, otherwise you wouldn’t get a timeout.

sitemeer.com/#https://195.20.40.47 cannot connect either.

You need to fix your server.

I can register the domain if you want :wink:

Your response was very charming, I should add :wink:

CF edge certificate is installed. And the website was online until now :slight_smile:
Well, looks like freenom was deleted my domain without any notifications… Wow…

The edge certificate is always there, that is obviously not what I was referring to. You need a certificate on your server.

There we go.

No. Even if I don’t have https enabled on my server, or using a self-signed certificate, I can access that website through CF over HTTPS (in Full or Flexible encryption mode selected in dashboard).

That is exactly what I said before, you site is still insecure in this case.

You need a valid certificate on your server.

In this case, I have encryption between end users and the network, and encryption between the server and the network.
it suits me.
This is not the reason for the timeout, in any case. This is what I’m talking about.

If you don’t have a certificate on your server you do not have any encryption on the connection to your server, hence insecure.

And yes, the timeout is obviously the reason here

connect to 195.20.40.47 port 443 failed: Connection timed out

Again, it does not connect on HTTPS

sitemeer.com/#https://195.20.40.47

Perhaps we did not understand each other.
Freenom did a very ugly thing by not deleting the domain, but replacing the authoritative nameservers.
I thought the IP address 195.20.40.47 belongs to Cloudflare. I thought that this was an entry from the DNS cache, because if the domain was deleted, it simply should not exist :slight_smile:
But, no, 195.20.40.47 is not the Cloudflare address or my server address. My server has a different IP, and as I said, there are no problems with certificates or accessibility via HTTPS.

So you do have a certificate on your server?

Then you just need to clarify this with the registrar and once the domain is back online it should work.

It turned out that I was not the only one who faced a similar problem.

https://gist.github.com/ilyaigpetrov/d7b06b7ea15143124b930f2dde3addfd

I highly discourage anyone from using Freenom.

Yup.

Then you just need to clarify this with the registrar and once the domain is back online it should work.

I don’t think it’s worth dealing with such an “honest” registrar.

This topic was automatically closed after 14 days. New replies are no longer allowed.