Schema initialization failure/false start (v 1.1.0)

I collapsed the migration files as instructed [here](https://hasura.io/blog/resetting-hasura-migrations/) to create a set of "init" migration files. (I also have a freshly exported metadata.yaml file.)

```
$ tree migrations/
migrations/
├── 1584481060641_init
│ ├── up.sql
│ └── up.yaml
└── metadata.yaml
```

Next, I attempted applying this migration to a fresh Hasura deployment as follows:

```
$ hasura migrate apply --version 1584481060641 --endpoint {url}
```

On the first attempt, I received a FATA[0034] response as follows:

```
FATA[0034] apply failed: failed parsing json: invalid character '<' looking for beginning of value; response from API:

Application Error

html,body,iframe {
margin: 0;
padding: 0;
}
html,body {
height: 100%;
overflow: hidden;
}
iframe {
width: 100%;
height: 100%;
border: 0;
}






```

On a subsequent attempt I receive the following:

`FATA[0003] apply failed: Version already applied in database`

Visually examining the console, it appears that my schemas are in place, but this is not a rigorous audit. Is this a known issue related to #3983 or #4117?