Connection problem on this 169.254.169.254 IP!

FleexSecurity / fleex

Fleex makes it easy to create multiple VPS on cloud providers and use them to distribute workloads.

https://fleexsecurity.github.io/fleex-docs/

Apache License 2.0

250 stars 30 forks source link

Connection problem on this 169.254.169.254 IP! #8

Open 0xhunster opened 3 years ago

0xhunster commented 3 years ago

xm1k3 commented 3 years ago

Hi, can you explain us more about the problem? are you using digitalocean as default provider? 169.254.169.254 is used for metadata in DO, you can't connect to it, if you want to see your Droplet metadata see this steps:

fleex ls to see droplets details

connect to the generated vps

fleex ssh -n pwn-1
OR
ssh op@IPV4 -p PORT

curl http://169.254.169.254/metadata/v1/ and see all your metadata about the droplet Response:

id
hostname
user-data
vendor-data
public-keys
region
interfaces/
dns/
floating_ip/
tags/
features/

Resources:

Let us know if everything is okay or if there are still problems

sw33tLie commented 3 years ago

Hi there, we just pushed a fix for this issue. I suppose you were attempting a fleex build and you were using Linode. Please update fleex by running GO111MODULE=on go get -v github.com/sw33tLie/fleex, then update your config files with a fleex config init --overwrite (so that your ~/fleex/build/common.yaml file will be updated).

Let us know if this works for you now :)

0xhunster commented 3 years ago

Hello, Sorry for the delay. Yes, I have to use Linode by default. fleex config init --overwrite not working! Then I delete fleex folder and reconfigure it via fleex config init. Then working :) Then I use fleex build command. Build properly does not show any error. Then when I use fleex images, I showed blank output. Then I used fleex ls as you can see? 20248

sw33tLie commented 3 years ago

Hey thanks for the new details. Just to make sure, you have put your token again in ~/fleex/config.yaml and adjusted the other values according to your needs, right?

0xhunster commented 3 years ago

xm1k3 commented 3 years ago

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: