Error establishing secure connection

bug

#1

Hello! It is strange why the site works? If in the browser address bar enter the address site.com it gives an error:
Error establishing secure connection
While loading page the connection to site.com was interrupted.
The page you are trying to view cannot be displayed because the validity of the data received cannot be verified.
Please contact the website owners and inform them about this problem.

And if you specify www.site.com that site opens and after works and site.com I www.site.com

What could be the reason? Thanks in advance for your help!


#2

Loads fine for me :wink:

Now, if you could post the actual domain.


#3

#4

Works for me in either case. Can you post the output of these commands?

ping golo.pro
nslookup golo.pro
ping www.golo.pro
nslookupwww.golo.pro

#5

All right! I checked… everything works except the region of the Russian Federation. There are many complaints from this region. There might be a problem with ip addresses in the region.


#6

I found a website in Russia that shows all blocked ip in Russia: https://eais.rkn.gov.ru! Website https://golo.pro located on ip 104.27.144.135. This ip is blocked in Russia. But then why so strange the site works on the territory of the Russian Federation? If it is blocked, it should not be visible at all on the territory of the Russian Federation. And it turns out that it does not work only in this form https://golo.pro… but it works https://www.golo.pro and if you disable https: / / then in this golo.pro / www.golo.pro ahhh! Why does everything work so strangely?


#7

Again, run the mentioned commands on the machines where you cant access your site and post their output. Once we have established you reach the right server we can continue.


#8

ping golo.pro
PING golo.pro (104.27.144.135) 56(84) bytes of data.
64 bytes from 104.27.144.135: icmp_seq=1 ttl=56 time=23.9 ms
64 bytes from 104.27.144.135: icmp_seq=2 ttl=56 time=23.8 ms
64 bytes from 104.27.144.135: icmp_seq=3 ttl=56 time=23.9 ms
64 bytes from 104.27.144.135: icmp_seq=4 ttl=56 time=24.2 ms

nslookup golo.pro
Server: 127.0.0.53
Address: 127.0.0.53#53

Non-authoritative answer:
Name: golo.pro
Address: 104.27.145.135
Name: golo.pro
Address: 104.27.144.135
Name: golo.pro
Address: 2606:4700:30::681b:9087
Name: golo.pro
Address: 2606:4700:30::681b:9187

ping www.golo.pro
PING www.golo.pro (104.27.145.135) 56(84) bytes of data.
64 bytes from 104.27.145.135: icmp_seq=1 ttl=56 time=24.2 ms
64 bytes from 104.27.145.135: icmp_seq=2 ttl=56 time=24.5 ms
64 bytes from 104.27.145.135: icmp_seq=3 ttl=56 time=24.5 ms
64 bytes from 104.27.145.135: icmp_seq=4 ttl=56 time=24.5 ms

nslookup www.golo.pro
Server: 127.0.0.53
Address: 127.0.0.53#53

Non-authoritative answer:
Name: www.golo.pro
Address: 104.27.144.135
Name: www.golo.pro
Address: 104.27.145.135
Name: www.golo.pro
Address: 2606:4700:30::681b:9187
Name: www.golo.pro
Address: 2606:4700:30::681b:9087


#9

All right, you resolve the right addresses. What is the output of the following two URLs?

http://golo.pro/cdn-cgi/trace
https://golo.pro/cdn-cgi/trace (this one presumably will fail to load)

#10

fl=98f28
h=golo.pro
ip=209.95.56.51
ts=1548744519.166
visit_scheme=http
uag=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36
colo=DEN
http=http/1.1
loc=US
tls=off
sni=off

fl=98f22
h=golo.pro
ip=209.95.56.51
ts=1548744544.644
visit_scheme=https
uag=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36
colo=DEN
http=h2
loc=US
tls=TLSv1.3
sni=plaintext


#11

So you can reach the site too, both over HTTP and HTTPS. But you get an error when you go to https://golo.pro? Considering you can access it via HTTPS, that really shouldnt happen.


#12

If you try using proxies with Russian servers:

https://golo.pro/cdn-cgi/trace that issues - ERR_CONNECTION_CLOSED

#13

Well, I obviously meant you should post the output when opening it from these locations. I mentioned this earlier and all of the debugging might have been useless at this point.

Did you run the earlier commands from these locations?


#14

ping golo.pro
PING golo.pro (104.27.144.135) 56(84) bytes of data.
64 bytes from 104.27.144.135: icmp_seq=1 ttl=56 time=23.7 ms
64 bytes from 104.27.144.135: icmp_seq=2 ttl=56 time=24.3 ms
64 bytes from 104.27.144.135: icmp_seq=3 ttl=56 time=23.6 ms
64 bytes from 104.27.144.135: icmp_seq=4 ttl=56 time=24.3 ms
64 bytes from 104.27.144.135: icmp_seq=5 ttl=56 time=23.8 ms
64 bytes from 104.27.144.135: icmp_seq=6 ttl=56 time=23.7 ms
64 bytes from 104.27.144.135: icmp_seq=7 ttl=56 time=24.2 ms

nslookup golo.pro
Server: 127.0.0.53
Address: 127.0.0.53#53

Non-authoritative answer:
Name: golo.pro
Address: 104.27.145.135
Name: golo.pro
Address: 104.27.144.135
Name: golo.pro
Address: 2606:4700:30::681b:9087
Name: golo.pro
Address: 2606:4700:30::681b:9187

ping www.golo.pro
PING www.golo.pro (104.27.144.135) 56(84) bytes of data.
64 bytes from 104.27.144.135: icmp_seq=1 ttl=56 time=23.7 ms
64 bytes from 104.27.144.135: icmp_seq=2 ttl=56 time=24.1 ms
64 bytes from 104.27.144.135: icmp_seq=3 ttl=56 time=24.4 ms
64 bytes from 104.27.144.135: icmp_seq=4 ttl=56 time=23.8 ms
64 bytes from 104.27.144.135: icmp_seq=5 ttl=56 time=24.5 ms
64 bytes from 104.27.144.135: icmp_seq=6 ttl=56 time=23.7 ms
64 bytes from 104.27.144.135: icmp_seq=7 ttl=56 time=24.5 ms

nslookup www.golo.pro
Server: 127.0.0.53
Address: 127.0.0.53#53

Non-authoritative answer:
Name: www.golo.pro
Address: 104.27.145.135
Name: www.golo.pro
Address: 104.27.144.135
Name: www.golo.pro
Address: 2606:4700:30::681b:9187
Name: www.golo.pro
Address: 2606:4700:30::681b:9087

fl=87f10
h=golo.pro
ip=80.83.239.112
ts=1548746090.749
visit_scheme=http
uag=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36
colo=DME
http=http/1.1
loc=RU
tls=off
sni=off

https://golo.pro/cdn-cgi/trace: Unable to access site ERR_CONNECTION_CLOSED

#15

That does seem as if someone on the line interrupts that connection. I believe there have been reports of some interference of some Russian ISPs, but nothing properly confirmed so far. That might be yet another case.

Is this the only site where you encounter issues or do other Cloudflare-backed sites not load on HTTPS either?


#16

I have one! But in the vastness of Russia, many forums and discussions of similar situations


#17

There is probably nothing you can do, except for complaining to that ISP and switching to another one, unless that IP is generally blocked for HTTPS (European governments love to censor sites), in which case changing ISP probably will not help either.


closed #18

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