poldim

How can I use this, https://github.com/xombiemp/rutorrentMobile, which needs to be installed in the plugins directory? Is this a folder that I would need to map myself or does it need to exist elsewhere?

Feb 25 18:52:52 ChiRAID kernel: usb 5-1: USB disconnect, device number 7 Feb 25 18:54:44 ChiRAID kernel: usb 5-1: new full-speed USB device number 8 using uhci_hcd Feb 25 18:54:44 ChiRAID kernel: cdc_acm 5-1:1.0: ttyACM1: USB ACM device Feb 25 19:05:44 ChiRAID kernel: usb 5-1: USB disconnect, device number 8 Feb 25 19:05:48 ChiRAID kernel: usb 5-1: new full-speed USB device number 9 using uhci_hcd Feb 25 19:05:48 ChiRAID kernel: cdc_acm 5-1:1.0: ttyACM1: USB ACM device Feb 25 19:07:15 ChiRAID emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Feb 25 21:27:00 ChiRAID kernel: br0: port 3(vnet1) entered disabled state Feb 25 21:27:00 ChiRAID kernel: device vnet1 left promiscuous mode Feb 25 21:27:00 ChiRAID kernel: br0: port 3(vnet1) entered disabled state Feb 26 00:00:01 ChiRAID kernel: mdcmd (40): check Feb 26 00:00:01 ChiRAID kernel: md: recovery thread: check P ... Feb 26 00:00:01 ChiRAID kernel: md: using 1536k window, over a total of 4883770532 blocks. Feb 26 01:00:01 ChiRAID root: mover started Feb 26 01:00:01 ChiRAID root: mover finished Feb 26 09:08:55 ChiRAID kernel: md: sync done. time=32934sec Feb 26 09:08:55 ChiRAID kernel: md: recovery thread: completion status: 0 Feb 26 14:28:36 ChiRAID kernel: usb 5-1: USB disconnect, device number 9 Feb 26 14:28:44 ChiRAID kernel: usb 2-1: new high-speed USB device number 10 using ehci-pci Feb 26 14:28:44 ChiRAID kernel: hub 2-1:1.0: USB hub found Feb 26 14:28:44 ChiRAID kernel: hub 2-1:1.0: 4 ports detected Feb 26 14:29:27 ChiRAID kernel: usb 2-1.4: new full-speed USB device number 11 using ehci-pci Feb 26 14:29:27 ChiRAID kernel: cdc_acm 2-1.4:1.0: ttyACM0: USB ACM device Feb 26 14:34:33 ChiRAID emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Feb 26 14:34:59 ChiRAID emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Feb 26 14:35:20 ChiRAID emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Feb 26 14:35:23 ChiRAID kernel: usb 2-1: USB disconnect, device number 10 Feb 26 14:35:23 ChiRAID kernel: usb 2-1.4: USB disconnect, device number 11 Feb 26 14:35:32 ChiRAID kernel: usb 2-1: new high-speed USB device number 12 using ehci-pci Feb 26 14:35:32 ChiRAID kernel: hub 2-1:1.0: USB hub found Feb 26 14:35:32 ChiRAID kernel: hub 2-1:1.0: 4 ports detected Feb 26 14:35:32 ChiRAID kernel: usb 2-1.4: new full-speed USB device number 13 using ehci-pci Feb 26 14:35:32 ChiRAID kernel: cdc_acm 2-1.4:1.0: ttyACM0: USB ACM device Feb 26 14:35:41 ChiRAID kernel: usb 2-1: USB disconnect, device number 12 Feb 26 14:35:41 ChiRAID kernel: usb 2-1.4: USB disconnect, device number 13 Feb 26 14:35:44 ChiRAID kernel: usb 2-1: new high-speed USB device number 14 using ehci-pci Feb 26 14:35:45 ChiRAID kernel: hub 2-1:1.0: USB hub found Feb 26 14:35:45 ChiRAID kernel: hub 2-1:1.0: 4 ports detected Feb 26 14:35:45 ChiRAID kernel: usb 2-1.4: new full-speed USB device number 15 using ehci-pci Feb 26 14:35:45 ChiRAID kernel: cdc_acm 2-1.4:1.0: ttyACM0: USB ACM device Feb 26 14:35:54 ChiRAID kernel: usb 2-1: USB disconnect, device number 14 Feb 26 14:35:54 ChiRAID kernel: usb 2-1.4: USB disconnect, device number 15 Feb 26 14:35:58 ChiRAID kernel: usb 2-1: new high-speed USB device number 16 using ehci-pci Feb 26 14:35:59 ChiRAID kernel: hub 2-1:1.0: USB hub found Feb 26 14:35:59 ChiRAID kernel: hub 2-1:1.0: 4 ports detected Feb 26 14:35:59 ChiRAID kernel: usb 2-1.4: new full-speed USB device number 17 using ehci-pci Feb 26 14:35:59 ChiRAID kernel: cdc_acm 2-1.4:1.0: ttyACM0: USB ACM device

