Open TarekSalama opened 4 years ago
I'm having the same issue as well, tried:
Neither thing seems to work
I can recreate this. @jackivanov It looks like cloud-init/base.sh
is not being run.
I'm getting the same error on a freshly created Hetzner CX11 running Ubuntu 20.04. I cloned the repo with git. Retry on another new vps of same the type also failed.
Retried once more with default config, also fails.
also having the same error, but attempting to run on an EC2 on region east-us-1
Would anyone please be so kind to open this issue again and give a comment? According to the docs Hetzner cloud is a supported provider and I followed the all steps as described in the docs . TNX
When using advanced setup with Ubuntu 20.04 on the same server, the playbook hangs at:
TASK [debug] ** ok: [localhost] => { "IP_subject_alt_name":
I can confirm that the issue still exists. No luck with provisioning Hetzner cloud instances (CX11). My server there is running Ubuntu 20.04. Is there any known workaround that could be applied?
I can also confirm this issue still exists on master branch (728b8aae0637a4f3d8374782c4d9426e3b3ef177):
I had previously installed AlgoVPN and it ran fine, but had to change my trusted servers recently.
Errors:
TASK [Additional variables for the server]
changed: [localhost]
TASK [Wait until SSH becomes ready...]
***
fatal: [localhost]: FAILED! => {"changed": false, "elapsed": 321, "msg": "Timeout when waiting for search string OpenSSH in
TASK [Fail the installation]
***
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Failed as requested from task"}
I'm guessing something changed on AWS, as I tried the version I used previously 060b4018801f17b87c9c7997cf8367f346de8390 and it also fails.
Can someone test Amazon Lightsail to isolate the issue? Thanks!
I was able to get this working again by selecting "yes" for...
[SSH tunneling prompt]
Do you want each user to have their own account for SSH tunneling?
[y/N]
I previously had only one user listed in config.cfg but this time added two users.
I was able to get this working again by selecting "yes" for...
[SSH tunneling prompt] Do you want each user to have their own account for SSH tunneling? [y/N]
I previously had only one user listed in config.cfg but this time added two users.
me too
I've encountered this issue (on this commit a103d8dd169beddb812863c9d77d5d7ce96d84e4) as well and have finally managed to solve it, hope this report helps someone in the future.
fatal: [localhost]: FAILED! => {"changed": false, "elapsed": 321, "msg": "Timeout when waiting for search string OpenSSH in ***.***.***.***:4160"}
y
for the SSH prompt. No luck either. Same error.
[SSH tunneling prompt]
Do you want each user to have their own account for SSH tunneling?
[y/N]
ufw disable
in https://github.com/trailofbits/algo/issues/14378. Still no luck. Same error.**.***.***.***:4160
is somewhat suspicious and looks like a VPC IP of DO. And that's when I finally found this https://github.com/trailofbits/algo/issues/14387 and this https://github.com/trailofbits/algo/issues/14420. Running ./algo -vvv
confirmed that this internal private IP is the first item of v4
list (only meaningful part of JSON left):
{
"data": {
"droplet": {
"networks": {
"v4": [
{
"gateway": "XXX.XXX.XXX.XXX",
"ip_address": "***.***.***.***",
"netmask": "255.255.0.0",
"type": "private"
},
{
"gateway": "XXX.XXX.XXX.XXX",
"ip_address": "+++.+++.+++.+++",
"netmask": "255.255.240.0",
"type": "public"
}
]
}
}
}
So, the +++.+++.+++.+++
IP should be used instead of ***.***.***.***
IP. We just need to make the algo use it. Fair enough, in the file ./roles/cloud-digitalocean/tasks/main.yml
in the set_fact
section change cloud_instance_ip
value from
cloud_instance_ip: "{{ digital_ocean_droplet.data.droplet.networks.v4.0.ip_address }}"
to
cloud_instance_ip: "{{ digital_ocean_droplet.data.droplet.networks.v4.1.ip_address }}"
That's it, we just need the 2nd item of the v4
list. After that everything works as expected. Hope it helps somebody.
Thank you @rozag, this worked for me today on Digital Ocean
@rozag thank you!!
@rozag Thank you very much, but i have such issues after those changes.
` **fatal: [localhost]: FAILED! => {"msg": "The task includes an option with an undefined variable. The error was: 'dict object' has no attribute 'droplet'\n\nThe error appears to be in '/Users/***/algo/roles/cloud-digitalocean/tasks/main.yml': line 46, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- set_fact:\n ^ here\n"}**
TASK [include_tasks] *** included: /Users/****/algo/playbooks/rescue.yml for localhost
TASK [debug] *** ok: [localhost] => { "fail_hint": [ "Sorry, but something went wrong!", "Please check the troubleshooting guide.", "https://trailofbits.github.io/algo/troubleshooting.html" ] }
TASK [Fail the installation] *** fatal: [localhost]: FAILED! => {"changed": false, "msg": "Failed as requested from task"} `
I can't get Algo to install on Vultr. This is my log.