ljm42

If Unraid is using a 10G nic for it's main connection to the network, then all docker containers and VMs will benefit from the 10g speeds. You would be sharing a bridged connection with the VM rather than doing passthrough (passthrough means Unraid doesn't use the device, but passes it through to the VM to use) I would not expect a difference in speed between an onboard 10G nic and a PCIe 10G nic. Having it onboard would be nice because it saves a PCIe slot. The question is whether Unraid has drivers for the onboard nic, I did a search for "Unraid Marvell AQtion AQC113CS" and found this which looks promising: https://forums.unraid.net/topic/73730-aquantia-aqtion-10g-pro-nic/ As to whether the various features of your motherboard can be passed through to a VM, it depends on the motherboard and whether those features are isolated into their own IOMMU group. IOMMU groups are shown on the Tools -> System Devices page, but you won't see that until you have built the system You might try searching "Unraid [motherboard name]" to see what other people have said. Note that sometimes the initial release of a motherboard doesn't have good support for this and a BIOS update resolves it.

Does reloading nginx give better results? /etc/rc.d/rc.nginx reload

Please open a web terminal and run this command, then paste the results back here: ssh -v -T [email protected]

Your DNS server is not resolving the hash.myunraid.net url. Go to Settings -> Network Settings and remove any static DNS server that might be set. Replace it with 8.8.8.8

Sorry for the trouble. I am aware of two systems that are getting this "toLowerCase" problem, we are still tracking it down. It will take a plugin update to resolve, if this is causing issues for you, you might want to uninstall the My Servers plugin for now.

Sorry for the trouble. I am aware of two systems that are getting this "toLowerCase" problem, we are still tracking it down. It will take a plugin update to resolve, if this is causing issues for you, you might want to uninstall the My Servers plugin for now.

Sorry for the trouble, we are having intermittent issues with My Servers Cloud (aka mothership) today, you can check the status here: https://status.unraid.net/ My Servers is an optional add-on to Unraid; the rest of your system is not affected.

Sorry for the trouble, we are having intermittent issues with My Servers Cloud (aka mothership) today, you can check the status here: https://status.unraid.net/

This is unrelated to My Servers, please see https://unraid.net/blog/ssl-certificate-update-2 Side note: Once that is resolved, I'd recommend upgrading to Unraid 6.11.5, it has many bug fixes and improvements over 6.11.0

You can just use the IP. Or if that changes a lot then a duckdns url would be a good choice. If WireGuard is setup on your server then when you are away from your house you would open a WireGuard tunnel back to your house and access the resources at your house as though you were there.

Hi, sorry I didn't see this earlier. Let me start with this - if your only goal is to setup WireGuard then you don't need a myunraid.net certificate. They are not related, neither is required for the other to work. This is not correct. I would remove all three DNS servers you currently have setup and simply use 8.8.8.8 as the one and only DNS server. Cleaning up the DNS servers may be enough to resolve this. If not, please provide updated diagnostics.

You need to set the "Peer type of access" to "Remote tunneled access". Try accessing a WAN address by IP and see if the issue is the connection or if it is DNS. If the issue is DNS, set the "Peer DNS Server" to 8.8.8.8 and get that working before you try setting it to the pihole. And don't forget to update the client every time you edit the wireguard tunnel on the server.

Open a web terminal on your server and run this: wget --output-document - https://mothership.unraid.net then paste the output back here.

Right, the port is part of the allowed origin check so it is currently blocked. In a future update you will be able to custom urls (including ports) to the list of allowed origins.

Are you using a reverse proxy? We will be adding support for adding reverse proxy urls to allowed origins in a future update. If you aren't using a reverse proxy then you may just need to adjust your servername and Local TLD settings so the urls match.

Are you behind a firewall? It seems that something is blocking your server's ability to connect to https://mothership.unraid.net . This is very unlikely to be an Unraid setting.

The My Servers plugin provides Remote Access to the webgui only. If you need to access your Docker containers remotely you'll need to use a VPN. Unraid has WireGuard VPN built-in: https://forums.unraid.net/topic/84226-wireguard-quickstart/

Sorry for the delay. So I have to admit, I don't see any issues in these logs. I don't think the My Servers plugin is the cause of your issues on the dashboard, but if you want to rule it out you can uninstall it. When the dashboard isn't showing data, it may help to open a web terminal and run: /etc/rc.d/rc.nginx reload

Yes we didn't call it out in the release notes but the current version does make some improvements here.

This thread is from a few versions ago so things have changed a bit. Please make sure you have the latest version of the plugin and then post a screenshot of your issue

Please open a web terminal and run: unraid-api restart Then wait 30 seconds and reload the webgui. Does that solve it?

BTW if the automatic detection picks the wrong card as eth0, you can navigate to Settings -> Network Settings -> Interface Rules and adjust things until the right nic is eth0

If you are using My Servers Remote Access, change the WAN port. You want something random between 1000 and 65000, see https://wiki.unraid.net/My_Servers#Configuring_Remote_Access_.28optional.29

Please see https://unraid.net/blog/ssl-certificate-update-2

Your config/go script has some old code for handling ssh, you should remove all of this: mkdir /root/.ssh cp /boot/config/ssh/* /root/.ssh/ cd /root/.ssh chmod 600 * #Copies all files needed for authorized ssh connections mkdir /root/.ssh cp /boot/config/ssh/* /root/.ssh/ cd /root/.ssh chmod 600 * /root/.ssh/ is a symlink to /boot/config/ssh/root/ so any files that you want to persist should be placed in /boot/config/ssh/root/ Nothing else stands out to me, I'd suggest installing the Fix Common Problems plugin and see if it highlights any issues.