JasonJoel

Not that this helps, but I would LOVE to see the font larger in the terminal.

Putty it is then. Thanks for your help, as always!

Very true, and I can certainly do that. It is just to tantalizingly easy to click the terminal button when in the interface, though. To your point - putty is a fine workaround if it can't be changed.

I guess I'm getting old... I simply can not easily read some of the text on the unraid console when I get in there. The green background highlighting with blue text messes with my eyes. Is there any way to change that? Example, see the text on the directory listing:

Understood, and that's what I did - no issues. Thanks for maintaining these great plugins!

Awesome, and thanks. I use this container for a bazillion things, and very much appreciate you maintaining it!

Stupid question @cmccambridge.... The community apps version of the container is 1.5.8... But I see the current version on your github is 1.6.x. EDIT: Never mind. It looks like when it installed originally the repository was listed as "cmccambridge/mosquitto-unraid:1.5.8". I changed it to "cmccambridge/mosquitto-unraid:latest" and all is good.

I use a SUPERMICRO MBD-M11SDV-8C-LN4F-O on my Unraid server. Epyc 3251 based. Works fine for my use (10 docker containers, 3-5 VMs, file server). I don't have any comments on 10GB ethernet, as I see it it as a waste (for my home use) until the switches come down in price.

I am surprised parted was moved to plus... Seems like anyone that mounts drives will want to format one sooner or later (?).

It looks like the issue was indeed on the Allowed IPs on the peer side when I set it up via the QR code. I guess by default it only adds the subnet the Unraid server is on, and its 10.253.0.1 tunnel address (which makes sense). Thanks for the pointer on Allowed Peer IPs!!! I didn't think to check that on the Android/peer side...

Hmm... Good question, I'll go through it again tonight and double check. Entirely possible it was user error.

I did get it to work - kind of. I could access anything on my primary subnet (192.168.1.x) which is the same subnet my unraid server is on. But I couldn't ever connect to anything from any of my other subnets. Didn't see the traffic at my router at all - so I'm not sure the bridge is routing traffic from other subnets (?) up to the router. I tried turning NAT on/off, no difference. Works fine w/OpenVPN, so back I went. I will say that wireguard was fast and connected quickly for those nodes on my primary LAN. Very cool - just wish I could get to my other subnets. Untangle is going to add wireguard support, too, so I may just have to wait for that, as theirs will support multiple subnets/routing.

So what is the verdict - can you use WireGuard if your Eth0/Eth1 is in a bond, or not (for Remote to LAN type conections)? I would rather not disable the bond, as I regularly go over a single 1Gb connection of bandwidth when doing backups on multiple nodes. Thoughts? My network connections today: Eth0/Eth1 - bonded, bridging = false. Eth2 - VM/Docker LAN connections, bridging=true Eth3 - VM/Docker IoT connections, bridging=true

Upgraded from 6.7.2 - no obvious issues. Thanks!

I setup notifications to go to Pushover. The problem is that the notifications go to ALL devices configured in Pushover. I have a lot of different devices configured in there, and don't want the notifications to go to all of them. Rather, I would like them to go to one specific device. Is there any way to do that?

Sorry to dredge up an old thread... But I saw my trim was failing on my 9207-8i card. Downgraded to firmware 16, and trim works correctly now. Thank you for the tip.

I would LOVE for the default colors to change / be able to be changed!!! The green back highlighted text is impossible to read.

Upgraded my AMD EPYC based system, no issues.

Fair enough - poor wording choice on my part. How to do the container definition via the GUI was tripping me up. I did get it to work, though, so thought I would come back and at least list how I did it (even though it was simple for anyone that understands docker better than I do ): 1. Imported node container from docker hub via CA 2. Set network to the interface I needed (br3 in my case) 3. Set static IP address 4. Added a path setting for the /user/src/app container location to /mnt/usr/appdata/<container name> 5. Switched to Advanced View 6. Added "-w /usr/src/app" in "Extra Parameters:" 7. Added "server.js" in "Post Arguments:", with server.js being the name of my node.js app. 8. Hit Apply and ran the container.

What I am trying to do is run a simple node.js app in a container, instead of the Ubuntu VM it is in now. I am a docker novice, but have been using it for a few years - mostly pre-made containers, but on Ubuntu I've made a few of my own that work as expected. I've never used a custom container in unraid, though, and the differences are tripping me up. In the end, what I'm trying to do is exactly what is described on the official node.js docker page: Is there a relatively straight forward way to do this in Unraid? I see how I can import the node container from docker hub, but past that I'm struggling. Thanks in advance for any help or advice.

My Supermicro / AMD EPYC 3251 based server seems to be perfectly compatible.