[6.11.1] VPN Tunnel Failing

[ljm42]

3 hours ago, beasthouse said:

I am getting the same issue as @x86intel - I followed what @erak had done and now my toggle bounces back to `inactive` when I attempt to set it to `active`.

 

Output of the script below:

 

```
root@Odin:/tmp# php testnet.php
Array
(
    [DHCP_KEEPRESOLV] => yes
    [DNS_SERVER1] => 10.0.0.1
    [DNS_SERVER2] => 8.8.8.8
    [DNS_SERVER3] => 
    [DHCP6_KEEPRESOLV] => no
    [BONDING] => yes
    [BONDNAME] => bond0
    [BONDNICS] => eth0,eth1
    [BONDING_MODE] => 1
    [BONDING_MIIMON] => 100
    [BRIDGING] => yes
    [BRNAME] => br0
    [BRNICS] => bond0
    [BRSTP] => no
    [BRFD] => 0
    [DESCRIPTION:0] => 
    [PROTOCOL:0] => ipv4
    [USE_DHCP:0] => no
    [IPADDR:0] => 10.0.0.10
    [NETMASK:0] => 255.255.255.0
    [GATEWAY:0] => 10.0.0.1
    [METRIC:0] => 
    [USE_DHCP6:0] => yes
    [IPADDR6:0] => 
    [NETMASK6:0] => 
    [GATEWAY6:0] => 
    [METRIC6:0] => 
    [PRIVACY6:0] => 
    [MTU] => 
    [TYPE] => access
)
BRIDGING: 'yes'
BRNAME: 'br0'
BONDING: 'yes'
BONDNAME: 'bond0'
ethX: 'eth0'
device: 'br0'
```
 

 

You are not having the same issue.

 

Open a web terminal and type:

rm /var/log/wg-quick.log

 

Then go to Settings -> VPN Manager, make a change and hit save. This will undo any manual customizations you made. Then try starting the tunnel.

 

Back in the web terminal, type:

cat /var/log/wg-quick.log

 

and copy/paste the results back here.

[beasthouse]

5 hours ago, ljm42 said:

 

You are not having the same issue.

 

Open a web terminal and type:

rm /var/log/wg-quick.log

 

Then go to Settings -> VPN Manager, make a change and hit save. This will undo any manual customizations you made. Then try starting the tunnel.

 

Back in the web terminal, type:

cat /var/log/wg-quick.log

 

and copy/paste the results back here.

 

edit: I was able to get something working by setting the DNS in Peer Settings and on the Client to 1.1.1.1, then tried my PiHole IP, and that works too. It was 10.253.0.1 that was not working. 

 

