If there's any "dynamic" component to this running on servers (not just
a non-Racket-based HTTP server serving static files, and the dynamic
happening purely in client-side JS), then I'd check the logs related to
that (process logging, any logging related to the connection between the
machine on which that runs and the frontend server/proxy runs, etc.).
Guessing something in there is more likely to break than Cloudflare
itself or Cloudflare's connectivity with these various people.
If you know how to use Wireshark/tshark/tcpdump, and a bit about TCP
states, (or want to learn) it doesn't hurt to watch that when you
reproduce your connection being rejected. It's easier to debug if you
use an HTTP request rather than HTTPS.
Also would help if you knew which ISPs people having trouble are using
(perhaps broken routes, or broken transparent proxying).
(FWIW, I could fetch this URL fine, from both my EC2 proxy and through
at least one Tor US exit node, the latter of which is usually more
likely to be blocked because it's an exit node or because of abuse. EC2
addresses/blocks sometimes blocked for abuse, as well, though not as
much as Tor exits.)
--
You received this message because you are subscribed to the Google Groups "Racket
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/racket-dev/410d4cb6-2950-e28b-4cd7-efd584171c00%40neilvandyke.org.
For more options, visit https://groups.google.com/d/optout.
