Unable to connect to depot builder

i’ve been trying to deploy my app since the past few hours but the build is not able to connect to the depot builder, both locally and via gh actions

There’s a few solutions in this forum - just search for one of the log lines, and you’ll find some relevant posts.

i did try to go through those but none worked i deployed some of my services by using local builds but some cant be built locally and i need remote builders, moreover i also need it to be working in gh actions otherwise my ci/cd would be broken

Splendid, what specifically did you try? If you can outline the most promising one, readers can help you with that. As far as I know, the past solutions will work in pipelines too.

Ah, would you give more detail on that? That may be an important constraint that readers need to know about.

none felt promising but here are some i tried to go through:

not sure about whats the constraint but my local docker builds the nextjs app with no issues but when i try to build locally with fly deploy, it just wont, im stuck on the build step for the last 30 mins, it aint even that complex just 7 pages (no route handlers/server actions im running a separate backend server)

edit : my device is mac air m4 and i have a decent network bandwidth

Could you supply the command you’ve been using for this?

flyctl deploy \
            --build-secret NODE_ENV=production \
            --build-secret ALLOWED_ORIGINS=${{ secrets.ALLOWED_ORIGINS }} \
            --build-secret AUTH_SECRET=${{ secrets.AUTH_SECRET }} \
            --build-secret DATABASE_URL=${{ secrets.DATABASE_URL }} \
            --build-secret SMTP_HOST=${{ secrets.SMTP_HOST }} \
            --build-secret SMTP_PORT=${{ secrets.SMTP_PORT }} \
            --build-secret SMTP_USER=${{ secrets.SMTP_USER }} \
            --build-secret SMTP_PASSWORD=${{ secrets.SMTP_PASSWORD }} \
            --build-secret NEXT_PUBLIC_BASE_URL=${{ secrets.NEXT_PUBLIC_BASE_URL }} \
            --build-secret NEXT_PUBLIC_API_URL=${{ secrets.NEXT_PUBLIC_API_URL }} \
            --build-secret NEXT_PUBLIC_AUTH_URL=${{ secrets.NEXT_PUBLIC_AUTH_URL }} \
            --dockerfile apps/web/Dockerfile \
            --config apps/web/fly-preview.toml \
            --local-only

OK, this is good.

Your image of your CI config uses –remote-only, which likely uses Depot, and I assume that’s broken again. Could you try –local-only here again?

(If you can, try to get into the habit of supplying text for logs, errors, config, code, etc; readers may wish to copy a piece to clipboard, and they can’t very well do that if a bitmap has been supplied.)

Readers may need more information to go on here. Would you try adding --verbose to your local command?

—local-only worked in the CI, don’t mind me but i’d still like to leverage remote depot builders for no specific reasons here

mind if i ask where i did not pass the text? i shared both the image and text for the command u asked

You’ll have to wait out the storm.

so its an issue with depot/github thats causing connections errors?

I’m not 100% sure how depot works but it sounds like it’s related to GHA since that’s what they use to schedule the remote builders.

I’d say Depot breaks sufficiently enough for users to want to be aware of alternatives.

In general, the more information you can give, the more readers can help.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.