David Myers

Algo moves the SSH port to `4160`. If you've used DigitalOcean before could you have set up a firewall that blocks this port? Or is it possible something on your...

In `config.cfg` try changing `ssh_port` to `22` (the SSH default), which they hopefully have not blocked. Edited to add: Hopefully they haven't blocked the WireGuard port of `51820` either. If...

Changing the WireGuard port after the fact is not terribly difficult, but if your network is blocking SSH I have a feeling it will be difficult to find a port...

> Don't forget to `sudo netfilter-persistent save` after changing the iptables rules. That will overwrite any changes made to `rules.v4` and `rules.v6`.

We've been wondering why we couldn't see Amazon reviews lately! I wouldn't have thought to try dropping the VPN, but sure enough that brings the reviews back. This is very...

I can see reviews again from my EC2 VPN.

There's something non-standard about this Ubuntu instance. In `TASK [common : Check apparmor support]` part of the output is `0 profiles are loaded`, which doesn't seem right. For example, on...

@zerkeizi I don't know why your instance of Ubuntu doesn't have AppArmor enabled, but Algo should still work. Try this: edit the file `roles/dns/defaults/main.yml` and delete the line `apparmor_enabled: true`.

Open an issue if you think it's not related to using OpenVZ. [This page](https://github.com/trailofbits/algo/blob/70f9f911124c8c942b42eac945fcada6e16767ef/docs/deploy-to-unsupported-cloud.md) says: > Hosting providers that rely on OpenVZ or Docker cannot be used by Algo since...

Please post the output from your installation attempt where it says: ``` --> Please include the following block of text when reporting issues: ```