I just checked, I have an unpaid invoice
I just checked, I have an unpaid invoice
CIf you open it, should be a
Pay onlineIN-CFUSA-
Wthe 100 can be lifted
Wbut no, no Pages for Platforms coming soon - with convergence you'll be able to use static assets in WfP but no timeline on that
Wwfp = workers for platforms
Was for limit increase - there's a limit increase form on the docs: https://developers.cloudflare.com/pages/platform/limits
Wwhat's your account ID?
Waccount ids aren't private, you can send here
Wthanks, i'll have someone check
Wlimit has been lifted
Wsup?
Wthis was escalated internally already
BHi, what is a custom domain? If I have foo.example.com and bar.example.com, is that one custom domain or two?
CThat is 2. It is any domain you want to serve your project from
BRight, but that is one domain and two subdomains
CYou are serving your site from two separate sources
WSpecific naming aside, they're called 2 custom domains.
It'd be confusing to have "custom domain" and " custom subdomain"
It'd be confusing to have "custom domain" and " custom subdomain"
WAlso abc.example.com can be a "domain" in CF terms (since it can have its own zone)
WBasically, naming is hard and terminology doesn't mix always well with products
DHello all. I'm deploying with wrangler, and get no error messages (additionally the site works locally when served by wrangler). But on the cloudflare dashboard it keeps reporting that the deployment has failed. Where can I get more information on why?
WUpdate to the latest wrangler
WThe bug of not seeing the error message is fixed there
DDang, didn't even think of that. Thanks, will try.
DWoah, updating wrangler straight up fixed the deploy. I appreciate your help.
Bis it the case that preview deployments don't count as an additional subdomain?
BI'm building a thing where that will be hosting customer websites using cloudflare pages. For example, my website is kelly.com and using cloudflare pages the URL for a customer's pages website might be customer.pages.dev.
To set up a custom domain, a customer might set up a CNAME from example.customer.com to customer.pages.dev. This is ok although I don't want customers to need to use customer.pages.dev, I'd rather they have customer.kelly.com.
My current plan to resolve this is to add a custom domain to the pages project, customer.kelly.com, and tell the customer to use customer.kelly.com, so it would be example.customer.com -> customer.kelly.com -> customer.pages.dev.
Is there any issue with this approach? I want to try it out and am getting
To set up a custom domain, a customer might set up a CNAME from example.customer.com to customer.pages.dev. This is ok although I don't want customers to need to use customer.pages.dev, I'd rather they have customer.kelly.com.
My current plan to resolve this is to add a custom domain to the pages project, customer.kelly.com, and tell the customer to use customer.kelly.com, so it would be example.customer.com -> customer.kelly.com -> customer.pages.dev.
Is there any issue with this approach? I want to try it out and am getting
CNAME Cross-User Banned when I load the domain the customer uses.CIs there any issue with this approach? I want to try it out and am getting CNAME Cross-User Banned when I load the domain the customer uses.CF Pages uses CF for SaaS under the hood, which basically has an allowlist of all the accepted host headers/subdomains allowed to use it. It's seeing
example.customer.com and saying "hey that's not on our list", and it would only allow it as a Verified Custom Domain if it was pointing directYour options basically are:
- Use CF Pages Custom Domains up to the limit: https://developers.cloudflare.com/pages/platform/limits/ (depending on plan), have customers cname to pages.dev
- Use Cf for SaaS, but in order to do that you'd need to have a Worker in the middle and pay for each request as an invocation. Snippets (Workers with more limits, limited to Pro, but no per request costs) may help with this but they're in Alpha/not recommended for production and still rolling out
B@Chaika Thanks. I just tested adding example.customer.com as another custom domain, so now I have two: example.customer.com and customer.kelly.com. Based on your reply I think this would not work, but there is no longer the error and it's working. Does that make sense?
CMakes sense in the way that Cf for SaaS validation is quirky lol, must be from the http validation? Eitherway if you go that way you'd hit the 100 Custom Domain Limit (on free) at some point and have to go someway else, and you won't be able to support root domains (customer.com)
Bwhy would I hit the 100 custom domain limit? The 100 custom domain is per website, and this is 2 domains per website.
Cno, it's per Pages Project
C
Byes, each customer gets their own project
Cthen you'll have to get the soft 100 project limit raised if you haven't already
Bsure, I can do that once I get to 100 projects, good problem to have!
