Nexus

Could be. This is very odd.

Something is up w/ Macinabox. I decided to do a complete re-install. I deleted the VM's and the Docker container. Went to reinstall, and poof...it's gone. See attached. Can anyone else confirm this?

I did not upgrade to 6.9. I am on 6.6.7. The machine type was unchanged - it remains at 3.0. That's as high as it goes Thx Update: I tried to create another MIB VM - and when I restarted my array the new VM was there. (yay) BUT when Is started it - I got the same errors as I did w/ my original VM and can not continue.

Well this is a new one. I have not modified anything related to MIB or it's container - and today when I booted it up I got this error and I can't proceed. See attached for error and log. Any ideas what I can do to get it back and operational?

Thanks. I double checked and even changed it to something simpler (only letters/numbers) and still the same errors. What's very unclear to me is when I am configuring the VPN - I choose my VPN provider in the drop down but does that in fact change the OPENVPN_CONFIG drop down options? They never seem to change based on who I select as a your provider. Maybe that is the issue?

Hi All, I have tried multiple times to set up the Transmission/VPN docker. I use Windscribe and set the location and my password. I can't seem to get the WEBUI to open and this is the error log. Any help would be appreciated. Wed Jul 1 17:46:34 2020 OpenVPN 2.4.7 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Sep 5 2019 Wed Jul 1 17:46:34 2020 library versions: OpenSSL 1.1.1c 28 May 2019, LZO 2.10 Wed Jul 1 17:46:34 2020 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Wed Jul 1 17:46:34 2020 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication Wed Jul 1 17:46:34 2020 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication Wed Jul 1 17:46:34 2020 TCP/UDP: Preserving recently used remote address: [AF_INET]103.77.233.67:1194 Wed Jul 1 17:46:34 2020 UDP link local: (not bound) Wed Jul 1 17:46:34 2020 UDP link remote: [AF_INET]103.77.233.67:1194 Wed Jul 1 17:46:35 2020 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this Wed Jul 1 17:46:35 2020 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this Wed Jul 1 17:46:35 2020 VERIFY OK: depth=1, C=CA, ST=ON, L=Toronto, O=Windscribe Limited, OU=Operations, CN=Windscribe Node CA Wed Jul 1 17:46:35 2020 VERIFY KU OK Wed Jul 1 17:46:35 2020 Validating certificate extended key usage Wed Jul 1 17:46:35 2020 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication Wed Jul 1 17:46:35 2020 VERIFY EKU OK Wed Jul 1 17:46:35 2020 VERIFY OK: depth=0, C=CA, ST=ON, O=Windscribe Limited, OU=Operations, CN=Windscribe Node Server 4096 Wed Jul 1 17:46:35 2020 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1602', remote='link-mtu 1550' Wed Jul 1 17:46:35 2020 WARNING: 'cipher' is used inconsistently, local='cipher AES-256-CBC', remote='cipher AES-256-GCM' Wed Jul 1 17:46:35 2020 WARNING: 'auth' is used inconsistently, local='auth SHA512', remote='auth [null-digest]' Wed Jul 1 17:46:35 2020 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA Wed Jul 1 17:46:35 2020 [Windscribe Node Server 4096] Peer Connection Initiated with [AF_INET]103.77.233.67:1194 Wed Jul 1 17:46:37 2020 AUTH: Received control message: AUTH_FAILED Wed Jul 1 17:46:37 2020 SIGTERM[soft,auth-failure] received, process exiting Wed Jul 1 17:46:37 2020 AUTH: Received control message: AUTH_FAILED Wed Jul 1 17:46:37 2020 SIGTERM[soft,auth-failure] received, process exiting

HI all, I have been around Hackinstoshes before - I've build a few, but this is my first month w/ an Unraid server. That said, I have question about SIOnes excellent container. I have successfully built my High Sierra container and wanted to pass my Nvidia 1080 through for better perf. I followed his video - but what's not clear is once I make the change to enable the GPU to be passed through, how do I remote into it? He says to use Splashtop- but I don't know where to point my client to once I do that? It appears that once you enable a GPU that VNC is no longer an option to login in? Also: Is there a way to take a snapshot of the container I have not that is running fine - so I can roll back to it if I mess something up while getting the GPU passed through? Thanks! P.S. I installed Splashtop - and it's really laggy when I use it to connect to my VM. Worse than VNC