Closed dserodio closed 6 years ago
See #1002. There's a workaround suggested there which succeeded.
Probably a duplicate of https://github.com/trailofbits/algo/issues/1103
@jackivanov @TC1977 LOG.txt
@jackivanov @ TC1977 LOG.txt
所以你在#1002中尝试了解决方法吗?
yes i did it: new LOG.txt
If you need to reproduce the environment. I can give you the vps service password. and give me your e-mail
Well this is a local installation, so it’s not quite the same issue. The error says wg0 is already up. Can you simply sudo wg-quick down
and try again?
there is syntax error? can't run:
root@wireguardVpn:/home/wireguard/algo# sudo wg-quick down
Usage: wg-quick [ up | down | save | strip ] [ CONFIG_FILE | INTERFACE ]
CONFIG_FILE is a configuration file, whose filename is the interface name
followed by `.conf'. Otherwise, INTERFACE is an interface name, with
configuration found at /etc/wireguard/INTERFACE.conf. It is to be readable
by wg(8)'s `setconf' sub-command, with the exception of the following additions
to the [Interface] section, which are handled by wg-quick:
- Address: may be specified one or more times and contains one or more
IP addresses (with an optional CIDR mask) to be set for the interface.
- DNS: an optional DNS server to use while the device is up.
- MTU: an optional MTU for the interface; if unspecified, auto-calculated.
- Table: an optional routing table to which routes will be added; if
unspecified or `auto', the default table is used. If `off', no routes
are added.
- PreUp, PostUp, PreDown, PostDown: script snippets which will be executed
by bash(1) at the corresponding phases of the link, most commonly used
to configure DNS. The string `%i' is expanded to INTERFACE.
- SaveConfig: if set to `true', the configuration is saved from the current
state of the interface upon shutdown.
See wg-quick(8) for more info and examples.
Sorry, sudo wg-quick down wg0
. Then try to run ./algo
.
the same error message: new LOG 2.txt
That's not the same error message. You essentially finished, it just choked at the last part because you already had a directory there.
I think at least part of your problem is you're running ./algo
repeatedly on a local install, and it's running into the leftover remnants of the previous failed installs. Also I don't know if it makes a difference, but you're not in a virtualenv.
How about sudo wg-quick down wg0
, to turn Wireguard off again, sudo rm -r configs/localhost
to remove that directory, then source env/bin/activate
and the other commands listed in step 4, then ./algo
.
it's wrong😂. new LOG 3.txt
I don't know why you were trying to install a virtualenv on top of a virtualenv 😅 , but you almost made it all the way through. Now the error you're getting is in the troubleshooting guide, and definitely related to the debris from your previous installs. Remove the lock files, run ./algo again (from within the virtualenv) and hopefully you'll be home free.
Describe the bug
After provisioning a new Scaleway instance with algo, wireguard service won't start
To Reproduce
Steps to reproduce the behavior:
Run
./algo
script Choose 6 (Scaleway) provider Answer other prompts (wait some time for Ansible)Expected behavior
Ansible should've finished successfully
Full log