You most likely did not open the port on the node, also you need to ensure all the traffic on the node is running threw the vps, this is where I have noticed most people make their mistake.
Failed to start wg-quick@wg0.service - WireGuard via wg-quick(8) for wg0. Also, all you posted is systemd is complaining about it but nothing in that post of why it’s down.
In experience that’s usually an issue with the file wg0.conf but let’s take a look.
Run this and paste out the problems back here and not the whole output. Red and yellow alerts
sudo systemctl status wg-quick@wg0.service --no-pager -l
sudo journalctl -xeu wg-quick@wg0.service --no-pager
sudo wg-quick up wg0
Checking configuration:
Info: rpt.conf has configuration for: 688580
Info: /etc/asterisk/iax.conf contains no registration lines.
Info: /etc/asterisk/rpt_http_registrations.conf contains 1 registration line(s)
Info: Registrations present for configured node(s): 688580
Warning: IP test to https://conntest-east1.allstarlink.org/ip failed
Warning: IP test to https://conntest-west1.allstarlink.org/ip failed
Warning: IP test to https://conntest-west2.allstarlink.org/ip failed
Warning: IP test to udp://conntest-east1.allstarlink.org:4570 failed
Info: IP from udp://conntest-west1.allstarlink.org:4569 reports: 44.27.133.126
Info: IP from udp://conntest-west2.allstarlink.org:4569 reports: 44.27.133.126
Error: HTTP IP probes DO NOT have consensus on the same perceived IP! CGNAT?
OK: IAX IP probes have consensus on the same perceived IP
Testing node 688580:
OK: Node registration config is well-formed
OK: Node registration type is HTTP
Error: register.allstarlink.org is unreachable (via HTTP)
Error: HTTP registration state is Not Registered
Info: Stopping node checks due to registration failure
Info: as further information will be unreliable
Something with your configuration is incorrect and your Wireguard tunnel isn't passing traffic properly. I'd suggest re-checking every step of your Wireguard setup.
Unfortunately, this is where my skill set starts to show its limits. I could go through the installation steps again, or are there other places to check?
‘4: wg0: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1380 qdisc noqueue state UNKNOWN group default qlen 1000
link/none
inet 44.27.133.126/32 scope global wg0
valid_lft forever preferred_lft forever
inet6 fe80::2cde:576a:904f:d72c/128 scope link
valid_lft forever preferred_lft forever’
ip rule show
‘0: from all lookup local
32764: from all lookup main suppress_prefixlength 0
32765: not from all fwmark 0xca6c lookup 51820
32766: from all lookup main
32767: from all lookup default’
It tells you that your configuration network-wise is correct. That leaves either a problem with the keys being mis-entered or your have a network problem reaching the 44Net Connect head end. Look at each keypair and compare it with what was in the 44Net portal.
