Elliot Hesp
CDCloudflare Developers
•Created by Elliot Hesp on 9/25/2024 in #general-help
Custom Hostnames (CF for SaaS) - some domains 522
Hi All,
We have custom hostnames enabled for a zone (docs.page), and have added a number of custom hostnames to test.
All hostnames are verified (green certificate status + hostname status). These hostnames are supposed to connect to a cloudflare worker, which is routed via the DNS record (this is setup).
The problem:
Some of these hostnames work (they hit the worker as expected), and some of them don't. Those that don't, have a 522 error, and there are no logs on the worker - it looks like an CF internal issue.
We've used a bunch of domains (both within cloudflare dns and outside):
Broken:
- https://test-docs.tangents.tech/ (Namecheap DNS)
- https://test.docs.page/ (Clouldflare DNS, same zone)
+ https://docs-test.giteye.io/ (Cloudflare DNS, same account)
Working:
- https://docs-test.elliothesp.co.uk/ (Cloudflare DNS, different account) - https://test-docs.unverified.lol/ (Cloudflare DNS, different account) We're totally stumped as to why this is happening - how do we go about debugging and resolving? Looks like those in the same account/zone are broken, but this shouldn't be the case...?
- https://docs-test.elliothesp.co.uk/ (Cloudflare DNS, different account) - https://test-docs.unverified.lol/ (Cloudflare DNS, different account) We're totally stumped as to why this is happening - how do we go about debugging and resolving? Looks like those in the same account/zone are broken, but this shouldn't be the case...?
5 replies
CDCloudflare Developers
•Created by Elliot Hesp on 3/26/2024 in #workers-help
Cache API - randomly started working
Hey all,
We've had a worker running for months, which gets a fair amount of traffic. We had some logic in place using the Cache API to help speed up some requests. Behind the scenes we're using D1, so the Cache layer was put in to speed up slow requests.
We never saw the cache being hit, it always missed.
One day we started to get a load of errors coming through, which was due to bad caching logic on our part (storing the wrong data in the
Response which was cached). Looking at our logs, we saw that many requests were now being cached as expected initially. This started to happen:
2024-03-04 23:02:03.305
There had been no changes on our end - worker deployments, settings etc. We've now fixed the bad logic and redeployed, the cache is now working as we'd expect.
Is there any reason or someone which could do some investigation for us as to why the Cache API randomly started to work again? It's a little disconcerting for us.
Thanks!1 replies
CDCloudflare Developers
•Created by Elliot Hesp on 7/24/2023 in #pages-help
Pages Logpush not syncing
Hello,
I've got Logpush setup on my account, and my workers are currently syncing fine. However my Pages deployment is not syncing logs. I don't see anything UI specific in my pages deployment on the dashboard - how do I get these working?
11 replies