ljm42

The usual issue when your Internet connection goes down is that your clients are unable to do a DNS lookup on 192-168-86-202.hash.myunraid.net and therefore they can't reach the server. The server itself is not broken in this case, it is just that the clients can't reach it. This fix for this is to use a url that doesn't need to do a DNS lookup. Depending on your settings, you may need to disable SSL in order to use a url that doesn't need DNS. This is the process described here https://wiki.unraid.net/My_Servers#How_to_access_your_server_when_DNS_is_down Rebooting the server would have no effect on this as it is an issue with the client not being able to do DNS lookups. The server itself is fine. I have never encountered a situation where the the server stops responding when it loses Internet access. You'll need to start disabling things to track down the culprit. I'd start by booting in safe mode, which disables all plugins. If the server doesn't have issues when the Internet goes down in safe mode then you know a plugin is responsible for the issue. Another option would be to disable the Docker service to determine if one of your Docker containers is causing the problem.

What exactly starts working when you restart the server? And then what makes it stop working? Once you get access to the server please upload your diagnostics.zip file (from Tools - Diagnostics)

BTW, back on step one... I see you tried accessing the server by IP address, are you sure the IP address didn't change? The instructions recommend using https://[servername].[localTLD] because there is a good chance that will work even if the IP address changed. The default servername is "tower" and the default Local TLD is "local". So if you are using defaults the url for step one would be: https://tower.local or https://tower.local:SSLPORT

OK so you tried the first step: If Use SSL/TLS is set to Yes, then you can access your server using: https://[servername].[localTLD] or https://[servername].[localTLD]:<https_port> (if your https port is not the default of 443) Since that didn't work, now you need to move on to step two: If that doesn't work, or if Use SSL/TLS is set to Strict, then using telnet, SSH or local keyboard/monitor log in to the server and type: use_ssl no

It sounds like a DNS issue. Go to Settings -> Network Settings, delete any DNS servers listed and replace with 8.8.8.8 If you continue to have issues, be sure to upload your full diagnostics.zip file (from Tools -> Diagnostics)

Please follow the steps outlined here to access your server: https://wiki.unraid.net/My_Servers#How_to_access_your_server_when_DNS_is_down If you continue to have issues, please post the exact url you are trying and what the error message is

Sorry, it is very unclear what the problem is. Screenshots may help Now I'm really confused : ) if you can access the Management Access page, doesn't that imply you have access to the webgui?

Oof 6.9.2 is really quite old and does not have the improvements of later versions. It doesn't look like you have ssl enabled, so http://192.168.86.41 should work (http not https). If you have trouble with that, try restarting your browser. Otherwise, using SSH (or a local keyboard/monitor), type this to restart nginx: /etc/rc.d/rc.nginx reload Or this to reboot the server: reboot I highly recommend that you take advantage of the free upgrade policy and upgrade to the current version. 6.9.2 is no longer supported, and is quite out of date in terms of security patches (and features!) You'll want to backup your flash drive, then read the release notes here: https://wiki.unraid.net/Manual/Release_Notes Open a new thread in General Support if you have issues.

Please follow the instructions at that link. They do apply here. Once you have access to the webgui, go to Settings -> Management Access and get your new url.

No worries, it is a point of confusion we are working to improve

You need to access the My Servers dashboard from a remote location, then it will show the Remote Access url instead of the Local Access url.

On Settings -> Management Access be sure to set the "Local TLD" to "local", this will activate mDNS. Note that mDNS only works if your server and client are on the same subnet. If you still have issues you might need to research mDNS and see if something on your network is blocking it.

The Remote Access URL is different from the Local Access URL, and often has an a port even if the Local Access one doesn't. I'd guess that you were inadvertently trying to access the server on your LAN using the Remote Access URL. Anyway, glad you were able to get access.

Where did you get the bad link from? If it was a bookmark then it will go stale when things like ports change. If you have My Servers installed then you can get the current default URL from the My Servers dashboard: https://forums.unraid.net/my-servers/ Or you can go to http://ipaddress or http://servername.local and you will get redirected to the server's default URL. Once you are in, (on recent versions of Unraid) the Settings -> Management Access page will list out all the valid URLs for the server.

There is not a global problem. If you are having issues first step would be to follow the link you quoted to get access to your server.

That is completely unrelated to Unraid. WireGuard was originally built for Linux, which Unraid is based on. It is out of beta and has been accepted into mainline Linux. When WireGuard was first ported to FreeBSD (which pfSense is based on) there were serious issues and it had to be pulled. I believe those issues have now been resolved, but I don't really follow pfSense.

We have not been able to reproduce this problem. However, replacing the flash drive did solve it for this person: https://forums.unraid.net/topic/133952-migrated-to-new-hardware-cant-log-in-diag-included/#comment-1243178

I am not clear what state your server is in, but this will help you get access to the webgui: https://wiki.unraid.net/My_Servers#How_to_access_your_server_when_DNS_is_down When you are ready to setup Remote Access see: https://wiki.unraid.net/My_Servers#Configuring_Remote_Access_.28optional.29

It is in the url that you posted. ip.hash.myunraid.net Are you still having issues?

What version of Unraid is this? WireGuard has not been a plugin for a while. Here is a hint about Cloudflare from the WireGuard Quickstart post: https://forums.unraid.net/topic/84226-wireguard-quickstart/

The system had some small hiccups yesterday that may have disconnected you: https://status.unraid.net/792858507 Also if your Internet drops or your modem reboots you will get disconnected. The api is intended to reconnect automatically when these types of things happen, but there are still issues. We have some fixes identified for the next plugin release. In the meantime, `unraid-api restart` should get you back up running, just note that it can take some time for the api to reconnect. More detail here: https://forums.unraid.net/topic/136219-unraid-api-error-cloud-client-closed-connection/#comment-1241122

Right, from the text you quoted: You can think of the My Servers dashboard as showing you a list of your licenses. Since you had multiple trial licenses on different flash drives, they are all going to be listed until 30 days after they expire.

There is no way to disable the password requirement, so you'd probably want to come up with another way to serve those files

A root password has been required to access the webgui as of Unraid 6.10.0: https://wiki.unraid.net/Manual/Release_Notes/Unraid_OS_6.10.0 Since this url is served by the webgui, the root password is required to access it: http://1.2.3.4/mnt/user/SHARE/PATH/TO/FILE.xml This is working as intended.

I'd suggest posting the exact message from your firewall (also, what firewall is it?) as well as your diagnostics.zip file (from Tools -> Diagnostics)