W

Wasp•14mo ago

Prefix

fly deploy pointing to wrong server URL

I am trying to deploy a postgres + websockets Wasp app to Fly, following the deploy instructions here: https://wasp-lang.dev/docs/advanced/deployment/cli

App works correctly locally.

I ran: wasp deploy fly launch my-wasp-app miawasp deploy fly launch my-wasp-app mia

This created 3 apps:

• my-wasp-app-client-morning-feather-500
• my-wasp-app-server-broken-mountain-1141
• my-wasp-app-broken-mountain-1141-db

When I visit the client app URL, I see the Wasp loading spinner, however requests are failing:

• ERR_NAME_NOT_RESOLVEDERR_NAME_NOT_RESOLVED for request to https://my-wasp-app-morning-feather-500-server.fly.dev/auth/mehttps://my-wasp-app-morning-feather-500-server.fly.dev/auth/me
• socket requests are failing

Looking at the names, it looks like the client was given the incorrect server name? my-wasp-app-morning-feather-500-servermy-wasp-app-morning-feather-500-server but it should be my-wasp-app-server-broken-mountain-1141my-wasp-app-server-broken-mountain-1141.

This might have been an issue during the deploy, where the CLI timed out waiting for the apps to be available. I re-ran the command since the TOML files were correctly created assuming it would pick off where it left off, but not sure what happened.

1: is there a way to fix this?
2: is this a known issue?

Deploying with the Wasp CLI | Wasp

Wasp CLI can deploy your full-stack application with only a single command.