Setting Up WireGuard® on Unraid


Recommended Posts

Thanks for the reply,
 
I've added a static route now on both configs -
STQICcK.png
 
Some improvements, but I still having some issues.
 
On the simple server -
I can now connect to the Unraid UI and to the pfsense UI. but I still can't access anything else on the network.
I've tried the firewall rules because of the firewall log:
 
I0OEbuu.png
(first one 192.168.0.31:8123 is the source, the 10.253.0.2 is the destination)
 
it looks like the remote device (the VPN peer) try to talk to the local service, but when the local service try to "take back" there's an issue.
 
on the complex server, it's basically the same + but I can't access the main UI as it forward automatically to the local domain (unraid.privateFQDN.org) and it stops there. dockers on the unraid server (using the IP address) connect perfectly.
 
 
Edit:
Found the fix the the issue, not sure why my config is causing it - but the scenario here is Asymmetric Routing.
The solution is to enable "Bypass firewall rules for traffic on the same interface" under System/Advanced/Firewall & NAT:
xJGqHNR.png
 
That fix both of the issues described above.

The gateway you created in pfsense for Unraid; what “interface” would that be? Can you share your gateway info for Unraid from pfSense, please?

016ef85772f11d99fc1d55ccc9346483.png
Link to comment
56 minutes ago, mark seaton said:

Ok I got access to my Unraid GUI remotely using remote access to server, but I don't see any of my shares on my server? am I missing some thing, do I need to port forward SMB or something as well?

 

If you chose "Remote access to server" then you need to connect to the server using the tunnel IP address as mentioned on the Wireguard settings page. You should see something like this:

 

image.png

 

So if the remote client is a Windows box you would go to the search bar and type:

  \\10.252.1.1

and Windows would use SMB to connect to that IP address. 

  • Like 1
Link to comment
17 hours ago, ljm42 said:

So if the remote client is a Windows box you would go to the search bar and type:

  \\10.252.1.1

and Windows would use SMB to connect to that IP address. 

So if my unraid server was 192.168.1.109 and a share on it was say movies then in windows i would use

 

\\192.168.1.109\movies

 

and I would have to do this for each of my shares on my Unraid box

 

I can also Map Network drive in windows correct?

 

is the reason for this because Wiregard is a silent VPN and does not allow SMB and NTF broadcasting?

 

Edited by mark seaton
Link to comment
9 minutes ago, mark seaton said:

So if my unraid server was 192.168.1.109 and a share on it was say movies then in windows i would use

 

\\192.168.1.109\movies

 

Is that the server's LAN address?

 

If you connected with "remote access to server", then you will not have access to the LAN IP address. You need to use the server's tunnel IP listed in the webgui

 

If you want to access the server's LAN address then choose "remote access to LAN" instead.

 

10 minutes ago, mark seaton said:

I can also Map Network drive in windows correct?

 

sure

 

10 minutes ago, mark seaton said:

is the reason for this because Wiregard is a silent VPN and does not allow SMB and NTF broadcasting?

 

It is related to DNS. See the "About DNS" portion of the first post here: https://forums.unraid.net/topic/84226-wireguard-quickstart/ 

 

Link to comment
On 7/21/2021 at 2:01 PM, ljm42 said:

 

Is that the server's LAN address?

 

If you connected with "remote access to server", then you will not have access to the LAN IP address. You need to use the server's tunnel IP listed in the webgui

 

If you want to access the server's LAN address then choose "remote access to LAN" instead.

I changed the connection to "remote access to Lan" and I still cant connect to the shares on my unraid server which has a LAN ip of 192.168.1.109, what am i missing?

 

Here is a screen shot of my settings, the blanked out is my duckdns

image.thumb.png.f900538c143e563fc16f7246460ab0d5.png

Link to comment
26 minutes ago, mark seaton said:

I changed the connection to "remote access to Lan" and I still cant connect to the shares on my unraid server which has a LAN ip of 192.168.1.109, what am i missing?

How are you accessing the server? You'll want do it by IP address \\192.168.1.109

 

26 minutes ago, mark seaton said:

Here is a screen shot of my settings, the blanked out is my duckdns

In the lower right corner it says "handshake not received". I don't think you are making a connection. I'd recommend starting over and going through the quickstart guide a step at a time.

 

As mentioned elsewhere, troubleshooting WireGuard is very tough because it fails silently. And all of the info someone would need to help you is private so you can't really share it.  The second post of the quickstart guide has a list of things for you to check.

  • Like 1
Link to comment

Hi,

 

I am also having difficulties connecting to my SMB shares via WireGuard. I did setup everything according to the steps descriped on the site of unraid and I am able to connect to my unraid server and browse the webgui, both from the tunneled IP (10.253.0.1) as the Internal IP address (192.168.1.254).

 

Whenever I try to connect to the SMB shares it simple gives me the message that it cant connect. I tried the following:

  1. Remote tunneling
  2. Remote access to server
  3. Remote access to LAN

Neither of these options give the direct access to the SMB shares of Unraid. I attached my current configuration, hopefully someone can help me out!

 

Thanks in advance!

 

WireGuard issue.png

Link to comment
3 hours ago, Rexl said:

Hi,

 

I am also having difficulties connecting to my SMB shares via WireGuard. I did setup everything according to the steps descriped on the site of unraid and I am able to connect to my unraid server and browse the webgui, both from the tunneled IP (10.253.0.1) as the Internal IP address (192.168.1.254).

 

Whenever I try to connect to the SMB shares it simple gives me the message that it cant connect. I tried the following:

  1. Remote tunneling
  2. Remote access to server
  3. Remote access to LAN

Neither of these options give the direct access to the SMB shares of Unraid. I attached my current configuration, hopefully someone can help me out!

 

Thanks in advance!

 

WireGuard issue.png

Got it to work with the help of this Reddit post: 

 

https://www.reddit.com/r/unRAID/comments/j676ce/wireguard_troubles_can_access_shares_from_phone/

 

Added the account reference via the account manager in Windows and everything worked like charm!

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.