Wasp•3w ago

Fly (Deploy command failed with exit code: 1)

First time seeing this error:

==> Building image
Waiting for depot builder...

Error: failed to fetch an image or build from source: error building: timed out connecting to machine: failed to list workers: Unavailable: connection error: desc = "transport: authentication handshake failed: tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2024-12-06T00:01:50+01:00 is before 2024-12-06T09:53:13Z"
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);

==> Building image
Waiting for depot builder...

Error: failed to fetch an image or build from source: error building: timed out connecting to machine: failed to list workers: Unavailable: connection error: desc = "transport: authentication handshake failed: tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2024-12-06T00:01:50+01:00 is before 2024-12-06T09:53:13Z"
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);

7 Replies

kapa.ai•3w ago

Hi @NEROX. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave: ---------------------- Based on the error message you've provided, it appears you're encountering an issue while trying to deploy your Wasp application to Fly.io. The error suggests there's a problem with the TLS certificate used in the connection to Fly.io's build service. Unfortunately, the knowledge sources provided don't contain specific information about this particular error. However, I can offer some general advice based on similar deployment issues mentioned in the sources: 1. First, ensure you're using the latest version of Wasp. You can check your version by running wasp version and update if necessary using the command:

   curl -sSL <https://get.wasp-lang.dev/installer.sh> | sh -s

   curl -sSL <https://get.wasp-lang.dev/installer.sh> | sh -s

Wasp CLI deployment docs (https://wasp-lang.dev/docs/advanced/deployment/cli#building-locally) mention that keeping Wasp up-to-date can help avoid deployment issues. 2. If you're still encountering the error after updating, you might want to try building locally instead of using Fly.io's remote builder. You can do this by adding the --build-locally flag to your deployment command:

   wasp deploy fly deploy --build-locally

   wasp deploy fly deploy --build-locally

This approach is mentioned in the Wasp CLI deployment docs (https://wasp-lang.dev/docs/advanced/deployment/cli#building-locally) and might help bypass issues with Fly.io's remote builder. 3. If the problem persists, it might be related to Fly.io's infrastructure or temporary issues with their service. In such cases, you may want to reach out to Fly.io support or check their status page for any ongoing issues. 4. As a last resort, you could try removing all existing resources and starting the deployment from scratch, as mentioned in a GitHub issue comment (https://github.com/wasp-lang/wasp/issues/1498). However, this should be done cautiously as it will delete your existing deployment. If none of these suggestions help, I recommend reaching out to the Wasp community on Discord or opening an issue on the Wasp GitHub repository for more specific assistance with this error. ---------------------- 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•3w ago

Fly Status is all operational, yesterday I haven't that issue @kapa.ai How can I do re-auth in fly io console?

kapa.ai•3w ago

Let me check the knowledge base for you again. One moment! :books: ---------------------- To re-authenticate in the Fly.io console, you can use the flyctl command-line interface. Here's how you can do it: 1. Open your terminal or command prompt. 2. Run the following command:

   flyctl auth login

   flyctl auth login

This command will initiate the authentication process. It should open a web browser where you can log in to your Fly.io account. If it doesn't open automatically, the command will provide a URL that you can copy and paste into your browser. After successfully logging in through the browser, your terminal should show a confirmation message that you're authenticated. If you're already logged in and want to switch accounts, you can use:

flyctl auth logout

flyctl auth logout

followed by flyctl auth login to log in with a different account. It's worth noting that, as mentioned in the Fly.io deployment docs (https://wasp-lang.dev/docs/advanced/deployment/manually#flyio-server-and-database), you can check your current authentication status with:

flyctl auth whoami

flyctl auth whoami

This command will show you which account you're currently logged in with. Remember, keeping your authentication up-to-date is important for smooth deployments and management of your Wasp applications on Fly.io. ---------------------- 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•3w ago

Still struggling with the depot

NEROXOP•3w ago

Let's see if I get any news https://community.fly.io/t/waiting-for-depot-builder/22939/2

NEROXOP•3w ago

✅ Fixed, just had the time unsynchronized

martinsos•3w ago

Oh wow 😄

Gaming

Programming

Fly (Deploy command failed with exit code: 1)