Cloudflare Developers•15mo ago

As in, can I use the binding with my next app?

AJR•10/21/24, 12:44 AM

Sorry, which binding is that? Not sure I'm following.

Mmr nooli As in, can I use the binding with my next app?

marcbejar•10/21/24, 7:30 AM

I think you are looking for this:
https://developers.cloudflare.com/workers/frameworks/framework-guides/nextjs/

Cloudflare Docs

Next.js | Cloudflare Workers docs

Create an Next.js application and deploy it to Cloudflare Workers with Workers Assets.

Mmarcbejar I think you are looking for this: https://developers.cloudflare.com/workers/fram...

mr nooliOP•10/21/24, 8:23 AM

Yep, exactly! The hyperdrive plugin with next on pages or open next

mr nooliOP•10/21/24, 9:26 AM

That’s really interesting actually, I tried to use the neon driver with open next @marcbejar but ran into this issue, https://github.com/cloudflare/next-on-pages/issues/605#issuecomment-2419842548

is this something that hyperdrive would fix?

GitHub

[🐛 Bug]: `pg` does not work · Issue #605 · cloudflare/next-on-pages

next-on-pages environment related information System: Platform: linux Arch: x64 Version: #202312122204 SMP PREEMPT_DYNAMIC Tue Dec 12 22:43:56 UTC 2023 CPU: (16) x64 AMD EPYC 7B13 Memory: 63 GB She...

marcbejar•10/21/24, 9:48 AM

@mr nooli If you are using Hyperdrive with a NEON connected to it, cloudflare recomends using postgres instead of neon driver or pg. See:

https://developers.cloudflare.com/hyperdrive/examples/neon/

Cloudflare Docs

Connect to Neon | Hyperdrive

Connect Hyperdrive to a Neon Postgres database.

mr nooliOP•10/21/24, 10:00 AM

Ah that's really interesting, I'm unfortunately using supabase and as far as I can see prisma doesn't support the postgres driver! They do however support neon and pg, and pg has been buggy from day 1! I've not been able to get it to work at all.

AJR•10/21/24, 12:50 PM

We support pg and postgres.js drivers. Both work very well as standalones, but depending on what Prisma is doing with them it may not cooperate.

I don't know if we've evaluated the neon driver. We all use and love neon as a product, might be worth giving it a look. I'll mention to our product folks and see what they think.

mr nooliOP•10/21/24, 1:00 PM

That would be really useful! I want to migrate the opennext but I'm just running into a bunch of bugs, that I'm clueless on how to fix!

AJR•10/21/24, 1:02 PM

Unfortunately I'm far from the JavaScript ecosystem expert in our department. If you are finding bugs, please do file issues. I know that our library folks are very invested in making this a good experience

mr nooliOP•10/21/24, 1:06 PM

Issue is, I've done it before and for a small time I was on next-on-pages but whenever I encountered an issue, I would tell prisma and then prisma would tell cf and then it'd end up going nowhere. Most of the issues that come up are bc of prisma not playing nice with cloudflare/adapters etc.

AJR•10/21/24, 1:07 PM

Ahhh. Yeah, I can appreciate that.

Mmr nooli Ah that's really interesting, I'm unfortunately using supabase and as far as I c...

thomasgauvin•10/21/24, 1:32 PM

Surprised to see Prisma doesn't natively support a driver for postgres.js https://www.prisma.io/docs/orm/overview/databases/database-drivers

Might be something worth talking with them about

Database drivers | Prisma Documentation

Learn how Prisma connects to your database using the built-in drivers and how you can use Prisma along with other JavaScript database drivers using driver adapters (Preview)

Tthomasgauvin Surprised to see Prisma doesn't natively support a driver for postgres.js https:...

mr nooliOP•10/21/24, 1:33 PM

I agree - but I'm also not an expert in the field and most of this goes straight over my head

I just want my app faster! It's very fast right now with Vercel's top level of function compute power, but I feel like it could be faster and ik that the pricing won't scale.

Mmr nooli I agree - but I'm also not an expert in the field and most of this goes straight...

thomasgauvin•10/21/24, 1:37 PM

@mr nooli actually, you should look into the new support for assets on workers https://developers.cloudflare.com/workers/frameworks/framework-guides/nextjs/

you could then use the 'pg' driver as recommended ('pg' is not supported on pages, only 'postgres')

