Fly Machines: [error] Error 2: Internal problem

Questions / Help
1

I’m not able to expose any ports using Fly Machines, visiting the “exposed” port returns an ERR_EMPTY_RESPONSE and

proxy[677ebe30] ewr [error] Error 2: Internal problem

is logged for every request

2

For context: these machines have been booted using the GraphQL endpoint.

3

Oh, that’s a problem. The GraphQL endpoint was experimental, we need to disable it.

You’ll need to use this API to manage machines: Machines · Fly Docs

The proxy error might be related, we can debug it better if you create machines with that API and skip the GraphQL API.

4

Oh that might explain a lot of the weird issues I’ve been encountering with machines.
I’ll give the REST endpoint a try and update you on how it goes!

5

If you can delete all the existing machines (or the app that contains them), you should. That’s a good catch, that gql endpoint should not do anything anymore.

6

Yeah, will do. I’m assuming the GQL endpoint has been making bugged machines since I couldn’t attach volumes to them either and flyctl machines is unable to locate them.

7

On a sidenote, is there a way to pull WG creds over GQL? I’m trying to make this not depend on flyctl proxy.

8

Yes, something like:

mutation($input: AddWireGuardPeerInput!) {
  addWireGuardPeer(input: $input) {
    peerip
    endpointip
    pubkey
  }
}

Pub and private keys are created here in go: flyctl/wg.go at master · superfly/flyctl · GitHub