Unable to Build Images with fleex,

[chronograph3r]

I have a digital ocean account and been trying to build an image and try out the fleex utility

I have added the DO token in the config.yaml

I did not change anything on the config file, though it says

FATA[0008] POST https://api.digitalocean.com/v2/droplets: 422 (request "f1...") xxxx.d:6d:80 are invalid key identifiers for Droplet creation.

when I run fleex build -f build/common.yaml or Just fleex build

I am sure that my DO token is valid. I ensured that the password is meeting its requirement. What else am I missing?

[xm1k3]

Hi, have you correctly configured the other parameters in addition to the token?

Check https://sw33tlie.github.io/fleex-docs/get-started/config/ for more

Try with fleex build -p digitalocean

Let us know if problem persist

[chronograph3r]

hey @xm1k3 Yes, the issue still persist.

When I try to do a

➜ fleex config init FATA[0000] Fleex folder already exists, if you want to overwrite it use the --overwrite flag ➜ fleex config get - : <nil>

looks like it isn't fetching the configuration. what are the file permissions for the config.yaml file?

could you guide me in the right way? Thanks

Here is my config.yaml Stripped down comments

provider: digitalocean
# SSH keys in $HOME/.ssh/
public-ssh-file: id_rsa.pub
private-ssh-file: id_rsa
# Settings for Digitalocean provider
digitalocean:
  token: cf2x.................8c8
  region: blr1
  size: s-1vcpu-1gb
  image: ubuntu-20-04-x64
  port: 22
  username: op
  password: QwerTy123

[xm1k3]

https://github.com/sw33tLie/fleex/issues/8#issuecomment-888927196

Hi, check if the files id_rsa.pub and id_rsa are present in the $HOME/.ssh/ folder or use your public/private ssh key pairs.

if you don't have ssh key pair create one with:

ssh-keygen

Or follow this resources:

* [How to Set Up SSH Keys on Ubuntu 18.04](https://www.digitalocean.com/community/tutorials/how-to-set-up-ssh-keys-on-ubuntu-1804)

* [How To Set up SSH Keys on a Linux / Unix System](https://www.cyberciti.biz/faq/how-to-set-up-ssh-keys-on-linux-unix/)

Maybe the problem can be this, can you try it?

If this is the case, I'll manage the error from the code

[chronograph3r]

Hey @xm1k3 sorry for the Late responses. I have verified that the ssh keys are in place. also, if I can use the ssh key pair, why do i require to give a username and password?

[xm1k3]

Hi, that is strange, i will work on it again, i tried on different vps and worked, could be the token permissions?

Username and Password are also used to spawn custom VPS

[byt3hx]

I also have the same issue and I am 100% sure my DO token is valid