Here's the log: root@ChiRAID:~# cat /var/log/syslog | grep ttyACM Feb 24 08:52:12 ChiRAID kernel: cdc_acm 5-1:1.0: ttyACM0: USB ACM device Feb 24 13:32:54 ChiRAID kernel: cdc_acm 5-1:1.0: ttyACM1: USB ACM device Feb 24 14:37:16 ChiRAID kernel: cdc_acm 5-1:1.0: ttyACM0: USB ACM device Feb 24 15:04:46 ChiRAID kernel: cdc_acm 5-1:1.0: ttyACM0: USB ACM device Feb 25 18:54:44 ChiRAID kernel: cdc_acm 5-1:1.0: ttyACM1: USB ACM device Feb 25 19:05:48 ChiRAID kernel: cdc_acm 5-1:1.0: ttyACM1: USB ACM device Feb 26 14:29:27 ChiRAID kernel: cdc_acm 2-1.4:1.0: ttyACM0: USB ACM device Feb 26 14:35:32 ChiRAID kernel: cdc_acm 2-1.4:1.0: ttyACM0: USB ACM device Feb 26 14:35:45 ChiRAID kernel: cdc_acm 2-1.4:1.0: ttyACM0: USB ACM device Feb 26 14:35:59 ChiRAID kernel: cdc_acm 2-1.4:1.0: ttyACM0: USB ACM device Feb 28 02:30:02 ChiRAID kernel: cdc_acm 2-1.4:1.0: ttyACM1: USB ACM device Feb 28 09:55:06 ChiRAID root: home-assistant: Error response from daemon: linux runtime spec devices: error gathering device information while adding custom device "/dev/ttyACM0": lstat /dev/ttyACM0: no such file or directory Error: failed to start containers: home-assistantunifi: started succesfully! Mar 1 02:30:01 ChiRAID kernel: cdc_acm 2-1.4:1.0: ttyACM0: USB ACM device Mar 2 02:30:02 ChiRAID kernel: cdc_acm 2-1.4:1.0: ttyACM1: USB ACM device I think I know what it is: I had HA initializing a soft reset based on the suggestion on their zwave config page (all the way at the bottom) that ran nightly at 2:30. Any idea what's after cdc_acm in the log? Is it the USB bus/device/etc? I'd still like to find a solution to permanently bind the device to a static mapping. I've got a separate thread HERE for it, but no responses.

Any takers here?

I've now had the device change it's address from /dev/ttyACM0 to /dev/ttyACM1 and /dev/ttyACM1 to /dev/ttyACM0 at separate times completely on it's own. How do I stop this from happening?

I've tried to follow this guide for making a persistent path for my zwave stick and udevinfo doesn't appear to be recognized. # udevinfo -bash: udevinfo: command not found lsusb produces the device # lsusb Bus 002 Device 019: ID 0658:0200 Sigma Designs, Inc. Any thoughts on what can be done to persistently link it to a fixed path?

True - I went back and removed the privileged tag and it's working without issues. Is there a clearly define way of how I get it to always load the zwave stick into the same path? It seems that if I remove it and plug it back in, it jumps between ACM0 and ACM1, but not every time.

Just sharing what I've done: Inserted my Z Wave stick into my UNRAID server. Went to the main UNRAID log and found this: Feb 24 08:52:12 ChiRAID kernel: usb 5-1: new full-speed USB device number 4 using uhci_hcd Feb 24 08:52:12 ChiRAID kernel: cdc_acm 5-1:1.0: ttyACM0: USB ACM device Feb 24 08:52:12 ChiRAID kernel: usbcore: registered new interface driver cdc_acm Feb 24 08:52:12 ChiRAID kernel: cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters Found that the system is referring to the stick as ttyACM0 per above. Went into Home assistant docker settings, enabled advanced view, and made the following changes: Extra Parameters: --device=/dev/ttyACM0 Privileged: ON Followed instructions on setting up z-wave stick by adding the required code to the yaml file: zwave: usb_path: /dev/ttyACM0

On Krusader, when I initiate a move file transfer, the dialog bar appears at the top to show progress. If I click elsewhere in Krusader, it hides as the krusader comes back to the forefront. How do I go back to see the status of the transfer?

