failed to launch VM: machines are disabled for this organization

1

Hello!

I’m trying to deploy a simple Node.js app, but hen I try to deploy it I get the following messages:

✓ Configuration is valid
→ Verified app config
==> Building image
WARN Failed to start remote builder heartbeat: failed to launch VM: machines are disabled for this organization

==> Building image
WARN Failed to start remote builder heartbeat: failed to launch VM: machines are disabled for this organization

Error: failed to fetch an image or build from source: failed to launch VM: machines are disabled for this organization (Request ID: 01J6TZTVR2WMAYZK6GKA806X44-gru) (Trace ID: eb559d78a937ce46f217a754acdcf40d)

I have virtualization on in my machine, I use docker and VM’s. Can anyone help me ith that?

1 Like
2

Having the exact same issue.

3

@guedes-tech we require a credit card to launch machines, your organization does not currently have one added (I’ll look at getting this error message updated becuase it’s not at all clear that’s the problem).

@marrf is this is for your org named production-(redacted)? (if yes: I think this may be a bug in linked billing, talking about it internally right now)

2 Likes
4

Oh I see. Thank you for your answer.

I was trying to use the service to test it and I didn’t want to register a credit card. So there is no option to just make a simple node deploy without using the credit card?

5

Hi! Yes, its related with the production one.
I think it is because I had a pending payment. I payed it, then linked the organizations, however for some reason the payment did not go through. I think that’s why the linked billing is in a weird state.

(I only received today an email saying that the payment didn’t go through)

Anyway, just sent an email to the billing support to get this solved!

Thank you!

1 Like
6

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