Hi, I'm getting 521 errors on proxied DNS. Proxied resource (B2 bucket) is available, SSL mode is Fu
Hi, I'm getting 521 errors on proxied DNS. Proxied resource (B2 bucket) is available, SSL mode is Full. Any ideas what I can troubleshoot more?
Rserver is not down, I can fetch results from it. I also don't get 521 responses for requests running from github actions for some reason.
RI see there's maint going on but nothing that should affect proxied requests
ACan someone please help me with this general-helpHelp: Cloudflare Images
HUno Reverse: mining crypto on a Lava Lamp
Pdisable the Cloudflare proxy for your DNS record temporarily, wait 5 minutes, and then try to load the page again
Pif it still doesn't load, then it's definitely your webserver
RStill 521. If it's not being proxied, how can it give me a 521?
ICan you give the domain? I suspect it's DNS cache and you're still hitting the proxied version.
RUrl through cloudflare (now unproxied) is http://zotero.retorque.re/file/apt-package-archive/./InRelease
RThe server behind it is https://f001.backblazeb2.com/file/apt-package-archive/./InRelease
IOK so the proxy either hasn't been turned off properly (do you see a grey cloud) or it's just taking a bit to turn off.
II'm still getting a Cloudflare IP returned for that domain.
RGrey cloud, correct
1DNS over Discord: A records
zotero.retorque.re A @1.1.1.1 +noall +answerdiggy diggy hole
•3/19/25, 2:58 PM
RI'm getting the 521 from 2 distinct networks. Each have entirely different dns hosts (home vs work)
IYeah, I don't think it's cache at this point but it's just not unproxying for some reason.
Cwhat does that record look like in the dashboard (screenshot?)
RUnproxied now does work
IYeah looks like it's pointing to backblaze directly now.
IWhat is your SSL mode set to on the dash?
RBut I have a new record set up proxied and that also works
RSsl is at Full
IGood, that's correct then.
Cif new proxied works, but old proxied doesn't, run your original hostname through trace then and see what you hit. Could be origin rule override, worker, etc (Rules -> Trace)
RI've reenabked proxy for the zotero url and there's now a warning triangle to the left "this record exposed the IP address used in the CNAME record on qkjb" (the proxied url that does work)
RAnd that's now gone...
Cit's nothing more then trying to warn you about security
Cif you have an unproxied record and proxied record to the same thing, it's saying "hey you're exposing it anyway"
RAnd now the zotero url works, proxied.
Cthis
http://zotero.retorque.re/file/apt-package-archive/InRelease one?RYes
CI still see
Ceh might just take a second though, if it works for you
RWell that's strange then. Works from my two networks now. Has continued to work from github actions.
DI had the same issue. So I created .npmrc file in the root directory of my project and added this single line of text to it:
Then after pushing this change to the main branch, Cloudflare build worked like cream.
Then after pushing this change to the main branch, Cloudflare build worked like cream.
Ehlo everyone, cloudflare is new for me like i have a website nd i want to do it live can someone guide me wht steps have to follow to do it live
A
Eiam trying to launch a website iam getting this error can any one please help me
EIam using Cloudflare for domain
Eplease help me
CThe AAAA record is not valid, there's also the issue of is your server allows you using CF SSL to initate proxy.
CEither way it's wrong, you need to help yourself at this point lack of understand is a vulnerability.
C
CWeird individual....
Cnothing diff t han some of the emails I get with support.
CLol yeah entitlement, it's sad to see.
CI provide a service for 10K+ users and I see that treatment often, mental health ain't on deck these days for some.... :X
CJust sad mentality, folks with sites hosting millions of users and this guy think he more important. :X
CI saw but that's sad.
