i ran "wrangler secret put API_KEY" and put a new api key. But the logs are still showing the old ap
i ran "wrangler secret put API_KEY" and put a new api key. But the logs are still showing the old api key. any ideas as to why?
Cif you're using Pages Functions, have to do in the dashboard: https://developers.cloudflare.com/pages/functions/bindings/#secrets
What you did is add it to some worker, probably the one you were mentioning trying before
What you did is add it to some worker, probably the one you were mentioning trying before
Cloudflare Docs
A binding enables your Pages Functions to interact with resources on the Cloudflare developer platform. Use bindings to integrate your Pages Functions …
CWrangler is very much workers first, although functions share the same resources (like kv buckets, r2 namespaces, etc)
CF is eventually hoping to converge both pages and workers into one product, a while off though
CF is eventually hoping to converge both pages and workers into one product, a while off though
Aah, that makes sense. they should have a doc page that shows the differences between workers and Pages Functions. Thanks for the help!
![Aiden [Switched to @aidendotgg]](https://cdn.discordapp.com/avatars/385642786013184000/32516402765184bffcf1ff4bf3efe0ba.webp?size=40)
AChallenge pages are not working for anyone atm
AOne of the requests are being 401'd and its completely breaking the challenge
Cit seems set now, did escalate though, hopefully a retro status page
![Aiden [Switched to @aidendotgg]](https://cdn.discordapp.com/avatars/385642786013184000/32516402765184bffcf1ff4bf3efe0ba.webp?size=16)
Cthat 401 is fine though
Calways going to get one from pat
Cthe issue was the script itself was being 403'd
C?PAT-401
FSeeing a 401 error in your console during a Turnstile security check?
You can safely ignore the error, it's requesting a PAT but your device/browser does not support PATs yet, so you see the error.
Learn more: https://blog.cloudflare.com/eliminating-captchas-on-iphones-and-macs-using-new-standard/
You can safely ignore the error, it's requesting a PAT but your device/browser does not support PATs yet, so you see the error.
Learn more: https://blog.cloudflare.com/eliminating-captchas-on-iphones-and-macs-using-new-standard/
AHmmm
Ayeah idk it was fully broken for a good like 10 minutes
Cit was broken for a few mins for sure, we escalated it and they made a retroactive incident, hopefully will get a retro status page as well. There was more talk in 🤖turnstile
IThere is now a retroactive status page 
I#cloudflare-status
KWhat Happened in Oceania?
KDid they got the upgrade first and then was scared about that spike or what happened?
4can someone answer #Access "Grafana" Icon? the thread has been covered by new posts and i cant find anything online
ACan someone please guide me how to change the nameservers of my domain on cloudflare to point to my hosting server from siteground?
HGet the IP of your Siteground server, then create an A record.
you can copy it from the Site Information → Website IP.
Cyour preferred ones don't change but there is no guarantee they will always be used
Cin case of conflict, they'll pick random ones. Also recently if you preset them at your registrar and then add the domain after, it'll pick two different ones (domain hijacking thing)
Chttps://developers.cloudflare.com/dns/zone-setups/reference/nameserver-assignment/
To prevent domain hijacking, you can no longer preset Cloudflare nameservers at your registrar before creating the respective zone in Cloudflare. If you preset your nameservers and then add the domain, your domain will be assigned a new pair of nameservers.
SVerifying you are human. This may take a few seconds.
SI have no vpn on
I?turnstile-issues Try the steps below.
FIf you're having trouble passing Cloudflare Turnstile challenges, you can try taking the following steps:
- Check your browser and use a different one if necessary. Cloudflare Turnstile supports the latest versions of popular browsers but some forks (such as Pale Moon) are not supported. See this link for more info: https://developers.cloudflare.com/fundamentals/get-started/concepts/cloudflare-challenges/#supported-browsers
- Disable your browser extensions. Sometimes browser extensions can cause Turnstile to block your browser.
- Scan your computer for malware (for example, using a free tool such as Malwarebytes). Sometimes malware can cause Cloudflare Turnstile to detect your computer as malicious and block it.
BHello
DI'm going to assume no, but is there any sort of way to integrate access with a third part controlled server, specifically for your own account? If not, legacy SSH keying will suffice, but just curious.
Edit: specifically referring to short lived certificates only. I know I can make a hostname and route through my tunnel to a public host, but I'm more curious about authentication being done.
Edit: specifically referring to short lived certificates only. I know I can make a hostname and route through my tunnel to a public host, but I'm more curious about authentication being done.
Ahi
Jhi,everyone , i use
Ji use cloudflare images,and i get some trouble on it:https://api.cloudflare.com/client/v4
/accounts/{account_id}/images/v2?page=1&per_page=10，i get the same image list，when page=1 and page=2
/accounts/{account_id}/images/v2?page=1&per_page=10，i get the same image list，when page=1 and page=2
AI have a cloudflare pages function that does a fetch of an external API using fetch.
fetch('https://www.alphavantage.co/query?function=TIME_SERIES_DAILY&symbol=VOO&apikey=XXX')
but it returns an error. When I do curl fo the same URL it works.
Do of the same URL it works.
curl 'https://www.alphavantage.co/query?function=TIME_SERIES_DAILY&symbol=VOO&apikey=XXX'
XXX is not my api key.
How does a fetch() differ from a curl?
fetch('https://www.alphavantage.co/query?function=TIME_SERIES_DAILY&symbol=VOO&apikey=XXX')
but it returns an error. When I do curl fo the same URL it works.
Do of the same URL it works.
curl 'https://www.alphavantage.co/query?function=TIME_SERIES_DAILY&symbol=VOO&apikey=XXX'
XXX is not my api key.
How does a fetch() differ from a curl?
ATried this too, but same thing
const apiResponse = await fetch(cacheKey, {
method: 'GET',
headers: {
'Accept': 'application/json'
}
});
const apiResponse = await fetch(cacheKey, {
method: 'GET',
headers: {
'Accept': 'application/json'
}
});
Pit returns an errorwhat is the error?
ASays too many api calls. Returned in the json
AThey have a limit of 25 per day. But the curl works. So I’m under the limit
ADoes cf cache requests? Maybe it’s a cached response from a previous day
AI’ve tried a fresh api key too. Same response
CMy guess is they might have some IP rate limiting as well. The IP that would be used when making the request from pages would be shared with other users.
HIsn’t that referring to the fact that the URL you request is /something.html
HWhich sends you a preload for /image.png
