jatkin
CDCloudflare Developers
•Created by jatkin on 10/11/2024 in #general-help
"Sorry, you have been blocked," and lots of requests from different countries
Hi CF discord,
My team member just visited our landing page and received a "Sorry, you have been blocked" error page from Cloudflare.
Both me and my other team member tried visiting the site and got the same error page.
It went away after 2-3 minutes, but I wanted to know if this indicates something wrong with my site configuration.
I took a look at the Analytics & Logs page and am seeing 50k requests in the last 7 days... we are definitely not expecting high traffic.
Is this a normal amount of traffic from bots/crawlers? Or is my site under attack?
Thanks everyone!
2 replies
CDCloudflare Developers
•Created by jatkin on 10/7/2024 in #general-help
Help with Cloudflare for SaaS - customer onboarding flow and SSL issues
Hi Cloudflare Developers,
I'm getting started using Cloudflare for SaaS.
I want to let customers use their own domains for static sites I'm hosting for them using R2 + Workers.
Was looking for some guidance on setting this up, and what the flow will look like for my customers.
A brief outline of my use case:
- Our product lets users build custom landing pages.
- Their pages are exported as HTML + JS and uploaded to R2, prefixed by their user ID.
- Each user has an entry in a Workers KV namespace mapping their chosen subdomain to their user ID.
- A Workers script checks the Host header of the incoming request and retrieves the user ID from the mapping, then serves content from that prefix in R2.
- As for DNS in this setup, there's only a single wildcard CNAME record pointing to the root domain, and the root domain has an A record pointing at CF's test/empty address (192.0.2.0)
So now onto CF for SaaS...
Here's the flow I'm envisioning:
1. User fills out form with their custom domain
2. Backend makes request with Cloudflare SDK to add a new custom domain
3. Frontend retrieves DNS records and shows user which records they need to add.
I was thinking that the user would add two records, a CNAME and an A record:
- CNAME record pointing their custom domain to their already-configured subdomain going through the routing logic described above:
Example: CNAME www.myvanitydomain.com -> customer1.mysaasapp.com
- A record pointing to a simple web server I will spin up redirecting non-www requests to www subdomain.
Additionally adding the verification records provided by CF.
I tested this flow with one of my domains, and I'm getting this error in Chrome: ERR_SSL_VERSION_OR_CIPHER_MISMATCH.
This was after adding Cloudflare's verification TXT records and adding my test domain as a custom domain.
Lastly:
I want to make this process as simple as possible for my end users.
Will they need to add the verification TXT records, or can they only add a CNAME and A record?
Thanks!
28 replies