27:T441,---------------------- To interact with your production database deployed on Fly.io, you can open a tunnel to your Fly production database using the `fly proxy` command. Here are the steps: 1. Open a tunnel to your Fly production database: ``` fly proxy 5432 -a ``` 2. After opening the tunnel, you can execute `wasp db studio` to interact with your database using Prisma Studio. Please remember to remove the `DATABASE_URL` with the production database URL from `.env.server` if you put it there, to avoid accidentally making changes to the production database later. If you encounter any issues while initiating a new app, you should run `flyctl apps destroy ` before trying again. Fly does not allow you to create multiple apps with the same name. Sources: - **Discord support thread: How to interact with database in prisma studio after deployment?** () ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------28:T4a6,---------------------- The error message you're seeing typically appears when Wasp is unable to connect to the database. This could be due to several reasons: 1. The database is not running: Ensure that your database is up and running. If you're using a local database, you can start it using the `wasp start db` command. 2. Incorrect `DATABASE_URL`: The `DATABASE_URL` in your `.env.server` file might be incorrect. Ensure that it points to the correct database instance. 3. Network issues: If you're trying to connect to a remote database, there might be network issues preventing the connection. Ensure that your network allows connections to the database. 4. Docker not running: If you're using Docker and it's not running, you might see this error. Ensure that Docker is installed and running. If you're trying to connect to your production database via a tunnel using `fly proxy`, ensure that the tunnel is up and running. You might need to keep the terminal window where you ran `fly proxy` open while you're using the database. If you're still having issues, you might want to ask for help in the Wasp community or check the Wasp and Prisma documentation for more information.29:T527,Sources: - **Github Issue (closed): wasp-cli command not handling white-space in path while running app** () - **Docs > Data-model > Databases > Connecting to a Database** () - **Discord support thread: Need help running Wasp app** () - **Github Issue (open): Have `wasp start db` produce nice warning message if docker daemon is not running** () - **Github Issue (open): [Managed dev db] Allow automatic and/or manual choosing of another port than 5432** () - **Github Issue (closed): Fix database initialization** () - **Github Issue (closed): During development, produce a nice error message for user if database is not running but it should be** () - **Discord support thread: Cant start database docker is not working on wsl properly** () ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

How to edit google oauth credits

How to edit google oauth credits

Continue the conversation

Wasp

Continue the conversation

Wasp

Similar Threads