[Jitsi?]

Try forwarding TCP port 5222 on your router to the unraid server internal address. May have to also map it for docker in unraid. For Jitsi you need ports 443 for https, 80 for http, UPD 10000, and TCP 5222. You can of course remap these to none standard points in your router as Unraid already uses 80 and 443. Here's a link to the jitsi documentation also. https://github.com/jitsi/jitsi-meet/blob/master/doc/manual-install.md

[No internet connection - unable to ping google]

On 4/2/2020 at 1:02 AM, xxbigfootxx said:

I am able to access my server from local network. Has a static IP set and DNS is set to 8.8.8.8 and 8.8.4.4 but when i try to ping google.com or 8.8.8.8 it comes back with network unreachable. 

 

 

I added a deafult route to my IP routing table as i noticed there was none there. When i add it though it shows up as wg0 instead of eth0. This wg0 has it's own IP address linked and i'm not sure if this is somehow linked but i've been unable to locate what the wg0 link is. 

 

Any help would be appreciated. 

See this has been up for a while so hopefully you have resolved this. One think to check. If you unraid host has multiple NICs and an IP is assigned in Network settings for each then make sure the br0 IP and physical post eth0, eth1, etc IP that you are connecting with match or that all are connected. The issue this causes is the ping request will leave via the connect NIC's IP but then your router will attempt to route the response back to you via the IP for the main NIC aka the NIC that has the same IP as br0. All you have to do is move the network connection to the correct NIC and you should be set. This is usually eth0 unless you have changed the config manually.

[Unable to load 6.8.0-rc3]

4 hours ago, cybrnook said:

If you didn't want to dig much further, you can always download the package manually and extract onto your USB.

This thought had crossed my mind but wasn't sure if it may cause other issues. Will it still provide the restore option if I needed to roll back in case of issues? Any specific options/flags to be used or just:

 

unzip unRAIDServer-6.8.0-rc3-x86_64.zip -d /boot

[Unable to load 6.8.0-rc3]

4 hours ago, Squid said:

One possibility:  Is your date and time out to lunch?

From terminal running date returns the correct date and time. Is there another process to check or location to check date and time? Seems to not be the issue though.

[Unable to load 6.8.0-rc3]

When selecting next branch in OS Update It shows the 6.8.0-rc3 version and the Install button. Clicking install brings up the Install Plugin window which shows the below errors:

 

plugin: installing: /var/tmp/unRAIDServer.plg
plugin: downloading: https://s3.amazonaws.com/dnld.lime-technology.com/next/unRAIDServer-6.8.0-rc3-x86_64.zip ... failed (Network failure)
plugin: wget: https://s3.amazonaws.com/dnld.lime-technology.com/next/unRAIDServer-6.8.0-rc3-x86_64.zip download failure (Network failure)

 

Not sure why there is a network failure here as I have internet access (can load apps page, upgraded plugins and dockers already) and can also ping successfully, via SSH into unraid, external sites like google.com and amazon.com.

 

Trying wget from SSH I get the below:

 

root@d2:~/test# wget https://s3.amazonaws.com/dnld.lime-technology.com/next/unRAIDServer-6.8.0-rc3-x86_64.zip
--2019-10-19 10:53:16--  https://s3.amazonaws.com/dnld.lime-technology.com/next/unRAIDServer-6.8.0-rc3-x86_64.zip
Resolving s3.amazonaws.com (s3.amazonaws.com)... 52.216.133.165
Connecting to s3.amazonaws.com (s3.amazonaws.com)|52.216.133.165|:443... connected.
OpenSSL: error:1408F10B:SSL routines:ssl3_get_record:wrong version number
Unable to establish SSL connection.

 

If I change https to http it is successful.

 

root@d2:~/test# wget http://s3.amazonaws.com/dnld.lime-technology.com/next/unRAIDServer-6.8.0-rc3-x86_64.zip
--2019-10-19 10:58:05--  http://s3.amazonaws.com/dnld.lime-technology.com/next/unRAIDServer-6.8.0-rc3-x86_64.zip
Resolving s3.amazonaws.com (s3.amazonaws.com)... 52.216.164.37
Connecting to s3.amazonaws.com (s3.amazonaws.com)|52.216.164.37|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 220557400 (210M) [application/zip]
Saving to: ‘unRAIDServer-6.8.0-rc3-x86_64.zip’

unRAIDServer-6.8.0-rc3-x86_64.zip             100%[==============================================================================================>] 210.34M  50.6MB/s    in 6.2s    

2019-10-19 10:58:12 (33.8 MB/s) - ‘unRAIDServer-6.8.0-rc3-x86_64.zip’ saved [220557400/220557400]

 

Thoughts on why https download is failing and how to correct?

 

[libusb error do close]

I have been getting the below error on one of my VMs. It happens almost daily. Restarting the VM works sometimes but lately it just happens again within minutes. I haven't had much luck finding any info on this at least that is helpful. Also just to note no usb devices were disconnected at least physically. Please let me know if there are other logs or info needed would be happy to provide it. Thanks

 

libusb: error [_open_sysfs_attr] open /sys/bus/usb/devices/3-3.4.1/bConfigurationValue failed ret=-1 errno=2
libusb: error [do_close] Device handle closed while transfer was still being processed, but the device is still connected as far as we know
libusb: warning [do_close] A cancellation for an in-flight transfer hasn't completed but closing the device handle
libusb: error [do_close] Device handle closed while transfer was still being processed, but the device is still connected as far as we know
libusb: error [do_close] A cancellation hasn't even been scheduled on the transfer for which the device is closing

 

 

Also to add details of the VMs being run. They are running Linux Mint 18 KDE they are assigned 8 cores and 8 GB ram. For usb devices they each have usb keyboard and mouse and a usb sound card on all but one of three VMs. The third VM is using the on board sound. Passing through pci for video cards.