ljm42

Hey folks, please go to the Plugins tab and check for updates, this will upgrade you to Unraid Connect: https://forums.unraid.net/topic/138392-unraid-connect-plugin-announcements/#comment-1255739 There have been many changes and improvements which should resolve many problems. Of course, if you continue to have issues please let us know.

Hey folks, please go to the Plugins tab and check for updates, this will upgrade you to Unraid Connect: https://forums.unraid.net/topic/138392-unraid-connect-plugin-announcements/#comment-1255739 There have been many changes and improvements which should resolve many problems. Of course, if you continue to have issues please let us know.

My Servers is now Unraid Connect! Check it out:

The Unraid API does not cause networking issues, however, it will alert you to them. At the time of your screenshot the system was having a DNS issue, which would also cause issues for containers. When the problem is happening you can grab diagnostics and ask for help in general support. Give the system a minute to stabilize after the reboot, the reload the page. If the error persists you can open a web terminal and type: unraid-api restart then wait a few minutes and reload the page, the message will likely be gone. We continue to improve this, keep an eye out for upcoming release

The screenshots show a line that says: nmbd: messaging_reinit() failed: NT_STATUS_DISK_FULL A full root filesystem can mess up all kinds of things. I would guess that whatever caused that is the source of the weirdness you were seeing. Unfortunately I don't see anything here that can tell us why it got full. One thing you can do is mirror the syslog to the flash drive: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/?tab=comments#comment-781601 so if this happens again there should be some clues as to what happened. This does add wear and tear on the flash drive so you wouldn't want to keep it running for months on end. The other thing is, make sure you have the ability to SSH to the server. Then even if the webgui doesn't work you can still type 'diagnostics'. Or if that fails you can type 'cp /var/log/syslog /boot' to copy the syslog to the flash drive so you can access it from another computer after shutting down.

I don't see any evidence of a hack in these files or screenshots. Let's see if someone else does. One thing to note - the diagnostics were generated before Fix Common Problems had a chance to run, so we can't see what it might have detected: Apr 11 15:05:25 NAS root: Delaying execution of fix common problems scan for 10 minutes If the OS was hacked, the hacker's changes were probably wiped out when you rebooted the server, since Unraid is loaded fresh each time it is rebooted. It is possible that a Docker container was hacked, that would not show up here. And those are not wiped after a reboot. If you have reason to believe a Docker container was hacked you should delete and recreate those.

If you would like help from the community we will need to see logs and settings. The next time you boot the system, wait for the problems to happen then generate a diagnostics.zip file (from Tools -> Diagnostics or by typing "diagnostics" via SSH) and upload the zip file here. The diagnostics does not include your list of users, so go ahead and post /etc/passwd as well so we can look for anything out of the ordinary.

This is not part of a normal workflow and not is not something I would ever want new users to think they need to do. I don't see this being added as a core feature of the product. However, if you are doing something like creating content for YouTube I could see the value in being being able to easily reset to stock between takes. It wouldn't be too difficult, mainly overwriting the config folder with stock files and rebooting. If you'd like to discuss this, please start a new thread where you describe your use case and what all you want. I'm sure the community can help you come up with a solution.

For me at least, network reliability is key and speed is a distant second. My main suggestion for networking is to keep it simple - if you have issues and need support, the more complex your network the fewer people there are who can help. So avoid jumbo frames and bonding. And use minimal VLANs - I put my IOT devices on a separate VLAN but keep all the real computers on the main network (with no VLAN tag) The UI LAG switches are for SPF connections only, so plug whatever SPF devices you have in there and plug your RJ45 switches into something else. But that seems kind of obvious : ) so maybe you could describe a bit more about what kind of advice you are looking for? I described my setup a bit in this thread, in case it helps: https://forums.unraid.net/topic/137637-unraid-networking-help/#comment-1252169

For random disconnections I would get rid of any off-brand switches and replace them with Unify. After that, I'd suspect the cabling. I threw out all of the random network cables I had collected over the years and replaced them with Monoprice Slimline Cat 6A cables https://www.amazon.com/Monoprice-SlimRun-Cat6A-Ethernet-Patch/dp/B01BGV2YS2/ I really like the slim form factor and they handle 10 GbE just as well as the Cat 7 cables I tried.

Glad you were able to find the cause

Having said that, if this is one of those "I want to try everything I possibly can" situations that can be a lot of fun : ) Just realize that is not the same as a "set it and forget it" situation; the more complex your network the harder it is to deal with issues. I too really like the Ubiquity ecosystem. I have the UDM SE with a USW-EnterpriseXG-24 switch. I have two Unraid servers with dual 10 GbE NICs and a 10 GbE connection for my laptop. Plus other 1 GbE, 2.5 GbE, and WiFi 6 devices. eth0 on each server is one of the 10 GbE ports connecting to the main network. This is a simple, easy to understand setup. But I do have those second 10 GbE ports on each server asking to be used : ) I can think of three options: 1) Setup a jumbo frames subnet. I did this by direct-connecting eth1 on the two servers and changing the mtu to 9000 on that connection. But it only added 5-10% to the speed and for me was not worth the hassle of remembering to use the alternate network when doing server to server transfers. 2) Bond the two ports. The thing is, this doesn't give you a 20 GbE connection between the servers. What it does is let each server talk to two clients at 10 GbE at the same time. That might be useful in a large business but in my home lab, not so much. 3) Use the second NIC for Docker containers. This is where I'm leaning: https://forums.unraid.net/topic/137048-guide-how-to-solve-macvlan-and-ipvlan-issues-with-containers-on-a-custom-network/ Anyway, that is my situation. Hopefully it gives you some ideas : )

