Wasp•4w ago

Google oAuth: change server name by app name?

https://whitehatseotactics.com/login In the Google oAuth page it displays the server URL

16 Replies

Hi @NEROX. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave: ---------------------- To address your question about changing the server name displayed in the Google OAuth page for your Wasp application, I can provide some guidance based on the available information. The server URL shown in the Google OAuth page is typically derived from the WASP_SERVER_URL environment variable. This variable is crucial for OAuth providers to generate the correct redirect URL. Here are the steps you can take to potentially change what's displayed: 1. Make sure you have set the WASP_SERVER_URL environment variable correctly for your production environment. It should be the full URL of your server, including the protocol (https://). Link to migration guide (https://wasp-lang.dev/docs/migrate-from-0-12-to-0-13) 2. Update the redirect URL in your Google OAuth app settings. The new format for the redirect URL should be:

   {serverUrl}/auth/google/callback

   {serverUrl}/auth/google/callback

Replace {serverUrl} with your actual server URL. Link to Google setup guide (https://wasp-lang.dev/docs/auth/social-auth/google#3-creating-a-google-oauth-app) 3. Ensure that your GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET environment variables are correctly set in your .env.server file or in your production environment. Link to Google env vars (https://wasp-lang.dev/docs/auth/social-auth/google#4-adding-environment-variables) 4. If you're using a custom domain for your app, make sure it's properly set up and that the WASP_SERVER_URL reflects this custom domain. If after following these steps you still see the server URL instead of your app name, it's possible that this is a limitation of how Google displays OAuth information, and may not be directly controllable through Wasp configuration. For more detailed assistance, you might want to check the Wasp documentation on Google Auth (https://wasp-lang.dev/docs/auth/social-auth/google) or reach out to the Wasp community for specific guidance related to your deployment setup. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @NEROX, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist: Perhaps try again in 15mins?

NEROXOP•4w ago

@kapa.ai how can I change my server address from default Fly server address to a custom domain address

kapa.ai•4w ago

Let me check the knowledge base for you again. One moment! :books: ---------------------- To change your server address from the default Fly.io server address to a custom domain address in a Wasp application, you need to follow these steps: 1. Add your custom domain to your Fly.io app: Run the following command, replacing mycoolapp.com with your actual domain:

   wasp deploy fly cmd --context client certs create mycoolapp.com

   wasp deploy fly cmd --context client certs create mycoolapp.com

This command will provide you with instructions to add DNS records for your domain Wasp CLI Deployment Docs (https://wasp-lang.dev/docs/advanced/deployment/cli#using-a-custom-domain-for-your-app). 2. Add the DNS records to your domain provider as instructed by the output of the previous command. This typically involves adding an A record and an AAAA record Wasp CLI Deployment Docs (https://wasp-lang.dev/docs/advanced/deployment/cli#using-a-custom-domain-for-your-app). 3. Update the WASP_WEB_CLIENT_URL environment variable for your server app to use your custom domain:

   wasp deploy fly cmd --context server secrets set WASP_WEB_CLIENT_URL=<https://mycoolapp.com>

   wasp deploy fly cmd --context server secrets set WASP_WEB_CLIENT_URL=<https://mycoolapp.com>

This step is crucial to keep your CORS configuration up to date Wasp CLI Deployment Docs (https://wasp-lang.dev/docs/advanced/deployment/cli#using-a-custom-domain-for-your-app). 4. Update the WASP_SERVER_URL environment variable to reflect your new custom domain. You can do this using the Fly.io CLI or through your deployment platform's interface Wasp Manual Deployment Docs (https://wasp-lang.dev/docs/advanced/deployment/manually#environment-variables). 5. If you're using any authentication providers (like Google or GitHub OAuth), make sure to update the authorized redirect URIs in their respective developer consoles to use your new custom domain. After completing these steps, your Wasp application should be accessible via your custom domain, and all the necessary configurations (like CORS and OAuth redirects) should work correctly with the new domain. Remember to replace mycoolapp.com with your actual custom domain in all the commands and configurations mentioned above. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @NEROX, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist: Perhaps try again in 15mins?

NEROXOP•4w ago

@kapa.ai hey I lost connection with my server

kapa.ai•4w ago

Let me check the knowledge base for you again. One moment! :books: ---------------------- I apologize to hear that you've lost connection with your server. To help you troubleshoot this issue, I'll need some more information. Here are a few questions and suggestions to help diagnose the problem: 1. Are you using Fly.io for deployment? If so, can you check the Fly.io dashboard for any error messages or logs? 2. Can you access the server logs? If you're using Fly.io, you can try running:

   wasp deploy fly cmd --context server logs

   wasp deploy fly cmd --context server logs

This might give you more insight into what's happening Wasp CLI Deployment Docs (https://wasp-lang.dev/docs/advanced/deployment/cli#using-a-custom-domain-for-your-app). 3. Have you made any recent changes to your app or deployment configuration? 4. Is your client still accessible, or is it just the server that's unreachable? 5. If you're using a custom domain, have you checked if there are any DNS issues? 6. Have you tried redeploying your app? Sometimes, a simple redeployment can resolve connection issues:

   wasp deploy fly deploy

   wasp deploy fly deploy

If none of these steps help, you might want to consider reaching out to the Wasp community on Discord (https://discord.gg/rzdnErX) for more specific assistance. They might be able to provide more targeted help based on your specific setup and circumstances. Remember, without more details about your specific situation, it's challenging to pinpoint the exact cause of the lost connection. If you can provide more information about your deployment setup and any error messages you're seeing, that would be very helpful in diagnosing the issue. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @NEROX, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist: Perhaps try again in 15mins?

NEROXOP•4w ago

@kapa.ai Access to XMLHttpRequest at 'https://whitehatseotactics-server.fly.dev/auth/me' from origin 'https://whitehatseotactics.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

kapa.ai•4w ago

Let me check the knowledge base for you again. One moment! :books: ---------------------- It appears you're encountering a CORS (Cross-Origin Resource Sharing) issue with your Wasp application. This error occurs when your client-side application (hosted at https://whitehatseotactics.com) is trying to make a request to your server (hosted at https://whitehatseotactics-server.fly.dev), but the server isn't configured to allow requests from that origin. To resolve this issue, you need to properly configure CORS on your server. Here are the steps you can take: 1. First, make sure your WASP_WEB_CLIENT_URL environment variable is correctly set to your client's URL. You can do this using the Fly.io CLI:

   wasp deploy fly cmd --context server secrets set WASP_WEB_CLIENT_URL=<https://whitehatseotactics.com>

   wasp deploy fly cmd --context server secrets set WASP_WEB_CLIENT_URL=<https://whitehatseotactics.com>

This step is crucial because Wasp uses this environment variable to configure CORS Wasp Manual Deployment Docs (https://wasp-lang.dev/docs/advanced/deployment/manually#environment-variables). 2. If you've recently changed your client URL, you might need to redeploy your server for the changes to take effect:

   wasp deploy fly deploy

   wasp deploy fly deploy

3. If the issue persists, you might need to customize the CORS configuration. You can do this by modifying the server middleware. Create or modify a file (e.g., src/server/middleware.js or src/server/middleware.ts) with the following content:

   import cors from 'cors'
   import { config } from 'wasp/server'

   export const serverMiddlewareFn = (middlewareConfig) => {
     middlewareConfig.set('cors', cors({ 
       origin: [config.frontendUrl, '<https://whitehatseotactics.com'],>
       credentials: true
     }))
     return middlewareConfig
   }

   import cors from 'cors'
   import { config } from 'wasp/server'

   export const serverMiddlewareFn = (middlewareConfig) => {
     middlewareConfig.set('cors', cors({ 
       origin: [config.frontendUrl, '<https://whitehatseotactics.com'],>
       credentials: true
     }))
     return middlewareConfig
   }

Then, in your main.wasp file, add:

   app myApp {
     // ...
     server: {
       middlewareConfigFn: import { serverMiddlewareFn } from "@src/server/middleware"
     },
   }

   app myApp {
     // ...
     server: {
       middlewareConfigFn: import { serverMiddlewareFn } from "@src/server/middleware"
     },
   }

This explicitly sets up CORS to allow requests from your frontend URL Wasp Middleware Config Docs (https://wasp-lang.dev/docs/advanced/middleware-config#1-customize-global-middleware). 4. After making these changes, redeploy your server. If you're still experiencing issues after trying these steps, it might be worth checking your server logs for any error messages:

wasp deploy fly cmd --context server logs

wasp deploy fly cmd --context server logs

Remember, CORS issues can sometimes be tricky to debug. If you continue to face problems, you might want to reach out to the Wasp community on Discord for more specific assistance. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @NEROX, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist: Perhaps try again in 15mins?

NEROXOP•4w ago

@kapa.ai $ flyctl postgres create --name whitehatseotactics-db --region mia --vm-size shared-cpu-1x --initial-cluster-size 1 --volume-size 1 automatically selected personal organization: Leo Golubyev Creating postgres cluster in organization personal Creating app... Setting secrets on app whitehatseotactics-db... Provisioning 1 of 1 machines with image flyio/postgres-flex:16.4@sha256:f107dbfaa732063b31ee94aa728c4f5648a672259fd62bfaa245f9b7a53b5479 Error: failed to create volume: failed to create volume: internal: failed to get app: sql: no rows in result set (Request ID: 01JDM5H3D55Q2F5A420TDR54TZ-mad) 🚀 There was an error running "wasp deploy fly create-db <region>". Please review the error and try again (if appropriate). ❌ --- [Error] Deploy command failed: --------------------------------------------- Deploy command failed with exit code: 1

kapa.ai•4w ago

Let me check the knowledge base for you again. One moment! :books: ---------------------- I apologize for the error you're encountering while trying to create a Postgres database for your Wasp application on Fly.io. This error suggests there was an issue with creating the volume for your database. Here are a few steps you can try to resolve this issue: 1. First, try running the command again. Sometimes, these errors can be transient due to temporary issues on Fly.io's side. 2. If the error persists, you can try creating the database manually using the Fly.io CLI instead of the Wasp CLI:

   fly postgres create --name whitehatseotactics-db --region mia --vm-size shared-cpu-1x --initial-cluster-size 1 --volume-size 1

   fly postgres create --name whitehatseotactics-db --region mia --vm-size shared-cpu-1x --initial-cluster-size 1 --volume-size 1

This is essentially the same command that Wasp is trying to run under the hood Wasp CLI Deployment Docs (https://wasp-lang.dev/docs/advanced/deployment/cli#create-db). 3. If you're still encountering issues, you might want to try a different region. You can see a list of available regions by running:

   fly platform regions

   fly platform regions

Then, try creating the database in a different region, for example:

   fly postgres create --name whitehatseotactics-db --region lax --vm-size shared-cpu-1x --initial-cluster-size 1 --volume-size 1

   fly postgres create --name whitehatseotactics-db --region lax --vm-size shared-cpu-1x --initial-cluster-size 1 --volume-size 1

4. If none of the above steps work, you might want to check if there are any existing resources with the same name that might be causing conflicts. You can list your existing Postgres databases with:

   fly postgres list

   fly postgres list

If you see a database with the same name, you might need to delete it first or choose a different name. 5. If you're still facing issues, it might be worth reaching out to Fly.io support or checking their status page for any ongoing issues. After successfully creating the database, you can continue with the rest of the deployment process using the Wasp CLI:

wasp deploy fly deploy

wasp deploy fly deploy

If you continue to encounter problems, you might want to consider deploying your app manually following the manual deployment guide (https://wasp-lang.dev/docs/advanced/deployment/manually#flyio-server-and-database), which gives you more control over each step of the process. Remember, if you're still stuck, the Wasp community on Discord is always available to help with more specific issues. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @NEROX, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist: Perhaps try again in 15mins?

miho•4w ago

@NEROX on how to set a custom backend URL: 1. Create cert for a subdomain e.g. api.yourapp.com on Fly (like you did for the client domain) 2. Set the correct WASP_SERVER_URL on the server and REACT_APP_API_URL when building the client Something like this: wasp deploy fly cmd --context server certs create api.mycoolapp.com Of course ... update the Google OAuth redirect URL to have the new server URL as well 🙂

NEROXOP•4w ago

and what about

Error: failed to create volume: failed to create volume: internal: failed to get app: sql: no rows in result set (Request ID: 01JDM999NSJXDWD1WJRTHS0FB9-mad)
🚀  There was an error running "wasp deploy fly create-db <region>". Please review the error and try again (if appropriate).


❌ --- [Error] Deploy command failed: ---------------------------------------------

@kapa.ai Provisioning 1 of 1 machines with image flyio/postgres-flex:16.4@sha256:f107dbfaa732063b31ee94aa728c4f5648a672259fd62bfaa245f9b7a53b5479\n' + 'Error: failed to create volume: failed to create volume: internal: failed to get app: sql: no rows in result set (Request ID: 01JDMDQ3MNKMVCX823Y1Q2GXV1-mad)\n' }

kapa.ai•4w ago

Let me check the knowledge base for you again. One moment! :books: ---------------------- I understand you're still encountering an error while trying to create a Postgres database for your Wasp application on Fly.io. This error is similar to the one you reported earlier, indicating a persistent issue with creating the volume for your database. Given that this error is recurring, here are some additional steps you can try: 1. Check your Fly.io account status: Make sure your account is in good standing and that you haven't hit any resource limits. You can check this in your Fly.io dashboard. 2. Try creating a smaller volume: The error might be related to resource allocation. Try creating a database with a smaller volume size:

   fly postgres create --name whitehatseotactics-db --region mia --vm-size shared-cpu-1x --initial-cluster-size 1 --volume-size 0.5

   fly postgres create --name whitehatseotactics-db --region mia --vm-size shared-cpu-1x --initial-cluster-size 1 --volume-size 0.5

3. Attempt to create the database in a different organization: If you have multiple organizations, try specifying a different one:

   fly postgres create --name whitehatseotactics-db --region mia --vm-size shared-cpu-1x --initial-cluster-size 1 --volume-size 1 --org your-org-name

   fly postgres create --name whitehatseotactics-db --region mia --vm-size shared-cpu-1x --initial-cluster-size 1 --volume-size 1 --org your-org-name

4. Check for any Fly.io service issues: Visit the Fly.io status page to see if there are any ongoing issues that might be affecting database creation. 5. Clean up and retry: If there's a possibility that a partially created resource is causing issues, you can try to remove it and start fresh:

   fly apps destroy whitehatseotactics-db

   fly apps destroy whitehatseotactics-db

Then try creating the database again. 6. Use the Fly.io support channels: If none of these steps work, it might be time to reach out to Fly.io support directly. They can provide more insight into what's causing this persistent error. If you continue to face issues with the Fly.io deployment, you might want to consider alternative deployment options for your Wasp application. The Wasp deployment documentation (https://wasp-lang.dev/docs/advanced/deployment/manually) provides information on other deployment methods that you could explore. Remember, the Wasp community on Discord is also a great resource for troubleshooting deployment issues. They might have encountered similar problems and could provide more specific guidance based on their experiences. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @NEROX, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist: Perhaps try again in 15mins?

NEROXOP•4w ago

@kapa.ai

rootall@Nerox-LpTp:~/apps/WhiteHatSeoTactics/app$    fly apps destroy whitehatseotactics-db
 Destroying an app is not reversible.
? Destroy app whitehatseotactics-db? Yes
Destroyed app whitehatseotactics-db
rootall@Nerox-LpTp:~/apps/WhiteHatSeoTactics/app$ wasp deploy fly create-db iad
$ flyctl version
flyctl v0.3.41 linux/amd64 Commit: b983a0d0b98cf771c58d1ecb998097e641c2fb7b BuildDate: 2024-11-25T17:17:41Z
$ flyctl auth whoami
[email protected]
🚀  Creating your DB on Fly.io! 
$ flyctl postgres create --name whitehatseotactics-db --region iad --vm-size shared-cpu-1x --initial-cluster-size 1 --volume-size 1
automatically selected personal organization: Leo Golubyev
Creating postgres cluster in organization personal
Creating app...
Setting secrets on app whitehatseotactics-db...
Provisioning 1 of 1 machines with image flyio/postgres-flex:16.4@sha256:f107dbfaa732063b31ee94aa728c4f5648a672259fd62bfaa245f9b7a53b5479
Error: failed to create volume: failed to create volume: internal: failed to get app: sql: no rows in result set (Request ID: 01JDME0B84HCZY8XFTERBQ09PS-mad)
file:///home/rootall/.local/share/wasp-lang/0.15.2/data/packages/deploy/node_modules/zx/build/core.js:146
            let output = new ProcessOutput(code, signal, stdout, stderr, combined, message);
                         ^

ProcessOutput [Error]: automatically selected personal organization: Leo Golubyev
Error: failed to create volume: failed to create volume: internal: failed to get app: sql: no rows in result set (Request ID: 01JDME0B84HCZY8XFTERBQ09PS-mad)
    at FlyCommand.createDb (file:///home/rootall/.local/share/wasp-lang/0.15.2/data/packages/deploy/dist/providers/fly/createDb/createDb.js:28:13)
    exit code: 1
    at ChildProcess.<anonymous> (file:///home/rootall/.local/share/wasp-lang/0.15.2/data/packages/deploy/node_modules/zx/build/core.js:146:26)
    at ChildProcess.emit (node:events:517:28)
    at maybeClose (node:internal/child_process:1098:16)
    at ChildProcess._handle.onexit (node:internal/child_process:303:5)
    at Process.callbackTrampoline (node:internal/async_hooks:128:17) {
  _code: 1,
  _signal: null,
  _stdout: 'Creating postgres cluster in organization personal\n' +
    'Creating app...\n' +
    'Setting secrets on app whitehatseotactics-db...\n' +
    'Provisioning 1 of 1 machines with image flyio/postgres-flex:16.4@sha256:f107dbfaa732063b31ee94aa728c4f5648a672259fd62bfaa245f9b7a53b5479\n',
  _stderr: 'automatically selected personal organization: Leo Golubyev\n' +
    'Error: failed to create volume: failed to create volume: internal: failed to get app: sql: no rows in result set (Request ID: 01JDME0B84HCZY8XFTERBQ09PS-mad)\n',
  _combined: 'automatically selected personal organization: Leo Golubyev\n' +
    'Creating postgres cluster in organization personal\n' +
    'Creating app...\n' +
    'Setting secrets on app whitehatseotactics-db...\n' +
    'Provisioning 1 of 1 machines with image flyio/postgres-flex:16.4@sha256:f107dbfaa732063b31ee94aa728c4f5648a672259fd62bfaa245f9b7a53b5479\n' +
    'Error: failed to create volume: failed to create volume: internal: failed to get app: sql: no rows in result set (Request ID: 01JDME0B84HCZY8XFTERBQ09PS-mad)\n'
}

Node.js v18.20.4


❌ --- [Error] Deploy command failed: ---------------------------------------------

Deploy command failed with exit code: 1
rootall@Nerox-LpTp:~/apps/WhiteHatSeoTactics/app$

rootall@Nerox-LpTp:~/apps/WhiteHatSeoTactics/app$    fly apps destroy whitehatseotactics-db
 Destroying an app is not reversible.
? Destroy app whitehatseotactics-db? Yes
Destroyed app whitehatseotactics-db
rootall@Nerox-LpTp:~/apps/WhiteHatSeoTactics/app$ wasp deploy fly create-db iad
$ flyctl version
flyctl v0.3.41 linux/amd64 Commit: b983a0d0b98cf771c58d1ecb998097e641c2fb7b BuildDate: 2024-11-25T17:17:41Z
$ flyctl auth whoami
[email protected]
🚀  Creating your DB on Fly.io! 
$ flyctl postgres create --name whitehatseotactics-db --region iad --vm-size shared-cpu-1x --initial-cluster-size 1 --volume-size 1
automatically selected personal organization: Leo Golubyev
Creating postgres cluster in organization personal
Creating app...
Setting secrets on app whitehatseotactics-db...
Provisioning 1 of 1 machines with image flyio/postgres-flex:16.4@sha256:f107dbfaa732063b31ee94aa728c4f5648a672259fd62bfaa245f9b7a53b5479
Error: failed to create volume: failed to create volume: internal: failed to get app: sql: no rows in result set (Request ID: 01JDME0B84HCZY8XFTERBQ09PS-mad)
file:///home/rootall/.local/share/wasp-lang/0.15.2/data/packages/deploy/node_modules/zx/build/core.js:146
            let output = new ProcessOutput(code, signal, stdout, stderr, combined, message);
                         ^

ProcessOutput [Error]: automatically selected personal organization: Leo Golubyev
Error: failed to create volume: failed to create volume: internal: failed to get app: sql: no rows in result set (Request ID: 01JDME0B84HCZY8XFTERBQ09PS-mad)
    at FlyCommand.createDb (file:///home/rootall/.local/share/wasp-lang/0.15.2/data/packages/deploy/dist/providers/fly/createDb/createDb.js:28:13)
    exit code: 1
    at ChildProcess.<anonymous> (file:///home/rootall/.local/share/wasp-lang/0.15.2/data/packages/deploy/node_modules/zx/build/core.js:146:26)
    at ChildProcess.emit (node:events:517:28)
    at maybeClose (node:internal/child_process:1098:16)
    at ChildProcess._handle.onexit (node:internal/child_process:303:5)
    at Process.callbackTrampoline (node:internal/async_hooks:128:17) {
  _code: 1,
  _signal: null,
  _stdout: 'Creating postgres cluster in organization personal\n' +
    'Creating app...\n' +
    'Setting secrets on app whitehatseotactics-db...\n' +
    'Provisioning 1 of 1 machines with image flyio/postgres-flex:16.4@sha256:f107dbfaa732063b31ee94aa728c4f5648a672259fd62bfaa245f9b7a53b5479\n',
  _stderr: 'automatically selected personal organization: Leo Golubyev\n' +
    'Error: failed to create volume: failed to create volume: internal: failed to get app: sql: no rows in result set (Request ID: 01JDME0B84HCZY8XFTERBQ09PS-mad)\n',
  _combined: 'automatically selected personal organization: Leo Golubyev\n' +
    'Creating postgres cluster in organization personal\n' +
    'Creating app...\n' +
    'Setting secrets on app whitehatseotactics-db...\n' +
    'Provisioning 1 of 1 machines with image flyio/postgres-flex:16.4@sha256:f107dbfaa732063b31ee94aa728c4f5648a672259fd62bfaa245f9b7a53b5479\n' +
    'Error: failed to create volume: failed to create volume: internal: failed to get app: sql: no rows in result set (Request ID: 01JDME0B84HCZY8XFTERBQ09PS-mad)\n'
}

Node.js v18.20.4


❌ --- [Error] Deploy command failed: ---------------------------------------------

Deploy command failed with exit code: 1
rootall@Nerox-LpTp:~/apps/WhiteHatSeoTactics/app$

kapa.ai•4w ago

Let me check the knowledge base for you again. One moment! :books: ---------------------- I apologize for the persistent error you're encountering while trying to create a Postgres database for your Wasp application on Fly.io. It seems that despite destroying the previous app and trying to create a new one, you're still facing the same issue. Given the repeated nature of this error, it appears to be a problem on Fly.io's side rather than with your Wasp configuration. Here are a few suggestions to try: 1. Check Fly.io status: Visit the Fly.io status page (https://status.fly.io/) to see if there are any ongoing issues that might be affecting database creation. 2. Try a different region: Instead of iad, try a different region. You can list available regions with:

   fly platform regions

   fly platform regions

Then try creating the database in a different region, for example:

   wasp deploy fly create-db lax

   wasp deploy fly create-db lax

3. Verify your Fly.io account: Make sure your account is fully verified and there are no billing issues. Sometimes, resource creation can be restricted due to account-related problems. 4. Use Fly.io CLI directly: Try creating the database using the Fly.io CLI directly instead of through Wasp:

   fly postgres create --name whitehatseotactics-db --region iad --vm-size shared-cpu-1x --initial-cluster-size 1 --volume-size 1

   fly postgres create --name whitehatseotactics-db --region iad --vm-size shared-cpu-1x --initial-cluster-size 1 --volume-size 1

5. Contact Fly.io support: If none of the above steps work, it's time to reach out to Fly.io support directly. The error message "failed to get app: sql: no rows in result set" suggests an internal issue on their side. You can contact them through their support channels (https://fly.io/docs/about/support/) or community forums. 6. Consider alternative deployment options: If you continue to face issues with Fly.io, you might want to consider deploying your Wasp application to a different platform. The Wasp deployment documentation (https://wasp-lang.dev/docs/advanced/deployment/manually) provides information on other deployment methods you could explore. Remember, the Wasp community on Discord (https://discord.gg/rzdnErX) is also a great resource for troubleshooting deployment issues. They might have encountered similar problems and could provide more specific guidance based on their experiences. I apologize that you're still facing this issue. It seems to be a persistent problem with Fly.io's service at the moment, and reaching out to their support team might be the best next step. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @NEROX, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist: Perhaps try again in 15mins?

miho•4w ago

Fly might be having some issues? https://status.flyio.net/

Fly.io Status

Welcome to Fly.io's home for real-time and historical data on system performance.

NEROXOP•4w ago

that shi tragic😭 Solved, was fly issue

Gaming

Programming

Google oAuth: change server name by app name?