i dont even setted up pages just using the cf dns
i dont even setted up pages just using the cf dns
Nwithout ssl etc
HHave you added any DNS records? Do any of them have a little orange cloud next to them?
Nyes ive just saved * as name and applied proxy
HWhen you add your first proxied DNS record then it issues a universal certificate for you
Noh okay so chaika was right about those scrape bots, but this means cf counts bots as unique visitors?
CIn the free web traffic analytics, "Unique Visitors" is purely unique IPs in the timeframe
THey all. First time using pages and so far it has been great. I have one question though about the forwarding of www to non www apex domain. I followed the docs here: https://developers.cloudflare.com/pages/how-to/www-redirect/ and that did not seem to work. So I setup a page rule with the redirect instead, and that is working. What is the actual way to setup this redirect? Usually this is fairly straightfoward but I think the CNAME flattening is making it a bit harder for me to understand, and the fact that the info in the docs doesnt seem to work unless I am missing something. Thanks!
Cloudflare Docs
In this guide, you will learn how to redirect the www subdomain to your apex domain (example.com). This is a common question and can be achieved by …
CWhat is the actual way to setup this redirect?Either will work, Page Rules will eventually be going away though. It'll be announced when there is and there will be plenty of time, but yea one day your options will only be Bulk Redirects/Dynamic Redirects, not Page Rules
Usually this is fairly straightfoward but I think the CNAME flattening is making it a bit harder for me to understandI don't get where CNAME flattening plays into this. Generally not something you need to worry about, espec not when everything is proxied. Your apex custom domain cname for pages is using CNAME flattening, but it doesn't change anything with this redirect.
and the fact that the info in the docs doesnt seem to work unless I am missing somethingThe most common mistake with Bulk Redirects is you made the list but not a rule using that list. Your Bulk Redirect List will have a status of inactive if that is the case.
Ti'm using cloudflare pages with sveltekit, and have ssr ( +page.server.ts), but my site always get 500 errors when a page slug first load (i'm using dymanic slug [slug] ), but working well when load at second, and this errors repeate when delete cache. Anybody have the same errors like me. This erros don't show in log
LHi, I'm trying to deploy my pages project and I'm getting an error "no loader is confured for ".svg" files. I know you can configure loaders for workers via wrangler.toml, but it doesn't seem to be working for pages. Any ideas? thx
XWhat are some database solutions I can use for my SvelteKit pages app? Hyperdrive does not work, and D1 does not seem ready to be used either.
IHyperdrive isn't a database, it's just a way to connect to an existing database. If you need a database then you could investigate Supabase, Neon, Turso, Planetscale, bigger clouds like AWS or Azure, or one of the many other providers.
XYeah, i meant hyperdrive connected to a self-hosted VPS postgres database. Hyperdrive was said to not work with pages at all.
Is there any self-host alternatives though? I dont want to pay the massive fees that these cloud database providers have.
Is there any self-host alternatives though? I dont want to pay the massive fees that these cloud database providers have.
IYou can still connect to the VPS Postgres database from Pages.
IYou'll just need to use
postgres.jsohh, node-postgres isnt viable?
IHyperdrive can make things faster, but if you couldn't get it to work then that's fine.
XI had build issues with it, which explains a lot
II believe it should work? There's a couple specifically supported ones. One second.
XThese were my build logs when trying to integrate node-postgres
ISo node-postgres is supported, but only with polyfills.
XAs a note, this is a SvelteKit pages app
ISo that's likely why it's not working.
XWhat are polyfills?
XI just read on it and I guess its some sort of middleware to provide compatibility? How do I implement it?
IExactly, yeah. But generally you don't implement it yourself, there are packages to do it for you.
II'm not certain which ones would apply in this use-case however.
AThey’re like fake packages that copy the same style as the node ones so things work on browsers/workers
XAh I see
Xdoes postgres.js work out of the box on pages?
XI could try all of the alternative libraries, and if none work then look into some sort of polyfill solution
AThe Cloudflare Blog
Neon.tech is a database platform that allows you to branch your (Postgres compatible) database exactly like your code repository.And with the release of their Cloudflare Workers integration you can get started in minutes.
ATry this
XI'll definetally look into this. Also I've tried the documented "postgres + drizzle + workers" implementation but this was what started the issues in the first place
Xseems like the
pg
W
XThank you for pointing this out, I'm implementing this right now
XI'm running into an issue where trying to use AWS SES within pages does not work. A runtime error occurs:
Error: Dynamic require of \"node:buffer\" is not supportedIs there any way around this? I dont want to use other services like mailgun because they're way too pricey 
JThis is what I am currently doing to connect to a postgres db from within pages using the pg driver
1) Create a pages application, for mine I am using Remix.
2) Setup a worker called
3) Setup drizzle with an http proxy in your pages application. The pages app can use a service binding to call the
4) Make requests with drizzle, they will be proxied to your pages worker and your pages worker will use the connection pool from Hyperdrive.
With this setup you can connect to any postgres db.
For email using Amazon SES I was able to get @aws-sdk/client-ses working within a pages handler.
1) Create a pages application, for mine I am using Remix.
2) Setup a worker called
pg-proxy3) Setup drizzle with an http proxy in your pages application. The pages app can use a service binding to call the
pg-proxy4) Make requests with drizzle, they will be proxied to your pages worker and your pages worker will use the connection pool from Hyperdrive.
With this setup you can connect to any postgres db.
For email using Amazon SES I was able to get @aws-sdk/client-ses working within a pages handler.
AHi, I am using Cloudflare Turnstile captcha for my website. sometimes the captcha works but sometimes even if with the genuine user the captcha fails and returns error, not allowing user to do the payment. Please guide me on how to fix this ?
Nhow do I set node_compat for my page in dashboard?
N
NI am not sure it's this
HPages doesn't support
node_compatnodejs_compathow do i set
nodejs_compat
Nactually i have it set
