peter_sm

What was the output of the command ? And can you see any files in easyRsa folder?

Try this /usr/local/emhttp/plugins/openvpnserver/scripts/rc.openvpnserver download_easy-rsa and post your /boot/config/plugins/openvpnserver/openvpnserver.cfg //Peter

You see that the directory doesn't exist ? Try move away from user share and use disk instead , maybe you didn't save settings?

Can you do this in a putty session /usr/local/emhttp/plugins/openvpnserver/scripts/rc.openvpnserver create_server_cert

Generate certs take a wile, did you also save "Server Config" so there are 3 green marker. //Peter

You are connecting your client to your WAN IP? if you are using iOS try the "inline file" :-) We have almost same settings, I have these that differ,see image. EDIT Added my router settings as well. //Peter

Can you attach your router settings (portforward) and server settings ? //Peter

Forward the port for Unraid IP.

Try to change machine to pc-0.14 some info here -> http://www.pandorawiki.org/QEMU#Installing_Microsoft_Windows_98

You must save the server settings , that one still have a red marking.

I have chosen to use LVM on my SSD to be used for my VM and docker, but I will take a look at this plugin....maybe LVM are a better choose than ZFS?

@LT This is for all pass trough I have, below show "error" on my USB controller passing trough to windows VM, would this be fixed in 6.2 ?? Dec 20 14:30:54 Tower kernel: vfio-pci 0000:00:1d.0: enabling device (0000 -> 0002) Dec 20 14:30:54 Tower kernel: vfio_cap_init: 0000:00:1d.0 hiding cap 0xa Dec 20 14:30:54 Tower kernel: vfio-pci 0000:02:00.1: enabling device (0400 -> 0402) Dec 20 14:30:56 Tower kernel: dmar: DRHD: handling fault status reg 3 Dec 20 14:30:56 Tower kernel: dmar: DMAR:[DMA Read] Request device [00:1d.0] fault addr ee000 Dec 20 14:30:56 Tower kernel: DMAR:[fault reason 06] PTE Read access is not set Dec 20 14:30:56 Tower kernel: kvm: zapping shadow pages for mmio generation wraparound Dec 20 14:37:29 Tower kernel: dmar: DRHD: handling fault status reg 3 Dec 20 14:37:29 Tower kernel: dmar: DMAR:[DMA Read] Request device [00:1d.0] fault addr ee000

