Error 523 - Origin Unreachable...but?

Blockquote
MAIN /usr/sbin # date
Sun 15 Mar 2020 06:10:52 AM CDT

MAIN /usr/sbin # ping -c5 www.vitamindcouncil.org
PING www.vitamindcouncil.org (104.20.185.18) 56(84) bytes of data.
64 bytes from 104.20.185.18 (104.20.185.18): icmp_seq=1 ttl=59 time=14.4 ms
64 bytes from 104.20.185.18 (104.20.185.18): icmp_seq=2 ttl=59 time=14.7 ms
64 bytes from 104.20.185.18 (104.20.185.18): icmp_seq=3 ttl=59 time=14.1 ms
64 bytes from 104.20.185.18 (104.20.185.18): icmp_seq=4 ttl=59 time=15.2 ms
64 bytes from 104.20.185.18 (104.20.185.18): icmp_seq=5 ttl=59 time=13.8 ms

www.vitamindcouncil.org ping statistics —
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 13.812/14.451/15.163/0.467 ms

MAIN /usr/sbin # traceroute 104.20.185.18
traceroute to 104.20.185.18 (104.20.185.18), 30 hops max, 60 byte packets
1 DPSHome (192.168.1.1) 0.747 ms 0.696 ms 0.767 ms
2 96.120.48.173 (96.120.48.173) 7.144 ms 7.116 ms 7.089 ms
3 po-301-1202-rur02.manitowoc.wi.minn.comcast.net (68.85.169.25) 11.766 ms 11.738 ms 11.710 ms
4 be-6-ar01.roseville.mn.minn.comcast.net (68.87.174.89) 17.778 ms 17.751 ms 17.724 ms
5 69.241.114.158 (69.241.114.158) 27.269 ms 27.242 ms 27.215 ms
6 104.20.185.18 (104.20.185.18) 19.493 ms 16.972 ms 16.765 ms

MAIN /usr/sbin # traceroute www.vitamindcouncil.org
traceroute to www.vitamindcouncil.org (104.20.184.18), 30 hops max, 60 byte packets
1 DPSHome (192.168.1.1) 1.017 ms 1.608 ms 1.576 ms
2 96.120.48.173 (96.120.48.173) 13.534 ms 13.419 ms 13.460 ms
3 po-301-1202-rur02.manitowoc.wi.minn.comcast.net (68.85.169.25) 13.718 ms 13.852 ms 13.750 ms
4 be-6-ar01.roseville.mn.minn.comcast.net (68.87.174.89) 20.334 ms 20.590 ms 19.897 ms
5 69.241.114.158 (69.241.114.158) 29.217 ms 29.069 ms 29.045 ms
6 104.20.184.18 (104.20.184.18) 20.992 ms 19.959 ms 20.188 ms /blockquote

The screenshot (HOPEFULLY?!?) is the result of trying to navigate to a website.
When that failed, with the Error 523 - Origin Unreachable, I tried to ping the website from the command line. THAT was successful. After strolling around the ‘community’ for a minute, I saw recommendations for running traceroute, so I tried it: 1st) the ip4 address ping returned, and 2nd) the ‘www’ address. All of the CLI stuff was successful, but neither Firefox (73.0.1) in the screenshot, nor Chromium (81.0.4044.34 - not shown) on the 2nd monitor, would bring up the web page. Just for kicks, I installed ‘links’ a text based web-browser: it kicked up the same (albeit in monotone text) error! :thinking:

So for some background. A few months ago, I swapped my (relatively) insecure routers for a minicomputer running OPNsense. One of the reasons I went this route was because where, and what, I browse is MY business and I don’t care to have that cached by WHOMEVER has access to my browsing history! I also installed DNSCrypt_Proxy to enable DoH, to keep EVERYBODY out! So here I am today, wondering why my browsers kick up a 523 error??? Or, more specifically, why I can ‘ping’ it from the CLI, but the browser(s) refuse to respond!?! Even more interesting…when I try it from my cellphone (running on the 4G LTE network - NOT on my local internet) I get the same error… That kind of suggests, in my mind, that THIS site has some affinity with CloudFlare and , for whatever reason, isn’t working…

What say you???

(edited for clarity)

You’re pinging the Cloudflare edge server, which is going to repond. But that edge server can’t reach your web server. You’d have to check logs at your server and its firewall. It’s even possible your server’s IP address has changed.

1 Like

sdayman: “You’re pinging the Cloudflare edge server, which is going to repond. But that edge server can’t reach your web server. You’d have to check logs at your server and its firewall. It’s even possible your server’s IP address has changed.”

I’m not quite sure what you’re saying: “You’re pinging the Cloudflare edge server…”
It’s not MY web page, just a page I was trying to visit.
However, on further research, it appears that that page is defunct.

But I appreciate the response!

1 Like