ljm42

To start, I'd recommend upgrading to 6.11.5. It has many improvements over 6.11.0. For #1, it is not clear what your users are trying to login to. Note that only the "root" user can login to the webgui. For #3, after upgrading to 6.11.5, please provide the *exact* urls you are having trouble with, including whether they are http:// or https:// . Also updated diagnostics in the new version.

Sorry for the trouble. I would fully expect "unraid-api restart" to resolve this. It takes a bit to reconnect, so wait at least 30 seconds and then refresh the page to see the new status.

You can download the latest backup the My Servers plugin made, but not historical backups. See: https://wiki.unraid.net/My_Servers#Restoring_Flash_Backup

Not a lot to go on here, but perhaps WG0 is setup as "VPN tunneled access for system"? Assuming you are on a recent version of Unraid, there is a “VPN tunneled access for docker” that you probably want instead. see https://forums.unraid.net/topic/84316-wireguard-vpn-tunneled-access-to-a-commercial-vpn-provider/

The only time the Unraid cloud sends incoming traffic to your firewall is if you press the "Check" button when setting up Remote Access. It will only hit the "WAN Port" you specified, not random ports. If the API is currently offline you can open a web terminal and run: unraid-api restart to reconnect. Watch your firewall logs while doing that and adjust any outgoing firewall rules to allow the traffic to pass.

AFAIK mDNS only works on the local network

I'd recommend either connecting by IP address, or using an FQDN that resolves to a local IP, such as the myunraid.net url Unraid provides: https://wiki.unraid.net/Manual/Security#Securing_webGui_connections_.28SSL.29

When in "Remote Access to Server" mode, you can't access the server by name or network IP, you need to use the server's IP on the WireGuard tunnel. The webgui will give you a "remark" telling you what the IP is: That is likely the mode you want, as it will give your guests access to your server and nothing else. Note: there is not an option for "just the server + the whole Internet". If you want to give them the Internet then you give them your LAN too. For more information about setting up WireGuard please see https://forums.unraid.net/topic/84226-wireguard-quickstart/

Please see this post: https://unraid.net/blog/ssl-certificate-update-2 If you have follow up questions be sure to mention what version of Unraid you have

.local domain names are typically just available on the local network, MDNS does not resolve over VPN. So over VPN you would want to connect by IP address A 404 for http://ipaddress doesn't make a lot of sense. So either your browser is being "helpful" and upgrading you to https (which *would* throw a 404 for your settings) or maybe SWAG is getting in the way. How about disabling SWAG while testing just to rule it out. With SWAG disabled, please show a screenshot of your browser accessing http://ipaddress (not https!) along with the error message

You are unable to use the ip.hash.myunraid.net url because DNS rebinding protection is enabled on your network. You may be able to get around this by using 8.8.8.8 as your DNS provider, or you may need to Google "disable dns rebinding [your router name]" Based on your settings, these urls should work: http://192.168.30.138 http://Tower.local Note: You need to specify the "http" part or your browser might try using https instead, but that is not enabled. If you have further questions please provide the exact url you are using, including the http:// or https:// part For more information about enabling SSL, see https://wiki.unraid.net/Manual/Security#Securing_webGui_connections_.28SSL.29

Do you have a pi-hole or firewall that could be interfering with communications? If so, watch the log on that device while you try to sign in and see if anything is blocked.

Sorry, I was referring to the first part of your comment which was that eth0 and eth1 were swapped. That could have been fixed on Settings -> Network Settings -> Interface Rules rather than physically removing the nic. Once the nic has been removed and eth0 has gone missing, then deleting the file and rebooting is the best way forward.

You should not need to modify network-rules.cfg manually. Go to Settings -> Network Settings -> Interface Rules and set the correct nic as eth0, then reboot. That will manage the network-rules.cfg file. Once Unraid is no longer using the onboard nic, you can go to Tools -> System Devices and bind the onboard nics to VFIO. That hides them from Unraid and makes them always available to be passed through to a VM.

My Servers does not currently support reverse proxies. The ability to add custom domains to the My Servers client's allowed origins will be coming in the future. In the meantime you will be able to use the Unraid webgui from an unconfigured url, just not My Servers related features.

Thanks for the log, nothing there looks related to us. You can test whether PiHole is the issue by fully disabling it and seeing if things change. But before doing that, see this thread: https://forums.unraid.net/topic/134859-server-showing-offline-logoutlogin-on-plugin-fixes-temporarily/#comment-1228284

There is currently an issue where if you have a momentary Internet problem the API will get disconnected but it won't realize it, so it doesn't try to reconnect on its own. There are two workarounds: First I would open a web terminal and run: unraid-api restart Wait 30 seconds, if you are still having issues then the second workaround is to sign out and sign back in. We should have this resolved in our next release. FYI - Remote Access is an optional feature and is not required for your server to show as online.

For WireGuard you can just use your wanip, or there is a DuckDNS container you can use for DDNS. No ETA at the moment.

We don't have a solution yet, but there is a work around. Depending on how many disks your files are spread across this may or may not be viable. Go to Settings -> Global Share Settings and set Enable Disk Shares to Yes. Then go to Shares -> Disk Shares -> diskX and set permissions so only you can access them. Then connect directly to the diskX share(s) and delete files that way, there will not be a warning. But please... NEVER EVER copy/move files between a user share and a disk share. Always go user share to user share or disk share to disk share. If you mix and match it is very easy to make a mistake and overwrite a file with itself, which results in a zero byte file. This is why disk shares are disabled by default. ... The fact that this only affects deletions from user shares is a good hint to us about where the bug is, but we don't have it solved yet. The bulk of development efforts are currently focused on ZFS so I would not bet on this being fixed in the first release of 6.12

Thanks. The issue is not on your end, there is a problem with the DNS entry that we need to resolve. For now continue to use one of the "Local Access" urls listed on the Settings -> Management Access page

To solve the My Servers disconnection error, open a web terminal and run: unraid-api restart Wait about 30 seconds, then reload the page. The other issue is unrelated, you may be able to solve it from a web terminal by running: /etc/rc.d/rc.nginx reload

good summary

Please run this command and send the results to me in a DM, I need to see the full url the system is trying to use: php /usr/local/emhttp/plugins/dynamix/include/UpdateDNS.php -vv Be sure to include a link back to this thread so I have context

Please open a web terminal and run: unraid-api restart Wait 30 seconds, then refresh the page

See the link John_M posted a few comments back