root@Odin:~# rm /var/log/wg-quick.log
root@Odin:~# cat /var/log/wg-quick.log
wg-quick down wg0
[#] ip link delete dev wg0
[#] logger -t wireguard 'Tunnel WireGuard-wg0 stopped'
[#] iptables -t nat -D POSTROUTING -s 10.253.0.0/24 -o br0 -j MASQUERADE
[#] ip -4 route flush table 200
[#] ip -4 route add unreachable default table 200
[#] ip -4 route add 10.0.0.0/24 via 10.0.0.1 dev br0 table 200

wg-quick up wg0
[#] ip link add wg0 type wireguard
[#] wg setconf wg0 /dev/fd/63
[#] ip -4 address add 10.253.0.1 dev wg0
[#] ip link set mtu 1420 up dev wg0
[#] ip -4 route add 10.253.0.2/32 dev wg0
[#] logger -t wireguard 'Tunnel WireGuard-wg0 started'
[#] iptables -t nat -A POSTROUTING -s 10.253.0.0/24 -o br0 -j MASQUERADE
[#] ip -4 route flush table 200
[#] ip -4 route add default via 10.253.0.1 dev wg0 table 200
[#] ip -4 route add 10.0.0.0/24 via 10.0.0.1 dev br0 table 200

Edited October 19, 2022 by beasthouse

[ljm42]

3 minutes ago, beasthouse said:

 

 

root@Odin:~# rm /var/log/wg-quick.log
root@Odin:~# cat /var/log/wg-quick.log
wg-quick down wg0
[#] ip link delete dev wg0
[#] logger -t wireguard 'Tunnel WireGuard-wg0 stopped'
[#] iptables -t nat -D POSTROUTING -s 10.253.0.0/24 -o br0 -j MASQUERADE
[#] ip -4 route flush table 200
[#] ip -4 route add unreachable default table 200
[#] ip -4 route add 10.0.0.0/24 via 10.0.0.1 dev br0 table 200

wg-quick up wg0
[#] ip link add wg0 type wireguard
[#] wg setconf wg0 /dev/fd/63
[#] ip -4 address add 10.253.0.1 dev wg0
[#] ip link set mtu 1420 up dev wg0
[#] ip -4 route add 10.253.0.2/32 dev wg0
[#] logger -t wireguard 'Tunnel WireGuard-wg0 started'
[#] iptables -t nat -A POSTROUTING -s 10.253.0.0/24 -o br0 -j MASQUERADE
[#] ip -4 route flush table 200
[#] ip -4 route add default via 10.253.0.1 dev wg0 table 200
[#] ip -4 route add 10.0.0.0/24 via 10.0.0.1 dev br0 table 200

 

I don't see any issues there at all. Can you describe the problem you are having in detail?

 

[beasthouse]

27 minutes ago, ljm42 said:

 

I don't see any issues there at all. Can you describe the problem you are having in detail?

 

I was able to get something working by setting the DNS in Peer Settings and on the Client to 1.1.1.1, then tried my PiHole IP, and that works too. It was 10.253.0.1 that was not working. 

 

Issue I had in detail:

After upgrade to UNRAID 6.11, Wireguard stopped working. I had followed all advice I could find but none of it worked. What did work was changing the DNS address.

[aqua]

@ljm42I was getting the slider turning itself off automatically also. I managed to get it working by deleting the dev and dev wg0 instances in the config file, but the output from my running of the testnet.php script is below (and I have attached the diagnostics file). I also have a weird issue with deleting files from some android apps over SMB since updating from 6.9.2 and I'd love for these to be the same issue and resolved together, but likely not...

 

root@Tower:/tmp# php testnet.php

Array
(
    [DHCP_KEEPRESOLV] => no
    [DNS_SERVER1] => 208.67.222.222
    [DNS_SERVER2] => 1.1.1.1
    [DHCP6_KEEPRESOLV] => no
    [BONDING] => yes
    [BONDNAME] => 
    [BONDNICS] => eth0,eth1,eth2,eth3
    [BONDING_MODE] => 1
    [BONDING_MIIMON] => 100
    [BRIDGING] => yes
    [BRNAME] => 
    [BRNICS] => bond0
    [BRSTP] => 0
    [BRFD] => 0
    [DESCRIPTION:0] => 
    [PROTOCOL:0] => 
    [USE_DHCP:0] => yes
    [IPADDR:0] => 192.168.1.5
    [NETMASK:0] => 255.255.255.0
    [GATEWAY:0] => 192.168.1.1
    [METRIC:0] => 
    [USE_DHCP6:0] => 
    [IPADDR6:0] => 
    [NETMASK6:0] => 
    [GATEWAY6:0] => 
    [METRIC6:0] => 
    [PRIVACY6:0] => 
    [MTU] => 
    [TYPE] => access
)
BRIDGING: 'yes'
BRNAME: ''
BONDING: 'yes'
BONDNAME: ''
ethX: 'eth0'
device: ''
HEY dev is empty!

tower-diagnostics-20221019-2209.zip

Edited October 20, 2022 by aqua

[ljm42]

11 hours ago, aqua said:

@ljm42I was getting the slider turning itself off automatically also. I managed to get it working by deleting the dev and dev wg0 instances in the config file, but the output from my running of the testnet.php script is below (and I have attached the diagnostics file). I also have a weird issue with deleting files from some android apps over SMB since updating from 6.9.2 and I'd love for these to be the same issue and resolved together, but likely not...

 

root@Tower:/tmp# php testnet.php

Array
(
    [DHCP_KEEPRESOLV] => no
    [DNS_SERVER1] => 208.67.222.222
    [DNS_SERVER2] => 1.1.1.1
    [DHCP6_KEEPRESOLV] => no
    [BONDING] => yes
    [BONDNAME] => 
    [BONDNICS] => eth0,eth1,eth2,eth3
    [BONDING_MODE] => 1
    [BONDING_MIIMON] => 100
    [BRIDGING] => yes
    [BRNAME] => 
    [BRNICS] => bond0
    [BRSTP] => 0
    [BRFD] => 0
    [DESCRIPTION:0] => 
    [PROTOCOL:0] => 
    [USE_DHCP:0] => yes
    [IPADDR:0] => 192.168.1.5
    [NETMASK:0] => 255.255.255.0
    [GATEWAY:0] => 192.168.1.1
    [METRIC:0] => 
    [USE_DHCP6:0] => 
    [IPADDR6:0] => 
    [NETMASK6:0] => 
    [GATEWAY6:0] => 
    [METRIC6:0] => 
    [PRIVACY6:0] => 
    [MTU] => 
    [TYPE] => access
)
BRIDGING: 'yes'
BRNAME: ''
BONDING: 'yes'
BONDNAME: ''
ethX: 'eth0'
device: ''
HEY dev is empty!

tower-diagnostics-20221019-2209.zip 138.11 kB · 0 downloads

 

 

Thanks! This is definitely the problem we're chasing in this thread, and the diagnostics are helpful. 

[ljm42]

@b1ue @erak @chris smashe @AW139 @Klinkaroo @boardyuk @ZosoPage1963 @Quadrapole @x86intel @proteinart @aqua

 

Good news! We resolved the issue with the missing config values. This will be fixed automatically in the next release, but in the meantime here's what you can do:

• First, stop the array.
• Then navigate to Settings -> Network Settings and make any small change that makes the Apply button appear, then undo the change and hit Apply. This will rewrite your network config files and fill in the missing values.
• Then start the array.
• Finally, make a dummy change to each of your WireGuard configs to rewrite them with the new values (and undo-any manual changes you might have made)

At this point your WireGuard tunnels should start without issue.

 

 

If you continue to have problems, open a web terminal and type:

rm /var/log/wg-quick.log

then try to start the tunnel. Go back to the web terminal and type:

cat /var/log/wg-quick.log

and copy/paste the result back here.

[aqua]

Worked for me. Thanks.

[x86intel]

This worked for me as well. Thank you!

 

Previously, when I had the WireGuard issue, I turned off Unraid for the night; but few days later, I came back to boot the Unraid machine; and I noticed this on console startup:

 

------

 

I suspect some bad network config was persisted during my previous shutdown.

 

I was able to get WebUI working temporairly enough to get to the Settings > Network tab; and I did the following:

1. Unbonded the NICs; gave everything separate IPs

--- NIC/eth0 is the only port connected to LAN

--- NIC/eth1 was never really bonded at the begining (i dont recall, I left this network config as-is after fresh install); and also eth1 was never connected to LAN
--- applied settings

2. Rebonded the NICs; this time explicitly specifying eth0 + eth1

--- applied settings

3. This seemed to work.

 

and now I don't have the console startup error anymore:

--- Only thing I get now is RTNETLINK `Operation not supported` .... but that's fine by me. =)

 

 

Also, now I can confirm WireGuard is working (and no manual edits are necessary).

Edited October 21, 2022 by x86intel

[ljm42]

11 hours ago, x86intel said:

This worked for me as well. Thank you!

 

Previously, when I had the WireGuard issue, I turned off Unraid for the night; but few days later, I came back to boot the Unraid machine; and I noticed this on console startup:

 

------

 

I suspect some bad network config was persisted during my previous shutdown.

 

I was able to get WebUI working temporairly enough to get to the Settings > Network tab; and I did the following:

1. Unbonded the NICs; gave everything separate IPs

--- NIC/eth0 is the only port connected to LAN

--- NIC/eth1 was never really bonded at the begining (i dont recall, I left this network config as-is after fresh install); and also eth1 was never connected to LAN
--- applied settings

2. Rebonded the NICs; this time explicitly specifying eth0 + eth1

--- applied settings

3. This seemed to work.

 

and now I don't have the console startup error anymore:

--- Only thing I get now is RTNETLINK `Operation not supported` .... but that's fine by me. =)

 

 

Also, now I can confirm WireGuard is working (and no manual edits are necessary).

 

Good job working through that. I'd recommend making a backup of your flash drive in case it is starting to go bad, config files don't normally self destruct like that.

 

For anyone following along, another option is to delete the config/network.cfg file from the flash drive, when Unraid boots up it will generate a good starting point.

 

That RTNETLINK `Operation not supported` message is harmless

 

I am glad to hear your WireGuard is working again too  

[Quadrapole]

Wireguard still not working for me. 

I see that the toggle will stay active now, but I still can't tunnel to my unraid server.

My phone is transmitting and wants to handshake but my unraid server doesn't see anything and ping doesn't work. I don't get what's wrong.
 

When I run the quick log I see: 

 

wg-quick down wg0
[#] ip link delete dev wg0
[#] logger -t wireguard 'Tunnel WireGuard-wg0 stopped'
[#] iptables -t nat -D POSTROUTING -s 10.253.0.0/24 -o br0 -j MASQUERADE
[#] ip -4 route flush table 200
[#] ip -4 route add unreachable default table 200
[#] ip -4 route add 10.31.0.0/22 via 10.31.0.1 dev br0 table 200

wg-quick up wg0
[#] ip link add wg0 type wireguard
[#] wg setconf wg0 /dev/fd/63
[#] ip -4 address add 10.253.0.1 dev wg0
[#] ip link set mtu 1420 up dev wg0
[#] ip -4 route add 10.253.0.2/32 dev wg0
[#] logger -t wireguard 'Tunnel WireGuard-wg0 started'
[#] iptables -t nat -A POSTROUTING -s 10.253.0.0/24 -o br0 -j MASQUERADE
[#] ip -4 route flush table 200
[#] ip -4 route add default via 10.253.0.1 dev wg0 table 200
[#] ip -4 route add 10.31.0.0/22 via 10.31.0.1 dev br0 table 200

 

However handshake doesn't occur.


 

[Interface] #HomeVPN

PrivateKey=

Address=10.253.0.1

ListenPort=51820

PostUp=logger -t wireguard 'Tunnel WireGuard-wg0 started'

PostUp=iptables -t nat -A POSTROUTING -s 10.253.0.0/24 -o br0 -j MASQUERADE

PostDown=logger -t wireguard 'Tunnel WireGuard-wg0 stopped'

PostDown=iptables -t nat -D POSTROUTING -s 10.253.0.0/24 -o br0 -j MASQUERADE PostUp=ip -4 route flush table 200

PostUp=ip -4 route add default via 10.253.0.1 dev wg0 table 200

PostUp=ip -4 route add 10.31.0.0/22 via 10.31.0.1 dev br0 table 200

PostDown=ip -4 route flush table 200 PostDown=ip -4 route add unreachable default table 200

PostDown=ip -4 route add 10.31.0.0/22 via 10.31.0.1 dev br0 table 200

 

[Peer] #test

PublicKey=

PresharedKey=

AllowedIPs=10.253.0.2

 

[Interface] #alvas21

PrivateKey=

Address=10.253.0.2/32 DNS=192.168.1.254

 

[Peer] #HomeVPN

PresharedKey=

PublicKey=

Endpoint=test.duckdns.org:51820

AllowedIPs=0.0.0.0/0

Can someone please help?

 

[imagoodusername]

On 10/17/2022 at 2:06 PM, fabricionaweb said:

If I remove the `dev` from `wg0.conf` I can not turn active the vpn, it keeps under inactive state.

Removing both `dev wg0` I could at least turn wireguard on, but did not worked as well.

I have handshake and some lan connection but really nothing else works.

I can confirm it was working before upgrade in the really same configs.

-- edit

Ok I got mine to work and I did not need to change wg0.conf.

Im not sure what worked because I did many things, but there is two or three settings that I can suspect.

 

What I did:

- stopped the wireguard if it was running

- deleted some docker network like br0 and wg0

- stopped docker network

- disabled "Host access to custom networks" in Docker settings

- uncheck the "IPV4 Custom network on interface br0" yet in Docker settings
- reboot

 

My wg0.conf still have the `dev br0` and `dev wg0` but it is working now.

 

Thank you for posting this. I landed here on a Google search.

 

Yesterday I stupidly made a change to my wireguard setting to try to get remote access to a custom network through wireguard. The change crashed my entire server. Had to pull my USB drive and manually edit wg0.conf to delete my change just to get unRAID to boot again. Then I changed my docker settings to allow "Host access to custom networks" -- which allowed my two dockers to talk to one another (and for me to have wireguard access to the custom network docker) but it killed internet access for me.

 

My output on the githubusercontent showed that my issue was not the issue in the thread, but in fact solved by you mentioning "disabled 'Host access to custom networks' in Docker settings". Wireguard is working again. My adguardhome-sync dockers are no longer working after disabling "Host access to custom networks" -- but whatever, I can manually sync things if needed.

[CyberIntellience]

On 10/20/2022 at 3:18 PM, ljm42 said:

@b1ue @erak @chris smashe @AW139 @Klinkaroo @boardyuk @ZosoPage1963 @Quadrapole @x86intel @proteinart @aqua

 

Good news! We resolved the issue with the missing config values. This will be fixed automatically in the next release, but in the meantime here's what you can do:

• First, stop the array.
• Then navigate to Settings -> Network Settings and make any small change that makes the Apply button appear, then undo the change and hit Apply. This will rewrite your network config files and fill in the missing values.
• Then start the array.
• Finally, make a dummy change to each of your WireGuard configs to rewrite them with the new values (and undo-any manual changes you might have made)

At this point your WireGuard tunnels should start without issue.

 

 

If you continue to have problems, open a web terminal and type:

rm /var/log/wg-quick.log

then try to start the tunnel. Go back to the web terminal and type:

cat /var/log/wg-quick.log

and copy/paste the result back here.

 

These steps did not work for me. I'm currently using Unraid version 6.11.5. The network change I made was to my static ip, I switched it to a new one and after saving changes moved it back. For wireguard the change I made was to the port used, i then changed it back. To confirm there was nothing weird going on, after the first failure I restarted the entire unraid box.
 

wg-quick up wg0
[#] ip link add wg0 type wireguard
[#] wg setconf wg0 /dev/fd/63
Warning: AllowedIP has nonzero host part: 192.168.1.1/24
[#] ip -4 address add 10.253.0.1 dev wg0
[#] ip link set mtu 1420 up dev wg0
[#] ip -4 route add 10.253.0.3/32 dev wg0
[#] ip -4 route add 192.168.1.0/24 dev wg0
RTNETLINK answers: File exists
[#] ip link delete dev wg0

wg-quick down wg0
wg-quick: `wg0' is not a WireGuard interface

 

[ljm42]

56 minutes ago, CyberIntellience said:

Warning: AllowedIP has nonzero host part: 192.168.1.1/24

 

 

Where did 192.168.1.1/24 come from? It should be 192.168.1.0/24 (if you want the whole subnet) or 192.168.1.1/32 (if you want a single IP)

[CyberIntellience]

7 minutes ago, ljm42 said:

 

Where did 192.168.1.1/24 come from? It should be 192.168.1.0/24 (if you want the whole subnet) or 192.168.1.0/32 (if you want a single IP)

honestly no idea, I must have just been trying random things before I figured out that wireguard was just not working at all (i didn't even realize at first it was in the inactive state). I changed this and it appears to be working now. Although I'm not sure if this was the fix or the fact that I disabled access to macvlan in docker settings. I'll try re-enabling this docker feature and see if things break.

 

Now just need to figure out how to configure clients correctly so they have access to entire LAN. Seems access to pihole running on unraid (but with IPv4 from home router) isn't working just yet.

[ljm42]

24 minutes ago, CyberIntellience said:

Seems access to pihole running on unraid (but with IPv4 from home router) isn't working just yet.

 

You'll want to read the first two posts here:

  https://forums.unraid.net/topic/84226-wireguard-quickstart/

paying particular attention to the section titled "Complex networks"

 

[CyberIntellience]

On 11/28/2022 at 3:32 PM, ljm42 said:

 

You'll want to read the first two posts here:

  https://forums.unraid.net/topic/84226-wireguard-quickstart/

paying particular attention to the section titled "Complex networks"

 

 

Thanks. Looking at the instructions of "complex networks" it looks like I cannot use this wireguard plugin. There is a step that is specifically for configuring static routes on your router. There are instructions for pfsense (its nice these are included). Sadly I am using consumer grade, ISP provided hardware and cannot switch over to my own hardware at this time. As far as I could tell there was no option to configure static routes in it. Previously I used to have OPNSense back when I had a reliable WiFi AP, I used the built-in wireguard plugin for VPN which worked pretty well. I think I will try to spin up a VM or LXC container on another box with wireguard on it. Maybe I'll also move over pi-hole DNS server as well.

[ljm42]

13 hours ago, CyberIntellience said:

 

Thanks. Looking at the instructions of "complex networks" it looks like I cannot use this wireguard plugin. There is a step that is specifically for configuring static routes on your router. There are instructions for pfsense (its nice these are included). Sadly I am using consumer grade, ISP provided hardware and cannot switch over to my own hardware at this time. As far as I could tell there was no option to configure static routes in it. Previously I used to have OPNSense back when I had a reliable WiFi AP, I used the built-in wireguard plugin for VPN which worked pretty well. I think I will try to spin up a VM or LXC container on another box with wireguard on it. Maybe I'll also move over pi-hole DNS server as well.

 

Yeah, it takes a bit of network magic to allow docker containers to run on their own IP, and WireGuard tunnels running on Unraid require help from your router to access them.

 

The ISP-provided routers I have used allowed static routes, maybe do a Google search for "[router name] static route" and see if anything comes up.

 

Otherwise, moving either WireGuard or the docker container that needs to run on its own IP to a different system will allow everything to work.

[CyberIntellience]

On 11/30/2022 at 8:06 AM, ljm42 said:

 

Yeah, it takes a bit of network magic to allow docker containers to run on their own IP, and WireGuard tunnels running on Unraid require help from your router to access them.

 

The ISP-provided routers I have used allowed static routes, maybe do a Google search for "[router name] static route" and see if anything comes up.

 

Otherwise, moving either WireGuard or the docker container that needs to run on its own IP to a different system will allow everything to work.

 

I did make a basic sanity online search as well as going through all the advanced settings page for my router/modem combo. Sadly nothing stood out. I feel like I now understand why the kubernetes team gave up on dockershim and no longer support docker. Docker's networking features are limited and "not great". Its fine for developer workstations and small scale isolated deployments (don't need to depend on non-docker deployed services), its not so good for more serious deployments. Docker mostly just gets in the way. The main good part about docker is building apps, push docker images to dockerhub(s), and finding pre-built images (on dockerhub) is easy. I've been using docker regularly since about 2014 at work. I use LXC containers in proxmox and you can have as many network interfaces as you want attached to a single container. The annoying part of LXC is there is no real ecosystem of pre-built and well-tested images like there is for docker...

[The Transplant]

I am having the same issue on 6.11.5 - clean install of Wireguard.  Wireguard starts up and shutdowns immediately.  I tried the resolution steps above but no luck.  I assume all of the 0.0.0.0's below are not good?

 

2022-12-31T19:53:56.216Z Server Listening on http://0.0.0.0:51821
Error: WG_HOST Environment Variable Not Set!
    at /app/lib/WireGuard.js:34:17
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
2022-12-31T19:54:03.037Z Server Listening on http://0.0.0.0:51821
Error: WG_HOST Environment Variable Not Set!
    at /app/lib/WireGuard.js:34:17
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
2022-12-31T19:55:35.896Z Server Listening on http://0.0.0.0:51821
Error: WG_HOST Environment Variable Not Set!
    at /app/lib/WireGuard.js:34:17
    at processTicksAndRejections (internal/process/task_queues.js:95:5)

[ljm42]

On 12/31/2022 at 1:01 PM, The Transplant said:

Wireguard starts up and shutdowns immediately.

 

I need to see your your wg-quick.log, see my previous posts in this thread thread on how to get it

[The Transplant]

@ljm42

 

Here you go - log below.  I did search for this error but couldn't find anything that could point me in the right direction.  Thanks for helping.

 

2022-12-31T19:53:56.216Z Server Listening on http://0.0.0.0:51821
Error: WG_HOST Environment Variable Not Set!
    at /app/lib/WireGuard.js:34:17
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
2022-12-31T19:54:03.037Z Server Listening on http://0.0.0.0:51821
Error: WG_HOST Environment Variable Not Set!
    at /app/lib/WireGuard.js:34:17
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
2022-12-31T19:55:35.896Z Server Listening on http://0.0.0.0:51821
Error: WG_HOST Environment Variable Not Set!
    at /app/lib/WireGuard.js:34:17
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
2023-01-02T12:26:58.617Z Server Listening on http://0.0.0.0:51821
Error: WG_HOST Environment Variable Not Set!
    at /app/lib/WireGuard.js:34:17
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
2023-01-03T22:04:25.242Z Server Listening on http://0.0.0.0:51821
Error: WG_HOST Environment Variable Not Set!
    at /app/lib/WireGuard.js:34:17
    at processTicksAndRejections (internal/process/task_queues.js:95:5)

[ljm42]

1 hour ago, The Transplant said:

Here you go - log below.

 

To clarify, that is the contents of /var/log/wg-quick.log ?  I do not recognize that at all

[The Transplant]

Ha, it definitely was not that log.  I just clicked on the docker and logs.  My bad.  Here is the file you reference.  Apparently the fireguard config file is missing but since I don't (yet) no what I am doing I will leave the diagnosis up to those that do!

 

wg-quick down wg0

wg-quick: `/etc/wireguard/wg0.conf' does not exist

 

wg-quick down wg0

wg-quick: `wg0' is not a WireGuard interface

 

wg-quick down wg0

wg-quick: `wg0' is not a WireGuard interface

 

wg-quick down wg0

wg-quick: `wg0' is not a WireGuard interface

[ljm42]

On 1/3/2023 at 5:56 PM, The Transplant said:

I just clicked on the docker and logs

 

Unraid's WireGuard solution is not Docker based, although some community members have created Unraid containers as an alternative to the built-in solution.

 

If you would like to use Unraid's built-in WireGuard solution, start here: https://forums.unraid.net/topic/84226-wireguard-quickstart/