David Myers

Make sure you're not using the same WireGuard config file on both devices. Also, those traces look like the WireGuard tunnel was up. You should test the connection between your...

@DavidMyers Hey Dave, it's Dave. :smiley: Yes, it looks like the "e" was left out of a mention above.

It works for me running Tor Browser 9.0.2 on macOS 10.14.6 Mojave using WireGuard with the default MTU to an AlgoVPN on EC2 us-east-1.

>Can you confirm it's currently supported to ssh into the algo server and make these changes manually? The document [AlgoVPN and Firewalls](https://github.com/trailofbits/algo/blob/master/docs/firewalls.md) tells you where Algo stores its firewall rules,...

I think your DO API key is in that output. You should delete it and generate a new one.

@daehee Do you perhaps have non-standard versions of either `python` or `openssl` installed?

@daehee Those look correct. I'm not sure what's going on. I just deployed fine from a fresh 19.04 container. Do you get any output from the command `dpkg -V ca-certificates`?

I don't think `mtr` will be useful in figuring this out. If you're using WireGuard on your client you can eliminate MTU as the issue by setting the MTU to...

> If you're using WireGuard on your client you can eliminate MTU as the issue by setting the MTU to 1280 in the WireGuard client. Did you you try this?

It's not documented anywhere but this should work: ``` ./algo -e "ansible_ssh_port=22022" ```