I had nextcloud working with mariadb but after trying to get it working with lets encrypt it's broken. I noticed the config file is missing the mysql reference you guys have. Is this part of the problem? <?php $CONFIG = array ( 'memcache.local' => '\\OC\\Memcache\\APCu', 'datadirectory' => '/data', 'instanceid' => 'xxxxxx', 'passwordsalt' => 'xxxxxx', 'secret' => 'xxxxxx', 'trusted_domains' => array ( 0 => '192.168.2.100', 1 => 'www.domain.me', 2 => 'domain.me', ), 'trusted_proxies' => array ( 0 => '192.168.2.100', ), 'overwritewebroot' => '/nextcloud', 'overwritehost' => 'domain.me', 'overwrite.cli.url' => 'https://192.168.2.100', 'dbtype' => 'sqlite3', 'version' => '11.0.0.10', 'logtimezone' => 'UTC', 'installed' => true, );

Followed the guide, they're all disabled and high performance power plan is on.

Could the fact that I'm using SeaBIOS be causing this issue?

I've found that using these settings appears to allow the VM to install normally. Key is the SeaBIOS and SATA settings.

I've got a Win10 VM that runs fine for about a half hour then just dies. I'm not sure if the networking stack is what's crashing preventing me from being able to use RDP or VNC to reach the system. Force stopping seems to be the only way of stopping the system. Upon restart, it comes back as it should and I can RDP in.

I should have clarified that I tried bridge only after hissy was not working and I thought it had something to do with the ups witching and VLAN setup. Having the docker in HOST creates the same "searching for server" behavior.

My plex server doesn't seem to be finding it's server. I'm not sure if this is related to recently changing by unraid IP. But I'm set to use Bridge network and can load up the Plex UI on IP:32400. Error message: The selected server is unreachable. Make sure it's running, double check your network, and try again. Connecting Where is my server? Remove server I've deleted the previous docker and moved my appdata/Plex folder out of the appdata folder and created a new docker. Still getting the same server not found message.

All cross VLAN communication is up and running. I can access the GUI no problem from all three networks and its functioning as it should (eth ports are untagged for VLAN 20 + trunked [tagged] for for 30 + 40). Only the guest network is islanded.

The first screenshot of the networks list IS from my router. I'm not trying to use unraid as another router.

I've got the following networks: I've setup my unraid server on the homelab network as well as the home automation and WLAN VLANs [settings]. I can access the GUI no problem from all three networks and its functioning as it should (eth ports are untagged for VLAN 20 + trunked [tagged] for for 30 + 40). The problem is that I cannot get the VMs to communicate at all. The two Win VMs are unable to ping anything and do not obtain DHCP IPs. I've assigned one to the default br and one to br.30 [options]. Behavior from both is the same with no connectivity. What am I doing wrong?

In the same position...

Are there docker / container options for running a DNS server? Or do nginx or apache provide similar functionality?

With the openVPN server running on unraid, will this only let you into your unraid box or your entire LAN + all subnets? I'm trying to determine if this is the best way to go or setup the VPN on my UniFi Router.

Is there a way to run the pi hole on a different IP address that way I can keep unpaid's UI on port 80? I've tried changing the port to other numbers and get the same error: [b]Removing container: pihole[/b] Successfully removed container 'pihole' [b]Command: [/b]root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="pihole" --net="bridge" -e TZ="America/Los_Angeles" -e HOST_OS="unRAID" -e "ServerIP"="192.168.1.26" -e "DNS1"="8.8.8.8" -e "DNS2"="8.8.4.4" -e "IPv6"="False" -p 53:53/tcp -p 53:53/udp -p [u][color=red]8111[/color][/u]:80/tcp -v "/mnt/user/appdata/pihole/pihole.log":"/var/log/pihole.log":rw -v "/mnt/user/appdata/pihole/blacklist.txt":"/etc/pihole/blacklist.txt":rw -v "/mnt/user/appdata/pihole/whitelist.txt":"/etc/pihole/whitelist.txt":rw --cap-add=NET_ADMIN diginc/pi-hole:alpine d4cea8212b5f7536bf61ecaa4b2cd218d8ebbdb121a7bd1546f490f21b5b1375 docker: Error response from daemon: failed to create endpoint pihole on network bridge: Error starting userland proxy: listen tcp 0.0.0.0:53: bind: address already in use. [b]The command failed.[/b] Unraid's IP is .25 and none of the other dockers are using port 8111. For 53, I get this: netstat -tulpn | grep --color :53 tcp 0 0 192.168.122.1:53 0.0.0.0:* LISTEN 11799/dnsmasq udp 0 0 0.0.0.0:53657 0.0.0.0:* 1681/rpc.statd udp 0 0 192.168.122.1:53 0.0.0.0:* 11799/dnsmasq udp 0 0 0.0.0.0:5353 0.0.0.0:* 8064/avahi-daemon:

Thanks

Can someone explain how changing the default port improves security?