Hi, I'm on version 6.1.6 and my syslog is full of these messages ,is this harmful ? or a kernel bug ? Its' for my GPU that I pass trough to a VM Dec 12 11:22:30 Tower kernel: dmar: DRHD: handling fault status reg 3 Dec 12 11:22:30 Tower kernel: dmar: DMAR:[DMA Read] Request device [02:00.0] fault addr f00485000 Dec 12 11:22:30 Tower kernel: DMAR:[fault reason 06] PTE Read access is not set Dec 12 11:22:30 Tower kernel: dmar: DRHD: handling fault status reg 3 Dec 12 11:22:30 Tower kernel: dmar: DMAR:[DMA Read] Request device [02:00.0] fault addr f00486000 Dec 12 11:22:30 Tower kernel: DMAR:[fault reason 06] PTE Read access is not set Dec 12 11:22:30 Tower kernel: dmar: DRHD: handling fault status reg 3 Dec 12 11:22:30 Tower kernel: dmar: DMAR:[DMA Read] Request device [02:00.0] fault addr f00488000 Dec 12 11:22:30 Tower kernel: DMAR:[fault reason 06] PTE Read access is not set Dec 12 11:22:30 Tower kernel: dmar: DRHD: handling fault status reg 3 Dec 12 11:22:30 Tower kernel: dmar: DMAR:[DMA Read] Request device [02:00.0] fault addr f00488000 Dec 12 11:22:30 Tower kernel: DMAR:[fault reason 06] PTE Read access is not set Dec 12 11:22:30 Tower kernel: dmar: DRHD: handling fault status reg 3 Dec 12 11:22:30 Tower kernel: dmar: DMAR:[DMA Read] Request device [02:00.0] fault addr f0048a000 Dec 12 11:22:30 Tower kernel: DMAR:[fault reason 06] PTE Read access is not set Dec 12 11:22:30 Tower kernel: dmar: DRHD: handling fault status reg 3 Dec 12 11:22:30 Tower kernel: dmar: DMAR:[DMA Read] Request device [02:00.0] fault addr f0048b000 Dec 12 11:22:30 Tower kernel: DMAR:[fault reason 06] PTE Read access is not set Dec 12 11:22:30 Tower kernel: dmar: DRHD: handling fault status reg 3 Dec 12 11:22:30 Tower kernel: dmar: DMAR:[DMA Read] Request device [02:00.0] fault addr f0048d000 Dec 12 11:22:30 Tower kernel: DMAR:[fault reason 06] PTE Read access is not set Dec 12 11:22:30 Tower kernel: dmar: DRHD: handling fault status reg 3 Dec 12 11:22:30 Tower kernel: dmar: DMAR:[DMA Read] Request device [02:00.0] fault addr f0048e000 Dec 12 11:22:30 Tower kernel: DMAR:[fault reason 06] PTE Read access is not set Dec 12 11:22:30 Tower kernel: dmar: DRHD: handling fault status reg 3 Dec 12 11:22:30 Tower kernel: dmar: DMAR:[DMA Read] Request device [02:00.0] fault addr f0048f000 Dec 12 11:22:30 Tower kernel: DMAR:[fault reason 06] PTE Read access is not set Dec 12 11:22:30 Tower kernel: dmar: DRHD: handling fault status reg 3 Dec 12 11:22:30 Tower kernel: dmar: DMAR:[DMA Read] Request device [02:00.0] fault addr f00490000 Dec 12 11:22:30 Tower kernel: DMAR:[fault reason 06] PTE Read access is not set Dec 12 11:22:30 Tower kernel: dmar: DRHD: handling fault status reg 3 Dec 12 11:22:30 Tower kernel: dmar: DMAR:[DMA Read] Request device [02:00.0] fault addr f00492000 Dec 12 11:22:30 Tower kernel: DMAR:[fault reason 06] PTE Read access is not set Dec 12 11:22:30 Tower kernel: dmar: DRHD: handling fault status reg 3 Dec 12 11:22:30 Tower kernel: dmar: DMAR:[DMA Read] Request device [02:00.0] fault addr f00493000 Dec 12 11:22:30 Tower kernel: DMAR:[fault reason 06] PTE Read access is not set Dec 12 11:22:30 Tower kernel: dmar: DRHD: handling fault status reg 3 Dec 12 11:22:30 Tower kernel: dmar: DMAR:[DMA Read] Request device [02:00.0] fault addr f00494000 Dec 12 11:22:30 Tower kernel: DMAR:[fault reason 06] PTE Read access is not set Dec 12 11:22:30 Tower kernel: dmar: DRHD: handling fault status reg 3 Dec 12 11:22:30 Tower kernel: dmar: DMAR:[DMA Read] Request device [02:00.0] fault addr f00495000 Dec 12 11:22:30 Tower kernel: DMAR:[fault reason 06] PTE Read access is not set Dec 12 11:22:30 Tower kernel: dmar: DRHD: handling fault status reg 3 Dec 12 11:22:30 Tower kernel: dmar: DMAR:[DMA Read] Request device [02:00.0] fault addr f00497000 Dec 12 11:22:30 Tower kernel: DMAR:[fault reason 06] PTE Read access is not set Dec 12 11:22:30 Tower kernel: dmar: DRHD: handling fault status reg 3 Dec 12 11:22:30 Tower kernel: dmar: DMAR:[DMA Read] Request device [02:00.0] fault addr f00498000 Dec 12 11:22:30 Tower kernel: DMAR:[fault reason 06] PTE Read access is not set Dec 12 11:22:30 Tower kernel: dmar: DRHD: handling fault status reg 3 Dec 12 11:22:30 Tower kernel: dmar: DMAR:[DMA Read] Request device [02:00.0] fault addr f00499000 Dec 12 11:22:30 Tower kernel: DMAR:[fault reason 06] PTE Read access is not set Dec 12 11:22:30 Tower kernel: dmar: DRHD: handling fault status reg 3 Dec 12 11:22:30 Tower kernel: dmar: DMAR:[DMA Read] Request device [02:00.0] fault addr f0049a000 Dec 12 11:22:30 Tower kernel: DMAR:[fault reason 06] PTE Read access is not set Dec 12 11:22:30 Tower kernel: dmar: DRHD: handling fault status reg 3

I'm using LVM instead of image files, I really like that and what I know much more powerful than image files , Google "LVM kvm" :-)

I removed transcode from /tmp and plex works.

I'm also positive that 6.1.4 have broken plex, what I know so have I not updated plex docker.

Thanks, plugin is now updated. //Peter

I need to update the plugin, there is a new version of this packages. http://mirrors.slackware.com/slackware/slackware64-current/slackware64/tcl/tcl-8.6.4-x86_64-2.txz //Peter

Router 192.168.0.1 Unraid 192.168.0.190 vpn 10.10.0.0

Do you set IP for VPN on same network as your LAN?

With this plugin you get access to your entire lan.

Please read the instructions, it says /boot/openvpn

Put these on your flash on a folder named openvpn, see instructions

That might be the issue using unassigned devices , for me using cache all is fine during boot, vpnserver is always up :-) //Peter

It works now, plugin updated. //Peter