ljm42

You can probably disable the onboard NIC in your BIOS. Or you can go to Settings -> Network Settings -> Interface rules and adjust so that the 10GB nic is eth0 Either way, note that when your server reboots it will get a different IP address from the router since the 10GB nic has a different mac address. It might help to have a monitor on the server so you can see the ip address on the console when the system boots.

@Squid Can we move Draculya's issues to a new thread in general support? This is the Unraid Connect area of the forum and these are bigger issues that need more eyes on them

Would you please upload another diagnostics? This one was from right after a reboot and fix common problems hasn't run yet: May 1 18:54:28 Tower root: Delaying execution of fix common problems scan for 10 minutes

You can't use WireGuard to join two networks that have overlapping subnets. So if one is 192.168.1.x and the other is 192.168.2.x then you are fine (assuming the subnet mask on both is 255.255.255.0). But if both networks use 192.168.1.x then you can't join those networks. In that case you can use the "Remote Access to Server" option and connect to the server via the server's tunnel ip. You will have access to the server only, nothing on the remote network.

You have a myunraid.net certificate, which uses URLs in the format: https://[ip-address].[hash].myunraid.net If eth0 does not have an IP address, nginx is unable to start because it can't generate a server name for that URL. So we see this in your syslog: May 29 00:47:53 Talonhawk root: Starting Nginx server daemon... May 29 00:47:53 Talonhawk root: nginx: [emerg] invalid number of arguments in "server_name" directive in /etc/nginx/conf.d/servers.conf:63 For now, please make sure eth0 has an IP address. This shortcoming will be addressed in 6.12.

When signed in at the terminal, type `diagnostics` and note where it stores the zip file on your flash drive. Then attach that file to your next post here.

This is flash backup error message, right? Your flash backup is corrupt. To fix that, on the Settings -> Management Access -> Unraid Connect page, choose the "Deactivate" option (and delete from remote) then "Activate" to start fresh.

There were significant changes to how SSL is handled between 6.9 and 6.10, and the meaning of "Auto" changed, which is why it was renamed to "Strict". So at this point you are on 6.11.5 and SSL is working as expected? If you would like to reach more about SSL in 6.11.5, see: https://docs.unraid.net/unraid-os/manual/security#securing-webgui-connections-ssl

One of the issues with the previous system is that we made assumptions about what URL would work from your current location. Depending on how your network is configured and whether you are using VPN, http://ted.local may or may not work and the Connect Dashboard doesn't have a way to know for sure. So we display all the options and let you pick. Perhaps we can give you the option to "remember" the choice down the road, but that complicates things because we'd also need a way for you to "forget" the choice. The best way to use this is to provision a myunraid.net certificate. Once you do that, client side code on the Connect Dashboard can query your myunraid.net URL and see if your browser can access it. If so, the Connect Dashboard will automatically use that URL. You say you have already provisioned a myunraid.net url, interesting. Would you please upload the diagnostics.zip from Tools -> Diagnostics on one of your systems that has a myunraid.net certificate? Also, please open a web terminal and run this command, then copy/paste the output here: unraid-api report -v

This system is having general networking trouble unrelated to Unraid Connect, I'm going to move this to General Support so that more people will see it. Note there are also a lot of btrfs errors May 22 03:00:14 ThoNAS kernel: I/O error, dev loop2, sector 32776576 op 0x0:(READ) flags 0x1000 phys_seg 2 prio class 0 May 22 03:00:14 ThoNAS kernel: BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 119, rd 214, flush 0, corrupt 0, gen 0 If it were my system I would probably reboot to see if it is any better, but you might want to wait for more advice.

I think you might have missed this from the first post: Also, you are getting a warning that your local endpoint doesn't resolve to Unraid's WAN IP. I'd really recommend investigating that, the the port forward doesn't matter if the local endpoint doesn't point to your router.

