bonienl

Port 443 is used by the GUI, your container can not use the same port.

I have seen some users who disable ipv6 in their 'go' file, using a command like this: --sysctl net.ipv6.conf.all.disable_ipv6=1 or echo 1 > /proc/sys/net/ipv6/conf/all/disable_ipv6 You need to remove these lines because it conflicts, Unraid takes care of enabling / disabling IPv6 per interface as configured

Like to see diagnostics

SSH works fine for me using Wireguard. There are no specific rules for wireguard tunnels to stop SSH.

In the past I have seen VMs and containers using the same bridge interface may cause problems. Best to use the interface as a dedicated interface for docker only.

It is not advised to do manual changes, any configuration update thru the GUI will undo them.

That indicates something is wrongly configured in your network settings. Need diagnostics to see this.

These are instructions when using docker containers, the plugin version of tailscale is started before the array comes online and doesn’t need the script.

Please also read the release notes of Unraid 6.12.0 which have more information about remote access.

See I encourage everyone to read the release notes of Unraid 6.12.0.

Changed Priority to Annoyance

macvlan call traces impact the complete system. Your situation is a bit weird. I studied your first diagnostics and everything looks alright. There is nothing in the logs which explains a loss of communication.

If using macvlan in docker settings, change it to ipvlan

Yours is a different issue, please open a topic in support and include diagnostics

In your latest log there is a macvlan call trace, change docker settings to use ipvlan instead.

Sometimes Windows gets confused. Did you try to reboot your Windows system? In all my tests SMB is working fine in 6.12.2

ip rule add sport 22 table This is not a standard rule and not included, how is this added to the configuration?

All, We need diagnostics for further investigation.

IPvlan operates in a mode which shares the same MAC address amongst multiple IP addresses. It seems to me that the Fritzbox can not handle that, it apparently wants to act on unique MAC addresses when doing port forwarding. Can the Fritzbox act on IP address instead? A couple of workarounds: 1. If you don't use VMs then the 'bridge' function is not needed on eth0 and you can use MACvlan directly on the interface, which doesn't cause call traces in my testing. 2. Use docker containers on a dedicated interface (eth1) with no IP addresses assigned and again no bridging enabled for this interface. This separates docker communication completely from system communication.

Please test in safe mode without plugins installed.

Changed Status to Retest

None of these issues can be replicated. Below a screenshot of the dashboard in firefox at a resolution of 1920 x 1080. - 3 columns are displayed - Header is displayed without scrollbar - No CSS errors Note: this is a plain firefox installation without any extensions or customization. Have you tested in safe mode? I notice your scrollbars are much wider than they should be. Any customization done to firefox?

Clear your browser’s cookies.

Changed Status to Retest

There is a change in 6.12.2, due to new functionality, it requires a reset. Open the Tile Manager and reset the dashboard, after that all should work properly.