tknx

@JorgeB tried direct connect same problem. My Caddy reverse proxy works fine to get into the services onto the machine from outside. I cannot ssh into the machine remotely either but can use the webUI based terminal.

Well now when I change network settings the UI entirely crashes, what a mess...

No luck there either.... This is pretty frustrating! root@Mnemosyne:~# ping cnn.com PING cnn.com (151.101.3.5) 56(84) bytes of data. From 10.253.0.1 (10.253.0.1) icmp_seq=1 Destination Host Unreachable ping: sendmsg: Destination address required ^CFrom 10.253.0.1 icmp_seq=2 Destination Host Unreachable ping: sendmsg: Destination address required --- cnn.com ping statistics --- 2 packets transmitted, 0 received, +2 errors, 100% packet loss, time 5001ms root@Mnemosyne:~# mnemosyne-diagnostics-20221017-1150.zip

Ok. I renamed network.cfg and by default I still get errors on ping mnemosyne-diagnostics-20221017-1107.zip

Hi @Jorge Yes - it does have internet access through eth0. eth1 doesn't have anywhere to clear a gateway from?

Fix Common Problems is having troubles connecting to github, if I try to ping google.com from the command line, it fails too. root@Mnemosyne:~# ping github.com ^C root@Mnemosyne:~# ping cnn.com ^C root@Mnemosyne:~# ping 1.1.1.1 PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data. ^C --- 1.1.1.1 ping statistics --- 14 packets transmitted, 0 received, 100% packet loss, time 13319ms root@Mnemosyne:~# ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. No idea why this is happening! mnemosyne-diagnostics-20221017-0934.zip

When I enable docker, the various lans get split up with shims to cover the addressable space. So in the attached picture you can see that my 10.0.0.0/22 main network has two shim-br0 to cover the addressable space: 10.0.0.0/23 10.0.2.0/23 Same for the IOT VLAN 10.0.20.0/24 which has two shim-br0.20 10.0.20.0/25 10.0.20.128/125 And then there are two entries at the bottom which I have no idea what they are for, but look like they are splitting apart the docker network: 172.17.0.0/16 docker0 172.31.200.0/24 br-fcb95060594f 172.31.201.0/24 br-6aaca2bea56c

Replacing the docker image fixed the network issues.

So I replaced the flashdrive and ported over my config folder and key, but none of my network settings stayed, There are no custom: br0 type network options available either. I basically want my default lan and my IOT vlan (20) available with custom br0 and br0.20 to appear. Nothing else. Added a screenshot of what I see when configuring a docker and a screenshot of my routing table, which clearly do not seem to match I can't ssh into my server either right now. mnemosyne-diagnostics-20221013-1137.zip

It is a relatively new one but yeah. Definitely going to switch it out.

Like an hour? something is going on with the boot usb too. Like I can’t use the CLI to manually grab the logs either. It won’t let me navigate to /boot/logs. The WebUI is now down entirely and the poweroff CLI command isn’t working. So I will probably do an unclean shutdown, update the USB and cross my fingers and hope for the best. But the whole thing is really making me nervous about my system.

I will. I guess. But I am unhappy that the functionality for both updates and logs are broken.

I want the new kernel so I can have hardware transcoding work with my Gen 12 Intel processor, so bit the bullet to do an upgrade. But no matter what I get stuck here: plugin: updating: unRAIDServer.plg plugin: downloading: https://unraid-dl.sfo2.cdn.digitaloceanspaces.com/stable/unRAIDServer-6.11.1-x86_64.zip ... done plugin: downloading: https://unraid-dl.sfo2.cdn.digitaloceanspaces.com/stable/unRAIDServer-6.11.1-x86_64.md5 ... done writing flash device - please wait... Archive: /tmp/unRAIDServer.zip I am unable to download diagnostic logs either, so I am unsure if it is flash drive related or something else.

So I want to setup Wireguard as tunneled access to my various VLANs (10.0.0.0/22; 10.0.20.0/24; etc.) I can get the Wireguard tunnel to access anything in my main LAN which is the 10.0.0.0 one where the Unraid server lives, but nothing on the 10.0.20.0 (vlan ID 20) one. Settings are here for my Unifi router and Unraid WG: https://imgur.com/a/77uP7pT

OK, test messages worked. So it is most likely Unraid that isn't sending remote logs.

Switching to VAAPI seemed to fix it. Let me do some more experimenting to see what is going on

So I switched to the official docker but can't get intel quicksync working. Whenever I try and use hardware transcoding it fails to do it and says the format is unsupported. Set it following the directions from the original docker (install intel_gpu_top and /dev/dri in config)

Hi Andrew, Here is an example pics of my config for the container and my config on the Splunk file. Nothing coming through on either UDP or TCP when I try either.

Trying to do this finally -, and of course that is its own project...

Hi I just set it up and am trying to send my unraid remote syslog to it, but no messages are coming through. I set it for a br:0 address, opened up port 514 TCP which is what I am sending from unraid on. Anything I am missing?

No UI elements were working, couldn't figure out what was going on and had to do an unclean shutdown. Rebooted the system at 11:05am PT Anyone able to tell why from the attached diagnostics? mnemosyne-diagnostics-20220716-1107.zip

So how do I get back to a default network config?

OK - I have no idea where the virbr network comes from. In all transparency, besides eth0, eth0.20, and wg, I have no idea what the rest of these are or what they do. This image worked fine until I stopped bridging my SFP+ ethernet with the not plugged in onboard ethernet. So do I have to modify each and every VM i installed and that was working? Why? My table looks like this:

I have several VMs and since I switched off of bridge to a single ethernet connection, they just don't seem to want to get an IP. Before I switch back to the bridge setting, I want to make sure I understand what is going on. Attached logs and some screenshots of one of them. mnemosyne-diagnostics-20220622-1110.zip

I updated the OS manually because the update would fail through the UI - but I think those were the same issues. I think I'll use this opportunity to recreate my dockers on xfs and hope that is it. I noticed that docker is not using the right runtime for one of the errors. I think I fixed the br0.20 errors which happened from when I switched over to my SFP+ card. I'll see if I can catch a video of it happening again.