Hi @YsarKain, it is very likely that one of the config files on your flash drive is corrupt. Replacing the flash drive is a good first step but the problem will remain if you copy a corrupt file from the old one to the new one. Please see my comment here to send us the info we need to figure out which file on your flash drive is corrupt: https://forums.unraid.net/topic/134517-cannot-read-properties-of-undefined-reading-tolowercase/#comment-1263126

I'd recommend following the instructions here: https://wiki.unraid.net/Connect#Remote_Access_.28optional.29 if you get stuck, let me know what step you are on. i.e. describe what you have done so far and what isn't working. Note that some routers don't let you use different WAN and LAN ports for a port forward. In that case I'd recommend using a high random port for both.

When you make a change to the URL used to access Unraid, you need to make a corresponding change to your Cloudflare config. Although I wouldn't say this is "supported", here is what worked for me: When Unraid's "Use SSL" setting is "no", then the CF Public Hostname should point to http://<ipaddress> When Unraid's "Use SSL" setting is "yes", then the CF Public Hostname should point to https://<ipaddress> and CF's TLS -> No TLS Verify option should be enabled. When Unraid's "Use SSL" setting is "strict", then the CF Public Hostname should point to https://<ipaddress>.<hash>.myunraid.net and the same <ipaddress>.<hash>.myunraid.net hostname should be added to CF's HTTP Settings -> HTTP Host Header. Note that when accessing the server via the Cloudlflare URL, you will see a message that says "The CORS policy for this site does not allow access from the specified origin", with more detail being shown on Settings -> Management Access -> Unraid Connect. We plan to let you add custom URLs to the allowed origins in the future but that hasn't been implemented yet.

Thanks @Hoopster, really nice to hear that the fan is quiet. Appreciate your advice here. I don't know if you remember, but we both have nearly the same Lian Li system too. It is that 9 year old system that I am looking at replacing, the BMC stopped responding and I'm having other issues that look hardware related. It had a good run. @Riverhawk thanks for the parts list, it looks awesome. I'd love to see pics of how it all fits into the Rosewell case if you'd like to show that off : ) Do you have room to add a GPU down the road? Also, how you feel about the noise?

Thanks for working through that @daddyfatsaks This was very enlightening, the reason we were never able to reproduce this is that it only happens when a config file on the flash drive is corrupted or has an unexpected value. When Unraid read this line of your config: shareNFSEnabled="y%s" it said "'y%s' is not 'yes' so I will treat it as 'no'", but when the API read that line it said "I don't know what 'y%s' means so I will throw an error". This is why Unraid itself didn't have any issues with the corrupt value but the API did. We will update the API so that it falls back to the same defaults that the OS does when there is an unexpected value in a config file. In the meantime, if anyone else has this problem we need to review your Unraid API logs and config data to see where the corruption is. This may have sensitive data, so rather than post it publicly please create a support request here: https://unraid.net/contact Watch for an email saying your case was created, reply to it with the info below. First, go to the Plugins tab and check for updates to ensure you are on the latest version of Connect. Then to Settings -> Management Access -> Unraid Connect and download your unraid-api logs, and attach those to your reply. Also open a web terminal and run: cat /usr/local/emhttp/state/var.ini and copy/paste the results of that into your reply. With this we should be able to tell which file has the corruption and help you recover from it.

You have configured Unraid to use port 84 for both http and https traffic, this will not work. They need to be on different ports. The defaults are: HTTP port: 80 HTTPS port: 443 The only reason to change the defaults is if you want to run Docker containers on those ports. On your flash drive there is a config/ident.cfg file. Edit that and change these entries so that they are unique on the system and do not conflict with any Docker containers: PORT="84" PORTSSL="84" After doing that, run: /etc/rc.d/rc.nginx reload Or restart the server

