Open JasonWolf727 opened 4 years ago
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 local network or Windows system is blocking this port?
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 local network or Windows system is blocking this port?
I bet it'ss likely the case that the port is blocked; I'm a student at a somewhat small university, and they block a good amount of stuff. Does there happen to be a list of other good port choices to try? (And correct me if I'm wrong, is changing the port done in the config.cfg file?)
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 it's blocked try the OpenVPN port 1194
.
In
config.cfg
try changingssh_port
to22
(the SSH default), which they hopefully have not blocked.Edited to add: Hopefully they haven't blocked the WireGuard port of
51820
either. If it's blocked try the OpenVPN port1194
.
Ok; I tried changing the ssh_port to 22 and it sadly still didn't work. Then I thought to try installing while on a VPN; after all, maybe I could still connect through the WireGuard port after the installation finished. So I used a free vpn, and the installation went through successfully. (Once the installation finished I turned it off.)
I went to go test if it would connect to one of my users (my Windows 10 desktop) and installed WireGuard. I found the .conf for my desktop in the config folder for algo, and set it up in WireGuard. I tried activating it, which it did, went to my browser to test if I had internet, aaand..... nothing. Sadly, I think the WireGuard port must be blocked by my university as well (seriously, it's annoying how much they block).
Now, is there a way to edit the config to try the different WireGuard port you suggested earlier without having to destroy the droplet and install an entirely new one? And also, would you have any other suggestions that I could try out?
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 to use for WireGuard.
To change the WireGuard port, log in to the VPN server and change 51820
to your desired port in the following files:
/etc/iptables/rules.v4
/etc/iptables/rules.v6
/etc/wireguard/wg0.conf
Then reboot the server. After that change the port for the Endpoint
in the WireGuard app on your client(s).
As a last resort you can try port 53
, but that requires changes to more than just the files above so you should deploy a new server instead. This port might not work over a mobile data network.
As a last last resort you can deploy a server with ipsec_enabled: false
and try using the IPsec ports of 500
or 4500
. I can't recall anyone having tried this.
Don't forget to This only applies if you change the iptables rules by using the sudo netfilter-persistent save
after changing the iptables rules.sudo iptables -A...
and sudo ip6tables -A...
commands.
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
.
Had anyone tried tunneling UDP through TCP? This forum discusses it but I'm not sure how secure it is.
https://news.ycombinator.com/item?id=17846891
My work WiFi blocks UDP but OpenVPN works, which is TCP. I would rather use Wireguard though.
Operating System Windows 10
Describe the bug This bug occurs during the installation, and I'm not sure what this is. I've tried looking up solutions to the problem, but it only seems to have happened to Mac users.
To Reproduce Steps to reproduce the behavior:
Expected behavior Installation without any errors.
Additional context I attempted uninstalling Ubuntu and Python 3.8 and reinstalling (Python 3.7 to see if the Mac solution back in the day would work) as well as uninstalling as much of Algo as I could find to try and fix the problem. Sadly, it didn't make a difference.
Full log