You can do it in reverse, and have a Worker that proxies to Pages?
You can do it in reverse, and have a Worker that proxies to Pages?
TThat is where I am at today with it, not a big fan of needing a worker (to use workers routes) to proxy the Pages app, but it is techincally possible.
HOr, if you are on an enterprise plan, then you should be able to use Origin Rules
HWhich would make it not bill per-request
HOr Snippets, as mentioned, if you can get access
TThank you! Ok I'll follow up with our CF contacts, we currently have an enterprise plan. Not too familiar with Origin Rules or the new Snippets feature but I'll look into it.
EHighly recommend contacting your account team, they should be able to point you in the right direction and should be able to get you ahead of the queue for Snippets access
AHey, Folks
We have our Next.js site hosted on Vercel but we're moving to Cloudflare Pages because of their weird restriction of max 1024 pages even in the paid plan, if you exceed it you need to upgrade to the Enterprise plan.
Anyways, right our domain has an A record pointing to Vercel's IP address, and CFP use CNAME to point the domain to the cloudflare pages app domain.
Any Tips or suggestions on what should I do to make sure there's no downtime b/w DNS propagation.
We have our Next.js site hosted on Vercel but we're moving to Cloudflare Pages because of their weird restriction of max 1024 pages even in the paid plan, if you exceed it you need to upgrade to the Enterprise plan.
Anyways, right our domain has an A record pointing to Vercel's IP address, and CFP use CNAME to point the domain to the cloudflare pages app domain.
Any Tips or suggestions on what should I do to make sure there's no downtime b/w DNS propagation.
CHello everyone,
I am currently using an API token for deploying updates to my Cloudflare Pages. I was wondering if there's a way to restrict this token's deployment capabilities to only specific sites. My goal is to ensure that each token can only deploy to a designated site for enhanced security and management. Does anyone know if Cloudflare provides a mechanism to set such restrictions on API tokens for Pages deployments?
Thank you for your assistance!
I am currently using an API token for deploying updates to my Cloudflare Pages. I was wondering if there's a way to restrict this token's deployment capabilities to only specific sites. My goal is to ensure that each token can only deploy to a designated site for enhanced security and management. Does anyone know if Cloudflare provides a mechanism to set such restrictions on API tokens for Pages deployments?
Thank you for your assistance!
Dhi @taczzy , thanks for the response. The reason why I need this to be a part of main domain is these are blog and doc websites which looks better if its under main domain.
_Third last example in this document would result in endless loop: https://developers.cloudflare.com/pages/configuration/redirects/
Should probably be changed.
/page/ /page/#fragment 301
Should probably be changed.
EGitHub
/page/ /page/#fragment 301 is a poor example since the resulting #fragment won't be sent to the server and it will result in an infinite loop.
Making the paths be different improves the example...
Making the paths be different improves the example...
Whow do I invite members to only pages?
CThey need Workers Admin
CThere's no way out of the box to restrict tokens to specific Pages Sites
CIf you can proxy the DNS Record for Vercel, changes are way quicker (in seconds) to make to Proxied DNS since you're not reliant on DNS Cache, just CF's internal DNS, then if you add a Custom Domain under the Pages Custom Domains tab it'll take care of deleting the old and creating the new at the same time for you.
Even if you kept it unproxied though, worst case will be Vercel would continue to get requests for a few hours until DNS Cache Expires, not the end of the world as long as you leave everything configured on Vercel's end and they can continue to serve responses
Might want to test on a subdomain first if your setup works with proxy enabled if you're not already using it. The most common mistake is having "Flexible" set under SSL/TLS -> Overview -> Encryption Mode. Should be Full Strict.
Even if you kept it unproxied though, worst case will be Vercel would continue to get requests for a few hours until DNS Cache Expires, not the end of the world as long as you leave everything configured on Vercel's end and they can continue to serve responses
Might want to test on a subdomain first if your setup works with proxy enabled if you're not already using it. The most common mistake is having "Flexible" set under SSL/TLS -> Overview -> Encryption Mode. Should be Full Strict.
HAnyone having issues with astro i18n?
Hcause mine isn't working properly
SHey Guys, So i need help with forwarding from go daddy. I added custom nameservers from Cloudfare to godaddy, but after that, I am unable to publish my website. Can anyone help me with the settings?
CThank you for your answer
DHey everyone. I am new to hosting on cloudfare with next.js and I keep on getting an error with Failed: build output directory not found. I would really appreciate it if anyone could offer me some guidance. Thanks
DHere is the entire log:
Cloudform_Log1.48KB
EAnyone here had any issues just in the past month or two with permissions during the execution of their build script? I've been happily using my bash-based build script for years, and then suddenly with no changes to it, all the
sed commands in it started throwing errors as if sed didn't have the proper permissions to create its temp files. Ex: The command: returns this error in the build logs: Anyone seen anything like this before? Btw, I tried created a temp folder within my build folder to see if that would help, but it didn't.
RDoes anyone have a recent working example of Pages + D1 + remix ?
IHi All, I just upgraded to Paid for pages due to the file size limitation and it still errors out. Am I missing something?
UThe file size limit is a hard limit no matter the plan you are on
UWhere did you get the idea that was not the case?
CI would follow the guide here to get started with next-on-pages, CF Pages utility to make next.js apps run on Pages:
https://github.com/cloudflare/next-on-pages/tree/main/packages/next-on-pages#cloudflarenext-on-pages
https://github.com/cloudflare/next-on-pages/tree/main/packages/next-on-pages#cloudflarenext-on-pages
CThe only size limit that would be raised is the max functions size, which with Workers Paid goes from 1 -> 10 MB. Is that what you saw?
A Paid Website Plan (like Pro/Business/Ent) would just give you more builds per month/custom domains/concurrent builds
A Paid Website Plan (like Pro/Business/Ent) would just give you more builds per month/custom domains/concurrent builds
ISo basically, I have to R2 for files over a certain size. Thanks!
CUnder the hood Pages uses KV, and KV has a technical limit of 25 MiB, can't be raised. That's why Pages has that limit as well
CWhat specific file it is? Sometimes people accidentally upload their cache dirs and get that error, that isn't the case for this? Usually pretty edge-case you'd have an asset that big, and in some cases with blazor wasm for example there's ways around it
IWe're hosting our corporate website on Pages. We're currently using this outsourced provider to handle the investor relations section, but service isn't great. Therefore, we're moving that to Pages too. The IR section has a bunch of public filings that are all huge PDFs.
Cah. Yea, could just throw those huge PDFs on R2 and leave the rest on Pages
CCan use R2 Custom Domain on a subdomain like cdn.example.com, use Cache Rule/Page Rule to force caching. Any Cache Hit doesn't cost you an R2 Operation, so pretty cheap and fast.
CWill pages ever have an Upload Endpoint via API just as workers has with upload worker module?
C@intsangity this is exactly what i do with my org. I even wrapped all the R2 apis to give a GUI for users to manage and access PDFs to not have to give a lot of people access to cloudflare dash
Ais there a way to troubleshoot segmentation faults in the build steps? cant reproduce it locally..
AI'm guessing the custom webpack configuration is coming from next-on-pages..
UUnless its something newer... no its not. My project I made a while ago doesnt have that
Abumping to a newer version of nextjs fixed the problem
XI am using
nuxtError 1102 - Worker exceeded resource limits
Cso will i be able to cloudflare for SaaS with pagesNo, Pages uses CF for SaaS under the hood. Your options are basically:
- Add them directly to Custom Domains of your Pages Project
- Use a Worker as your CF for SaaS Origin which proxies the request to Pages
If you are Enterprise you can ask for a Pages Custom Domain increase iirc, not sure about non-ent.. can I pass different images to resizing request for same size and charged once?
Has to be the same image and the same options
Cjust having a worker which fetches your custom domain. You'd be paying for invocations yea
DWhat can and cant be ran on pages? I am running on a hosting company. Just wondering if I can host something temporarily like a login page, and a way to interact with docker containers
UHeres the service specific terms for cloudflare pages:
https://www.cloudflare.com/service-specific-terms-developer-platform/#developer-platform-terms
https://www.cloudflare.com/service-specific-terms-developer-platform/#developer-platform-terms
DPerfect, thank you
