ljm42

Perplexing. Can you give me a link to the app in the Google Play store? And then the simplest set of steps you can think of for reproducing the problem?

This will be fixed in the next release, in the meantime here are the steps to resolve: https://forums.unraid.net/topic/129257-6111-vpn-tunnel-failing/page/2/#comment-1182737

@tetrapod @ercoppa @ChatNoir please see the fix here: https://forums.unraid.net/topic/129257-6111-vpn-tunnel-failing/page/2/#comment-1182737

@Autchirion And just like that we've got the fix https://forums.unraid.net/topic/129257-6111-vpn-tunnel-failing/page/2/#comment-1182737

@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.

Sorry, you are running into this bug: https://forums.unraid.net/topic/129257-6111-vpn-tunnel-failing/#comment-1181934 We're working on a fix for the next release

There are several threads about this, I've been responding in this one: https://forums.unraid.net/topic/129257-6111-vpn-tunnel-failing/#comment-1181934 I believe I have what we need to track down the issue and get it resolved in the next release. Thanks!

Hmm, the helptext is old. For better privacy we don't offer the www host on the myunraid.net domain. You can use the url that Unraid pre-fills, or you can use a url provided by another DDNS provider (one option - search Community Applications for "duckdns")

Don't feel bad, this is pretty advanced stuff. But I won't be able to give step by step. In general, I would say to setup two tunnels on each server, one for your phone/laptop/whatever and one for server to server communication. That will simplify things for you. Over here I have a guide on setting up LAN to LAN between two servers: https://forums.unraid.net/topic/88906-lan-to-lan-wireguard/ might be more than you are looking for but it should help.

On the first system - do the initial setup and add a peer for the second system and download the files On the second system - import the files you downloaded Whenever you make a change on the first system that results in a "Peer update required" message, you'll need to replicate those changes on the second system.

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

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

Just to clarify... Unraid 6.11.0 and 6.11.1 have Samba 4.17.0, and we expect the issue to be resolved with Samba 4.17.1 ?

Does it work if you choose one of the other peer options? If so, switch to advanced mode and see if there are any warnings/errors/required fields when you set it to "vpn tunneled access for system" If that doesn't help, 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. Hopefully there will be some clues.

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.

Thank you, this is the condition I was looking for. Would you please upload your diagnostics.zip file (from Tools -> Diagnostics). I need to try and replicate this.

The issue seems to be with this line in the code: https://github.com/limetech/webgui/blob/d196c027aa6fa49987773bf72d5859055a1321f4/plugins/dynamix/include/update.wireguard.php#L238 for some reason the `$device` variable is empty on some systems. I wrote a small script to isolate these variables: https://gist.github.com/ljm42/cc8bce83129cecbe148c09f0fbf6d3da If you are having this issue, please do the following to download and run that script: cd /tmp wget https://gist.githubusercontent.com/ljm42/cc8bce83129cecbe148c09f0fbf6d3da/raw/2e42e812d6946089b9443a94eada1ce637ae84b3/testnet.php php testnet.php My output looks like this: Array ( [DHCP_KEEPRESOLV] => no [DNS_SERVER1] => 192.168.10.1 [DHCP6_KEEPRESOLV] => no [BONDING] => no [BONDNAME] => [BONDNICS] => [BONDING_MODE] => 1 [BONDING_MIIMON] => 100 [BRIDGING] => yes [BRNAME] => br0 [BRNICS] => eth0 [BRSTP] => no [BRFD] => 0 [DESCRIPTION:0] => [PROTOCOL:0] => ipv4 [USE_DHCP:0] => yes [IPADDR:0] => 192.168.10.50 [NETMASK:0] => 255.255.255.0 [GATEWAY:0] => 192.168.10.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: 'no' BONDNAME: '' ethX: 'eth0' device: 'br0' If at the end you see "device: 'br0'" (or 'eth0' or some other value) that means everything is working correctly and I would not expect you to have the issue being discussed here. But if you have the issue being discussed then the device variable at the end is probably blank (i.e. you see something like "device: ''") Please copy/paste the whole output here so we can figure out why.

I renamed the post in the hopes that someone else with more experience in this will look at it.

Glad your ISP was able to confirm this. There isn't really anything we can do to help when the ISP is blocking your port forward.

It sounds like Remote Access is no longer configured, here are instructions for setting it up: https://wiki.unraid.net/My_Servers#Configuring_Remote_Access_.28optional.29

please see the discussion here https://forums.unraid.net/topic/126124-cannot-provision-ca-signed-certificate-fixed-briefly-currently-broken-again-multiple-weeks/page/2/#comment-1181483

Sorry for the trouble, please see the discussion here https://forums.unraid.net/topic/126124-cannot-provision-ca-signed-certificate-fixed-briefly-currently-broken-again-multiple-weeks/page/2/#comment-1181483

Sorry for the trouble, please see the discussion here https://forums.unraid.net/topic/126124-cannot-provision-ca-signed-certificate-fixed-briefly-currently-broken-again-multiple-weeks/page/2/#comment-1181483

Hi folks, Sorry for the trouble, we had some database issues that took a bit to track down. Things are back up and running now, but if you continue to have problems please post a note here shortly after attempting to provision and we'll check the logs around that time.

Exactly what url are you trying to use? According to your diagnostics, the webgui is configured on these ports: HTTP port: 80 HTTPS port: 443 You should be able to access it on these urls: https://192.168.0.21 https://RizznetUnraid.local https://hash.unraid.net <-- replace with your personal hash