Cloudflare Docs

Next.js | Cloudflare Workers docs

Create an Next.js application and deploy it to Cloudflare Workers with Workers Assets.

mr nooliOP•10/21/24, 1:39 PM

Ah, so this would mean deploying on workers? Does that include the CI pipeline from pages?

mr nooliOP•10/21/24, 1:39 PM

(Open next right?)

Mmr nooli Ah, so this would mean deploying on workers? Does that include the CI pipeline f...

thomasgauvin•10/21/24, 1:43 PM

Yes, I would recommend following the guide I linked to get a sample app up and connecting to your database to see if it's possible for you to migrate

mr nooliOP•10/21/24, 1:44 PM

I’ll give it a go tonight!

mr nooliOP•10/21/24, 1:44 PM

But also worth me questioning if it’s worth it as I had managed to get a very small part of my app running on next on pages and it matched the page speed (the web dev page speed insights) as my Vercel app.

mr nooliOP•10/21/24, 1:44 PM

It should be faster in theory right?

Mmr nooli It should be faster in theory right?

thomasgauvin•10/21/24, 8:20 PM

I don't know the specifics of your stack so I can't confirm if it would be faster or not. Hyperdrive makes it faster for you to connect to a regional database from global workers

mr nooliOP•10/21/24, 9:22 PM

Let's give it a go and find out ig!

mr nooliOP•10/21/24, 10:09 PM

no dice! Just so many errors popping up!

I'm gonna give next-on-pages a go, and if there's no luck there I'm gonna just have to drop the idea of using CF for the mo

thomasgauvin•10/23/24, 3:37 PM

@mr nooli I think Pages should also have enhanced compatibility, you should use https://developers.cloudflare.com/workers/runtime-apis/nodejs/#get-started

Cloudflare Docs

Node.js compatibility | Cloudflare Workers docs

Node.js APIs available in Cloudflare Workers

AJR•10/25/24, 1:30 PM

New blog about the Hyperdrive Tunnel integration is out. It goes into some depth, if anyone has been curious about how it works.

https://blog.cloudflare.com/elephants-in-tunnels-how-hyperdrive-connects-to-databases-inside-your-vpc-networks/

The Cloudflare Blog

Elephants in tunnels: how Hyperdrive connects to databases inside y...

Hyperdrive (Cloudflare’s globally distributed SQL connection pooler and cache) recently added support for directing database traffic from Workers across Cloudflare Tunnels. We dive deep on what it took to add this feature.

Marat•10/25/24, 11:57 PM

