next-learn icon indicating copy to clipboard operation
next-learn copied to clipboard
verified publisher icon vercel

Chapter 6: Exploring Your Database

Open bradacraig opened this issue 1 year ago • 5 comments

After seeding the database and navigating to the Vercel data section I'm unable to see any tables in the dropdown. I also can't click on the dropdown as the cursor changes to a circle with a cross through upon hover. I'm assuming something has gone wrong with the seeding. I got this error in the terminal:

Error: Connection terminated unexpectedly at un.eval (webpack-internal:///(rsc)/./node_modules/.pnpm/@[email protected]/node_modules/@neondatabase/serverless/index.mjs:1258:44) at Object.onceWrapper (webpack-internal:///(rsc)/./node_modules/.pnpm/@[email protected]/node_modules/@neondatabase/serverless/index.mjs:422:39) at un.emit (webpack-internal:///(rsc)/./node_modules/.pnpm/@[email protected]/node_modules/@neondatabase/serverless/index.mjs:409:63) at x.eval (webpack-internal:///(rsc)/./node_modules/.pnpm/@[email protected]/node_modules/@neondatabase/serverless/index.mjs:1210:66) at x.emit (webpack-internal:///(rsc)/./node_modules/.pnpm/@[email protected]/node_modules/@neondatabase/serverless/index.mjs:409:63) at WebSocket.eval (webpack-internal:///(rsc)/./node_modules/.pnpm/@[email protected]/node_modules/@neondatabase/serverless/index.mjs:998:51) at callListener (webpack-internal:///(rsc)/./node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/ws/lib/event-target.js:290:14) at WebSocket.onClose (webpack-internal:///(rsc)/./node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/ws/lib/event-target.js:220:9) at WebSocket.emit (node:events:518:28) at WebSocket.emitClose (webpack-internal:///(rsc)/./node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/ws/lib/websocket.js:260:10) at TLSSocket.socketOnClose (webpack-internal:///(rsc)/./node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/ws/lib/websocket.js:1272:15) at TLSSocket.emit (node:events:530:35) at node:net:337:12 at TCP.done (node:_tls_wrap:657:7) at TCP.callbackTrampoline (node:internal/async_hooks:130:17) ⨯ uncaughtException: Error: Connection terminated unexpectedly at un.eval (webpack-internal:///(rsc)/./node_modules/.pnpm/@[email protected]/node_modules/@neondatabase/serverless/index.mjs:1258:44) at Object.onceWrapper (webpack-internal:///(rsc)/./node_modules/.pnpm/@[email protected]/node_modules/@neondatabase/serverless/index.mjs:422:39) at un.emit (webpack-internal:///(rsc)/./node_modules/.pnpm/@[email protected]/node_modules/@neondatabase/serverless/index.mjs:409:63) at x.eval (webpack-internal:///(rsc)/./node_modules/.pnpm/@[email protected]/node_modules/@neondatabase/serverless/index.mjs:1210:66) at x.emit (webpack-internal:///(rsc)/./node_modules/.pnpm/@[email protected]/node_modules/@neondatabase/serverless/index.mjs:409:63) at WebSocket.eval (webpack-internal:///(rsc)/./node_modules/.pnpm/@[email protected]/node_modules/@neondatabase/serverless/index.mjs:998:51) at callListener (webpack-internal:///(rsc)/./node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/ws/lib/event-target.js:290:14) at WebSocket.onClose (webpack-internal:///(rsc)/./node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/ws/lib/event-target.js:220:9) at WebSocket.emit (node:events:518:28) at WebSocket.emitClose (webpack-internal:///(rsc)/./node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/ws/lib/websocket.js:260:10) at TLSSocket.socketOnClose (webpack-internal:///(rsc)/./node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/ws/lib/websocket.js:1272:15) at TLSSocket.emit (node:events:530:35) at node:net:337:12 at TCP.done (node:_tls_wrap:657:7) at TCP.callbackTrampoline (node:internal/async_hooks:130:17)

This is what my database on vercel looks like:
Screen Shot 2024-07-11 at 4 38 06 PM

bradacraig avatar Jul 11 '24 04:07 bradacraig

i have exactly the same problem. have you solved it? @bradacraig

Mahdyrll avatar Aug 19 '24 14:08 Mahdyrll

No I haven't figured it out yet sorry! I'd love to know what I'm doing wrong so I can complete this

bradacraig avatar Aug 29 '24 21:08 bradacraig

Well my problem is solved. The only thing I did was that i just quitted and closed everything and checked it back the next day and it was working without any issues.

Mahdyrll avatar Sep 02 '24 07:09 Mahdyrll

It seems likely that the issue is related to connecting to the Neon database instead of Vercel. Neon has its own interface for managing databases, so you won’t be able to see the tables in Vercel’s data section.

Here are some steps you can follow to resolve the issue:

  1. Check the Connection in Neon: Go to the Neon console (https://neon.tech/) and ensure the database is created correctly and that the tables exist.

  2. Verify Credentials: Make sure the connection credentials in your project match those provided by Neon.

  3. Retry Seeding: If the tables are not created, try running the seeding script again and check if it completes without errors.

  4. Check Logs: Look into the application logs to see if there are any other errors affecting the connection.

  5. Ensure the Connection: If you still face connection issues, double-check that the client is configured correctly to connect to Neon, and there are no network or firewall issues blocking the connection.

By following these steps, you should be able to manage your tables through Neon’s interface instead of Vercel.

Starklord17 avatar Sep 03 '24 13:09 Starklord17

See https://github.com/vercel/next-learn/issues/879#issuecomment-2398960727

It solved my issue. Long in short, you may have done everything right and just need to click into the search bar to see the tables available.

N-G-Asker avatar Nov 13 '24 23:11 N-G-Asker