ERR_SOCKET_NOT_CONNECTED When using Cloudflare

Hi, is anyone else getting ERR_SOCKET_NOT_CONNECTED with Cloudflare, i tried pausing the site and it works (without https).

My website is https://app.symbolsecurity.com
My SSL is set to flexible.

Loads fine for me. How often do you get that error? Can you post a screenshot?

Thanks for checking @sandro!, it’s happening all the time now for us:

I’d first check you actually resolve it to the right IP address and dont have it point anywhere else. Secondly, do you have any proxies configured in your browser? Thirdly, could you try a different browser than Chrome and check if it happens there too?

A quick search did not reveal much (=anything obvious) about that error, except for a pretty usless comment in Google’s forums. I’d expect that to be a local issue though. Do you have that issue with other sites too? Particularly sites behind Cloudflare?

No, only with this site, all other sites i have that use Cloudflare still working good, this one however is hosted in GCP and it was working good until yesterday (no changes to the DNS).

I think it has to be related with my Cloudflare DNS because:

  • If i “Pause” the site in the Cloudflare portal it works
  • if i go directly to the IP it works

Well, that message would indicate an issue between you and Cloudflare. Hence my question if you experience it with other sites too. Do you have by any chance IPv6 on your network enabled?

Do you mean my local network, or servers network? Regarding local network, if i try to reach the site over LTE i got the same result.

I meant local network. If you say you had it via a mobile connection too, we can probably rule out the local network (unless you connected that mobile connection to the local network). My next guess would be a local issue on the computer. You’d need to debug this and try to rule out possible options one by one.

Can you post the outputs of (without blanks)

  • https:// app.symbolsecurity. com/cdn-cgi/trace
    and
  • http:// sitemeer. com/cdn-cgi/trace

https:// app.symbolsecurity. com /cdn-cgi/trace
DNS_PROBE_FINISHED_NXDOMAIN (1st attempt)
ERR_CONNECTION_RESET (2nd attempt)

http://sitemeer.com/cdn-cgi/trace
fl=41f13
h=sitemeer.com
ip=181.48.185.148
ts=1538574345.449
visit_scheme=http
uag=Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36
colo=MDE
spdy=off
http=http/1.1
loc=CO
tls=off
sni=off

Could you try to run dig app.symbolsecurity.com on the command line and post the output?

; <<>> DiG 9.10.6 <<>> app.symbolsecurity.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58583
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1460
;; QUESTION SECTION:
;app.symbolsecurity.com. IN A

;; ANSWER SECTION:
app.symbolsecurity.com. 300 IN A 104.24.122.154
app.symbolsecurity.com. 300 IN A 104.24.123.154

;; Query time: 30 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Wed Oct 03 08:52:15 -05 2018
;; MSG SIZE rcvd: 83

Hmm, it does resolve to the right IP addresses. :thinking:

At this point the only differences are the IPv6 addresses and different edge servers. I’d open a support ticket at their “support” email address and include the information you posted here. Maybe they can dig deeper.

Edit: Another difference is HTTPS but I wouldnt expect that to throw that error :confused:

1 Like

Thanks @sandro Appreciate all the help and guidance you’ve given me here.

Do you mean at [email protected] ? or another one ?

1 Like

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