bonienl

By design ... of course First the webGui pages are loaded and then the additional plugin pages. This allows any plugin to either add or replace functionality.

This only applies to page files, but the customized page can refer to a customized version of a script in the include folder of your plugin.

The proper way to replace a stock page with a customized page is to give the customized page the same name as the stock page and store this under your plugin folder. When the GUI is loaded, it will automatically overwrite the stock page with the customized page.

Stop the Docker and VM services (see settings) Now under Network settings change the DNS settings to use a single server (start with 8.8.8.8)

Sorry, I was mixing up things. In case of a host network your DNS settings are okay. I am puzzled why it isn't working.... maybe change your DNS to a single entry and see if that works?

Inside a container, you should see something like this root@b142de55abf9:/# cat /etc/resolv.conf nameserver 127.0.0.11 options ndots:0

Your "mothership" is alright Container syntax is cat /etc/resolv.conf

Two things to check first Open a terminal session and type cat /etc/resolv.conf Open a console session of the container and type cat /etc/resolv.conf Post the results.

Switch to advanced view I expect no DNS setting here (extra parameters)

Do you have the "--dns" parameter set for this container (see extra parameters field in advanced view) ?

I don't see anything wrong in your network settings. A minor thing, you have enabled IPv6 but your router is not giving out IPv6 addresses, though this should not be an issue. You can use the 'console' function of the failing container and do the following. What is the result? ping 8.8.8.8

Post a screenshot of your network settings

Your diagnostics tell otherwise. # Generated settings: IFNAME[0]="eth0" PROTOCOL[0]="ipv4" USE_DHCP[0]="no" IPADDR[0]="10.10.1.233" NETMASK[0]="255.255.255.0" GATEWAY[0]="10.10.1.1" DNS_SERVER1="10.10.1.1" DNS_SERVER2="8.8.4.4" DNS_SERVER3="8.8.8.8" USE_DHCP6[0]="yes" DHCP6_KEEPRESOLV="no" IFNAME[1]="eth1" PROTOCOL[1]="ipv4" USE_DHCP[1]="no" IPADDR[1]="10.10.1.234" NETMASK[1]="255.255.255.0" GATEWAY[1]="10.10.1.1" SYSNICS="2"

You have configured two interfaces eth0 and eth1 in the same network. This is not recommended as it may give asymmetric traffic flows, something your firewall will block. It you want redundancy, change enable bonding for interface eth0 and add eth1 as a member.

The container is set to use the host network, which means it is directly accessing the interface, similar as Unraid itself. When Unraid has network/internet access so should have the container. Do you have any other containers running or configured with the same ports 8080 or 8090?