Hello, has anyone faced "Internal Server Error" when creating Hyperdrive configuration?
I tested DB connection from server and local machine. All cloudflare ipv4 ranges where allow listed for accessing DB (https://www.cloudflare.com/ips/)
Also tryed

?ssl=true

?ssl=true

and

?sslmode=require

?sslmode=require

.
Any other hints how to fix the problem?

IP Ranges | Cloudflare

This page is intended to be the definitive source of Cloudflare’s current IP ranges.

TW•10/26/24, 2:54 AM

Does Hyperdrive support connecting from non-Cloudflare services (e.g. from Fly.io)? Because it seems that changes from CF Workers through Hyperdrive is not propagated immediately to the "bare" DB, so my service in Fly.io that connects directly doesn't see it yet

VIO•10/27/24, 3:27 PM

Hello there, I have a postgres db setup on a machine, a CF tunnel pointing to that db, and Acces service auth setup above all, is there a way to get the connection string by API and simply use that in a nodejs project?

okku•10/30/24, 3:22 AM

Hi, has anyone been experiencing caching problem on hyperdrive?
My website cannot connect to a database when connecting through hyperdrive. It looks like it is resolved for 5-10 mins after either switching on and off the caching.
Metrics reads fine, and it can connect to the database with cache and without cache, but it only works for 5-10 mins on both cases.

Nick•10/30/24, 11:36 AM

I try to setup Hyperdrive with a tunnel. Followed all the steps 3 times but get this error:
"Failed to connect to database using the provided information: Internal error."

On the server "cloudflared tail --level debug" and in the dashboards 'Access authentication logs' i dont see anything happen.
Tunnel status on dashboard says "Healthy".
Everytime i try to setup it up in Application > Policies a policy is automaticly created.
First time I run "cloudflared tail --level debug" i got the error "Cannot determine default origin certificate path." which i fixed with this

thomasgauvin•10/30/24, 7:27 PM

Hyperdrive update:

2024-10-30: New Hyperdrive configurations to private databases using Tunnels are validated before creation to make it easier to troubleshoot connectivity issues

https://developers.cloudflare.com/hyperdrive/platform/changelog/#2024-10-30

SteffTek•11/4/24, 12:11 PM

Hey guys! I have a small problem with hyperdrive. I want to test it with a local postgres instance in docker, to which I can connect without problems, but my worker script says it's failing to authenticate due to bad password. Same connection string works with drizzle for migrations

AJR•11/4/24, 1:07 PM

Interesting. Same connection string works in hyperdrive?

What username and password did you provide when making your Hyperdrive? I wonder if there was some shell escaping or something that caused it to not have your DB password stored correctly?

AAJR Interesting. Same connection string works in hyperdrive? What username and pa...

SteffTek•11/4/24, 1:19 PM

yeah sorry im just incredibly stupid. the db controller that fires first somehow still had the old d1 object as param and typescript screamed at me and i just ignored it...

AJR•11/4/24, 1:30 PM

Heh. Happens to the best of us. Good luck!

DoggeSlapper•11/6/24, 6:59 PM

I'm trying to use hyperdrive with neon drizzle & postgresjs but I'm getting

✘ [ERROR] Uncaught (async) Error: write CONNECT_TIMEOUT 2a4a9d73ee44058fe7577f3b613e1ae9.hyperdrive.local:5432

✘ [ERROR] Uncaught (async) Error: write CONNECT_TIMEOUT 2a4a9d73ee44058fe7577f3b613e1ae9.hyperdrive.local:5432

DoggeSlapper•11/6/24, 7:18 PM

I been trying pg & postgresjs but cant manage to cconnect

DoggeSlapper•11/6/24, 7:31 PM

I have reduced to:

const sql = postgres(env.HYPERDRIVE.connectionString, { ssl: true });
const result = await sql`SELECT * FROM pg_tables;`;
console.log(result);

const sql = postgres(env.HYPERDRIVE.connectionString, { ssl: true });
const result = await sql`SELECT * FROM pg_tables;`;
console.log(result);

Without SSL true I get

✘ [ERROR] Uncaught (in promise) PostgresError: connection is insecure (try using `sslmode=require`)

✘ [ERROR] Uncaught (in promise) PostgresError: connection is insecure (try using `sslmode=require`)

AJR•11/6/24, 7:31 PM

Is your database configured with

ssl=on

ssl=on

DoggeSlapper•11/6/24, 7:31 PM

When I have it enabled I get timeout error

Uncaught (in promise) Error: write CONNECT_TIMEOUT f86bad4f8437b66de3bf8efae5264dd3.hyperdrive.local:5432

Uncaught (in promise) Error: write CONNECT_TIMEOUT f86bad4f8437b66de3bf8efae5264dd3.hyperdrive.local:5432

AJR•11/6/24, 7:32 PM

SSL is required to be configured for databases Hyperdrive connects to.

AAJR SSL is required to be configured for databases Hyperdrive connects to.

DoggeSlapper•11/6/24, 7:32 PM

it's ?sslmode=require

DoggeSlapper•11/6/24, 7:34 PM

I'm trying to use neon with hyperdrive from local

DDoggeSlapper it's ?sslmode=require

AJR•11/6/24, 7:34 PM

That's the client-side request mode. Is the database itself set up with SSL?

AAJR That's the client-side request mode. Is the database itself set up with SSL?

DoggeSlapper•11/6/24, 7:39 PM

afaik neon uses ssl right?

DoggeSlapper•11/6/24, 7:41 PM

export WRANGLER_HYPERDRIVE_LOCAL_CONNECTION_STRING_HYPERDRIVE= my connection string
pnpm run dev

export WRANGLER_HYPERDRIVE_LOCAL_CONNECTION_STRING_HYPERDRIVE= my connection string
pnpm run dev

With ssl I get TIMEOUT

DoggeSlapper•11/6/24, 7:47 PM

Error: write CONNECT_TIMEOUT 00cb16054d82c846e02014158175759c.hyperdrive.local:5432
    at connectTimedOut (file:///Users/leon/code/domainsHunter/node_modules/.pnpm/postgres@3.4.5/node_modules/postgres/cf/src/connection.js:259:20)
    at done (file:///Users/leon/code/domainsHunter/node_modules/.pnpm/postgres@3.4.5/node_modules/postgres/cf/src/connection.js:1035:8)
    at new Query (file:///Users/leon/code/domainsHunter/node_modules/.pnpm/postgres@3.4.5/node_modules/postgres/cf/src/query.js:35:9)
    at sql (file:///Users/leon/code/domainsHunter/node_modules/.pnpm/postgres@3.4.5/node_modules/postgres/cf/src/index.js:113:11)
    at null.<anonymous> (file:///Users/leon/code/domainsHunter/apps/workflows/src/index.ts:104:27)
    at async Promise.all (index 0)
    at async Object.queue (file:///Users/leon/code/domainsHunter/apps/workflows/src/index.ts:97:3) {
  code: 'CONNECT_TIMEOUT',
  errno: 'CONNECT_TIMEOUT',
  address: '00cb16054d82c846e02014158175759c.hyperdrive.local',
  port: 5432,
  query: undefined,
  parameters: undefined,
  args: [],
  types: null
}

Error: write CONNECT_TIMEOUT 00cb16054d82c846e02014158175759c.hyperdrive.local:5432
    at connectTimedOut (file:///Users/leon/code/domainsHunter/node_modules/.pnpm/postgres@3.4.5/node_modules/postgres/cf/src/connection.js:259:20)
    at done (file:///Users/leon/code/domainsHunter/node_modules/.pnpm/postgres@3.4.5/node_modules/postgres/cf/src/connection.js:1035:8)
    at new Query (file:///Users/leon/code/domainsHunter/node_modules/.pnpm/postgres@3.4.5/node_modules/postgres/cf/src/query.js:35:9)
    at sql (file:///Users/leon/code/domainsHunter/node_modules/.pnpm/postgres@3.4.5/node_modules/postgres/cf/src/index.js:113:11)
    at null.<anonymous> (file:///Users/leon/code/domainsHunter/apps/workflows/src/index.ts:104:27)
    at async Promise.all (index 0)
    at async Object.queue (file:///Users/leon/code/domainsHunter/apps/workflows/src/index.ts:97:3) {
  code: 'CONNECT_TIMEOUT',
  errno: 'CONNECT_TIMEOUT',
  address: '00cb16054d82c846e02014158175759c.hyperdrive.local',
  port: 5432,
  query: undefined,
  parameters: undefined,
  args: [],
  types: null
}

AJR•11/6/24, 7:53 PM

Ohhh, this is local dev. You're using

wrangler dev

wrangler dev

AAJR Ohhh, this is local dev. You're using `wrangler dev`?

DoggeSlapper•11/6/24, 7:54 PM

yes I'm trying to connect to neon during my local development with hyperdrive

AJR•11/6/24, 7:55 PM

Got it. This is a known issue, fix is going out with the next

workerd

workerd

release.

Error: write CONNECT_TIMEOUT 00cb16054d82c846e02014158175759c.hyperdrive.local:5432 at connectTimedOut (file:///Users/leon/code/domainsHunter/node_modules/.pnpm/postgres@3.4.5/node_modules/postgres/cf/src/connection.js:259:20) at done (file:///Users/leon/code/domainsHunter/node_modules/.pnpm/postgres@3.4.5/node_modules/postgres/cf/src/connection.js:1035:8) at new Query (file:///Users/leon/code/domainsHunter/node_modules/.pnpm/postgres@3.4.5/node_modules/postgres/cf/src/query.js:35:9) at sql (file:///Users/leon/code/domainsHunter/node_modules/.pnpm/postgres@3.4.5/node_modules/postgres/cf/src/index.js:113:11) at null.<anonymous> (file:///Users/leon/code/domainsHunter/apps/workflows/src/index.ts:104:27) at async Promise.all (index 0) at async Object.queue (file:///Users/leon/code/domainsHunter/apps/workflows/src/index.ts:97:3) { code: 'CONNECT_TIMEOUT', errno: 'CONNECT_TIMEOUT', address: '00cb16054d82c846e02014158175759c.hyperdrive.local', port: 5432, query: undefined, parameters: undefined, args: [], types: null }

As in, can I use the binding with my next app?

Similar Threads

Similar Threads

Similar Threads