Jumbo frames are leftover tech from the early days of networking, IMHO they provide endless headaches for very little speed improvement on modern hardware. The only time they should be used is on a dedicated subnet that doesn't connect to the Internet, where every device on that subnet uses jumbo frames. If you ever have any kind of networking problem, your first thought should be to disable jumbo frames and the second to disable the bond. Both of these require proper configuration of other networking gear not related to Unraid. Supporting this requires knowledge of both Unraid and your networking gear and is beyond the scope of what most people can help with. Fix Common Problems should be warning about both

I am not aware of any issues overriding the DNS servers provided by DHCP. If you are able to reproduce this, first try again in another browser (ideally one without plugins or ad blockers) If the problem happens in multiple browsers, please provide me with step by step instructions to reproduce it myself. A Loom recording of the problem ( https://www.loom.com/ ) could also be helpful. Unzip your diagnostics and look at the system/urls.txt file It shows that at the time you collected diagnostics, DNS 1 was undefined It also hides your IP address because it determined that the IP is routable. This was logic I added for privacy reasons, but if you feel I got the logic wrong please let me know what the server's IP address so I can review the logic.

Based on the timing of your post, this message probably happened when the My Servers Cloud was down for a bit. I assume it is fixed now, if not please start a new thread over in the My Servers forum board. Be sure to mention how you noticed the problem and whether it is affecting anything

Hmm, I expected the nginx command to grab the current ip from eth0 and rewrite the nginx config files, but that didn't happen I think we are in a weird state from hand editing the network.cfg, where it wasn't fully applied. Can you try a reboot? Once this is resolved, you'll want to investigate these read and write errors on disk1. Hopefully someone else can help with that: Apr 3 00:33:30 HunterNAS kernel: md: disk1 read error, sector=2160964152 Apr 3 00:33:30 HunterNAS kernel: md: disk1 write error, sector=2160937944

You need to break the bond in order to use the NICs independently. The bond has its own MAC address, so when you break it you will likely get a different IP address from the router. You want to configure the main NIC as eth0 I would get that much working before adding more complexity.

Keep in mind that the upload/download speed on both ends matter. Downloading from home to a remote locations uses your home upload speed and the remote download speed. Whichever is slower is the bottleneck. Uploading from a remote location to home uses your remote upload speed and home download speed. Whichever is slower is the bottleneck.

If you are comfortable on the command line you can edit the same file here: /boot/config/docker.cfg to disable Docker and then reboot. Or you can edit this file: /boot/config/ident.cfg and change the PORT to something other than 80, then reboot. But you must take care to choose a port that is not already in use.

The webgui is trying to load on port 80 but something is already using that, probably a Docker container. There are a couple of ways to solve it, what I would do is shut the server down, move the flash drive to another computer and edit config/docker.cfg and change DOCKER_ENABLED="yes" to DOCKER_ENABLED="no" Then put the flash drive back in the system and boot up. When the system comes back up the webgui will work, then you can go to Settings -> Docker and enable Docker, then go to the Docker tab and figure out which container is trying to use port 80 and change it to something else. Do not reboot again until you've fixed this : ) Newer versions of Unraid do a better job of protecting you from configuring these sorts of conflicts.

127.0.0.1 refers to Unraid itself, there is no DNS resolver there. You should put the IP address of the PFsense VM. Or really, just keep it pointed at a public DNS server like 8.8.8.8. Many people cause problems for themselves by pointing at a local DNS server like pihole that does ad blocking and it ends up blocking something Unraid needs. If your network is using routable IPs then DNS Rebinding Protection doesn't really protect you from anything anyway. It isn't a hard requirement, but I would recommend using a private IP space and then disabling DNS Rebinding Protection for the myunraid.net domain. Using pfsense you can leave it enabled everywhere else. That is a private IP so it is something on your network. If you do a Google search for "unraid 172.17.255.255" it looks like it is related to Docker. If you want more details I'll move this thread to General Support where more folks will see it.

It looks like your server is configured for Jumbo frames, revert that back to normal. See https://forums.unraid.net/topic/120220-fix-common-problems-more-information/page/2/#comment-1167702 It also looks like the server has four NICs, but eth0 is not connected. Unraid works best when eth0 is your main NIC, you can either move the network cable around until you find eth0 or you can go to Settings -> Network Settings Interface Rules and adjust until the connected NIC is eth0. See https://forums.unraid.net/topic/120220-fix-common-problems-more-information/page/2/#comment-1170361 Once the network is back, I highly recommend you install the Fix Common Problems plugin as it will automatically alert you to this sort of thing.

Please don't post the same thing in multiple places. I've already replied in your other thread so let's keep the conversation there: https://forums.unraid.net/topic/137820-lost-my-servers-connection/

OK glad you're into the server now. Please open a web terminal and run: /etc/rc.d/rc.nginx reload That may resolve the issue, if not please upload your diagnostics.zip (from Tools -> Diagnostics)

It looks like the system does not have a DNS server. Go to Settings -> Network Settings and apply a static DNS server of 8.8.8.8, that will likely solve your connectivity issues. Once the network is working, I'd highly recommend that you install the Fix Common Problems plugin, it will alert you to other potential issues. Also, the server has a routable IP address. Unraid is not meant to be put directly on the Internet, it should be behind a firewall. DNS Rebinding Protection must be disabled in order to use ip.hash.myunraid.net urls.