What a great thread, thanks! I'm looking for a 4U rack mount case as well. The Rosewell was at the top of my list but then I found the Sliger CX4712, anyone have thoughts on this? https://sliger.com/products/rackmount/4u/cx4712/ I had been looking at the ASRock board but I was bummed that it only has one M2 NVMe slot. Would really prefer to have redundancy on the cache drive. Thanks for that Supermicro board, it has 3 M2 NVMe slots and more PCI slots too. nice. I'd need to use one of them for a 10GbE nic but that's ok. Either way, I like the W680 chipset because it supports ECC RAM. And both have 8 SATA ports without an HBA which is nice. I was planning on water cooling the CPU to help with noise, but I'll take a look at that Noctua fan too. Have you done any research on noise for that Noctua? I also have an RTX 3080 that will add to the power and heat dissipation requirements of this system. Have you pulled the trigger on this yet @Riverhawk or @Hoopster ?

No, the OS reports the IPv6 link but the back end isn't in place to support it yet.

You can see the FCP code here: https://github.com/Squidly271/fix.common.problems/blob/ce84e87f79caaf750bc84a16f7ecdb93561f4cec/source/fix.common.problems/usr/local/emhttp/plugins/fix.common.problems/include/tests.php#L714 If this file exists on your flash drive it will trigger that message: /boot/config/vsftpd.user_list It looks like when you go to Settings -> FTP Server and remove the users, it empties the file but does not delete it. The FCP test could be updated to ignore a file with no data. In the meantime you can get rid of the message by deleting the empty config/vsftpd.user_list file from your flash drive.

Glad you are liking it! For best results, go to Settings -> Management Access and provision a myunraid.net certificate. That plays very nicely with Connect.

It appears that something on your network is preventing the server from downloading this file: https://sfo2.digitaloceanspaces.com/unraid-dl/unraid-api/dynamix.unraid.net.plg You can manually backup the flash drive by going to Main -> Boot Device -> Flash -> Flash Backup

How many network cards does this system have? The network.cfg thinks it has 12 ?!?! # Generated settings: IFNAME[0]="GATEWAY6:1" DHCP_KEEPRESOLV="yes" DNS_SERVER1="127.0.0.1" DNS_SERVER2="172.52.52.1" DHCP6_KEEPRESOLV="no" IFNAME[1]="GATEWAY:1" IFNAME[2]="IPADDR6:1" IFNAME[3]="IPADDR:1" IFNAME[4]="METRIC6:1" IFNAME[5]="METRIC:1" IFNAME[6]="NETMASK6:1" IFNAME[7]="NETMASK:1" IFNAME[8]="PRIVACY6:1" IFNAME[9]="USE_DHCP6:1" IFNAME[10]="br0" BRNAME[10]="br0" BRSTP[10]="no" BRFD[10]="0" DESCRIPTION[10]="work" BRNICS[10]="eth0" PROTOCOL[10]="ipv4" USE_DHCP[10]="yes" DHCP_KEEPRESOLV="yes" DNS_SERVER1="172.52.52.1" DNS_SERVER2="10.128.0.1" USE_DHCP6[10]="yes" DHCP6_KEEPRESOLV="no" MTU[10]="1500" IFNAME[11]="br1" BRNAME[11]="br1" BRNICS[11]="eth1" BRSTP[11]="no" BRFD[11]="0" DESCRIPTION[11]="cat_and_dog" PROTOCOL[11]="ipv4" USE_DHCP[11]="yes" MTU[11]="1500" SYSNICS="12" It looks like this file may have been edited manually because I see some duplicate entries. I'd suggest that you delete config/network.cfg from the flash drive and reboot. The system should pick up a new IP on eth0 from DHCP. Then go to Settings -> Network Settings, make a dummy change and hit save to generate a new network.cfg and start testing things from there.

Hi folks, please update to today's release: https://forums.unraid.net/topic/138392-unraid-connect-plugin-announcements/#comment-1257785 It should be impossible to see this message any longer: "cannot read properties of undefined (reading 'tolowercase')" but I am not sure what it will be replaced with as we have not been able to reproduce this. If you continue to have issues, please go to Settings -> Management Access -> Unraid Connect and see the new section on how to download and submit logs. Once we have the logs we should be able to get to the bottom of this.

This area of the forum is for support with Unraid Connect specifically. As you are having general networking issues, please start a new thread under General Support where a lot more people will see it.