Everything posted by bonienl
-
Assign docker to physical Nic
This is really weird. I am using the LSIO plex container. You can try this one and see if it makes a difference.
-
Assign docker to physical Nic
the binhex-plexpass
-
Assign docker to physical Nic
If the above stop / start doesn't work, try the following 1. Delete the plex container (including the image) 2. Add container and select the Plex template This will re-install the container freshly with all settings retained
-
Assign docker to physical Nic
The webUI field in the settings is correctly filled-in, this should give the GUI option in the dropdown menu. Can you stop and start the container. Does that make a difference?
-
Assign docker to physical Nic
Everything looks alright. Can you post a screenshot of the not working part?
-
Assign docker to physical Nic
Sorry, I forgot to say "view in advanced mode" (plex settings)
-
Assign docker to physical Nic
Post a screenshot of your Plex settings
-
Unraid OS version 6.8 available
@m8ty the underlying script to do the upgrade does several checks and necessary updates, which are not available when doing a manual update. This may lead to some inconsistency (all depends on your situation before upgrading). Any reason to do a manual upgrade?
-
Assign docker to physical Nic
Do the following network configurations (see Settings -> Network Settings) Eth0 - bond = No, bridge = Yes (single member eth0), static IP address = 10.0.1.122 /24, gateway = 10.X.X.X Eth1 - bond = No, bridge = Yes (single member eth1), IP address = NONE --------------------------------------------------------------------------- Docker configuration (see Settings -> Docker) BR0 - uncheck BR1 - Subnet = 10.0.1.0 /24, gateway = 10.X.X.X, DHCP pool = 10.0.1.128 /25 (assuming this does not conflict with the DHCP range of your router) When you configure the Plex container, choose "Custom br1" as network and give the container the static address 10.0.1.124
-
[KERNEL]custom kernel build with treaks (2020.03.07 v6.8.3|5.5.8|4.19.108|NAVI|VEGA|NFSv4|R8125|Zen2)
It may sound good to do a custom build, but I strongly recommend you use the Unraid stock build and make a request for the missing parts (no guarantee they are added) Custom builds are impossible to support. Next time you have an issue, nobody can help you. Even more it will be extremely confusing. A custom build will not be mentioned in the error topic and people will be clueless about the differences.
-
WireGuard quickstart
What do you mean with "so my firewall is active"? Switch to advanced view and make sure "Local server uses NAT" = Yes Anything in a different network as 192.x.y.z needs two-way routing (but this is out of scope for Unraid)
-
WireGuard quickstart
Switch to "advanced view" and set "Local server uses NAT" = "Yes". (If this setting is "No" you will need to add a static route on your router to point back to the WG tunnel)
-
Unraid OS version 6.8 available
I have three servers running with a static IP assignment...
-
[6.8.0] Unresponsive
Start with libvirt.hotplug.usb NerdPack
-
[6.8.0] Unresponsive
First thing to do is start your system in "safe mode" without plugins and retest.
-
[6.8.0] Unresponsive
Please open a topic under general support. Something "else" is interfering with your set up. Did you try "safe mode"?
-
WireGuard quickstart
Yes, this works (I tested this using a bonded interface with 4 members)
-
WireGuard quickstart
Use "wg" instead root@vesta:/# wg interface: wg0 public key: +vmlfqmRg6XxRCo86Ynqzsobd4kN0HXZsq2bN13akCI= private key: (hidden) listening port: 51821
-
Setting Up WireGuard® on Unraid
dnsmasq is used by the VM manager and listens on the virbr0 network. Stopping the VM service will stop dnsmasq too. Ps. good to hear you have it working.
-
Unraid OS version 6.8 available
VNC is working just fine for me with Unraid 6.8
-
Setting Up WireGuard® on Unraid
I haven't tested this, but if it works, it certainly is a plausible afternative.
-
Unraid OS version 6.8 available
Try the following: 1. Stop the VM(s) 2. Go to the edit page of the VM(s) and press "Update" (this forces VNC to re-apply the VNC port) 3. Start the VM(s) and try to access using VNC
-
Unraid OS version 6.8 available
The implementation of WireGuard on Unraid, allows VPN access even when the array is not started. And remote access is almost instantly available after reboot. This is a huge advantage as compared to WireGuard running in a docker container, which is only possible when the array is up and running and all services are correctly started.
-
WireGuard quickstart
It is unclear to me what you try to achieve. If there is another server setting up a WG tunnel, then it might be as simple as setting routing for the Unraid server to the "external" WG tunnel, but this has nothing to do with the WG implementation on Unraid
-
WireGuard - VPN Tunneled Access to a commercial VPN provider
Difficult to say, because it is unclear / not possible yet, how to do this with WireGuard.