Unraid is inaccessable after an internet outage

[mrclean5953]

I'm sorry If this has already been asked, I've been searching through the forum and tried a few things but nothing seems to be working.}

My ISP has been doing some upgrades overnight and in the morning the unraid sever is inaccessible. Any suggestions on how to fix this?

Also, with the server being inaccessible how am i supposed to safely reboot the server?

[JonathanM]

https://wiki.unraid.net/My_Servers#How_to_access_your_server_when_DNS_is_down

[mrclean5953]

On 4/8/2023 at 12:52 PM, JonathanM said:

https://wiki.unraid.net/My_Servers#How_to_access_your_server_when_DNS_is_down

This didn't work, I'd like to add that my issue is AFTER an outage not during an outage

 

Edited April 11, 2023 by mrclean5953

[JonathanM]

What address are you using to access the server?

[mrclean5953]

6 hours ago, JonathanM said:

What address are you using to access the server?

I'm trying all the ones listed on the management access page

[ljm42]

7 hours ago, mrclean5953 said:

This didn't work, I'd like to add that my issue is AFTER an outage not during an outage

 

 

Sorry, it is very unclear what the problem is. Screenshots may help

 

  

13 minutes ago, mrclean5953 said:

I'm trying all the ones listed on the management access page

 

Now I'm really confused : ) if you can access the Management Access page, doesn't that imply you have access to the webgui?

[mrclean5953]

9 minutes ago, ljm42 said:

 

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?

The internet has been dropping at my house, by the time I get home my internet is back up and running, but I cannot access the unraid server without rebooting it.

 

I can't access the management access page. I copied all the listed addresses and have tried them all. 

[ljm42]

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

[mrclean5953]

1 minute ago, ljm42 said:

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

I've already done this

 

[ljm42]

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

[ljm42]

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 

[mrclean5953]

2 hours ago, ljm42 said:

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 

I've got a static ip set in the router. I was also trying tower.local and tower.local:sslport

 

I had to restart the server manually as nothing was getting me in. I also checked the router and the server wasn't being seen but the router. 

[ljm42]

2 hours ago, mrclean5953 said:

I had to restart the server manually as nothing was getting me in.

 

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)

[mrclean5953]

10 hours ago, ljm42 said:

 

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)

After a reboot absolutly everything works.

What makes it stop working is my ISP has been having some issues with the internet dropping off and after an hour or so of the internet being down the server then becomes unresponsive. Once I get home the internet is back online but the server is unresponsive

tower-diagnostics-20230412-1025.zip

[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.

[mrclean5953]

On 4/12/2023 at 12:17 PM, ljm42 said:

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.

I disabled the docker container binhex-qbittorrentvpn and all my issues went away

[ljm42]

Glad you were able to find the cause

[psycmos]

Hello.
I'm getting the same issue.

Somebody can give me the issue?

contimaciva-diagnostics-20230818-1017.zip

[JorgeB]

21 minutes ago, psycmos said:

I'm getting the same issue.

Everything looks normal to me, can you access the server using the IP?

 

Aug 18 10:10:12 [927]: br0: leased 192.168.0.162 for 3600 seconds

 

Make sure you enter http first since most browsers now default to https

[psycmos]

6 hours ago, JorgeB said:

Everything looks normal to me, can you access the server using the IP?

 

Aug 18 10:10:12 [927]: br0: leased 192.168.0.162 for 3600 seconds

 

Make sure you enter http first since most browsers now default to https

Yes for now i can acess to server IP, but in some hour/ or 1 ou 2 days i will lost the access, until force shutdown.
Thar are any way to get the register log about this event?

[JorgeB]

39 minutes ago, psycmos said:

Yes for now i can acess to server IP, but in some hour/ or 1 ou 2 days i will lost the access, until force shutdown.

That's a different issue, enable the syslog server to see if it catches anything.

[sbeex]

I face exactly the same issue  and sorry this is pretty easy to reproduce.
 

1) have unraid up and running
2) disconnect your internet cable
3) unraid ip is unavailable via the http://ip (even on the local network.. why does it stop..)
4) reconnect the internet cable
5) unraid is still unreachable...
6) reboot the unraid machine 
7) it works.

I have two unraids servers with fixed IP address defined by the router. Both have the same issue.

I can also confirm that my synology do not have this issue and also have a fixed IP. So the issue is probably due to something within unraid.

Could it be related to some containers trying to actively access internet ? (I was thinking maybe it would prevent unraid somehow to "reset the connection" as they keep trying over and over to reach internet ?

Any help is welcome as it's quite a pain... I get my internet from mobile antennas and it happens at very least once a week that I have a 5 sec outage.

Thank's a lot!

[Mainfrezzer]

Sound highly like a powertop --auto-tune issue

[sbeex]

6 minutes ago, Mainfrezzer said:

Sound highly like a powertop --auto-tune issue

 

Ok if that helps I didn't do any kind of optimization for the power usage.

[Mainfrezzer]

Just now, sbeex said:

 

Ok if that helps I didn't do any kind of optimization for the power usage.

huh, if thats the case, diagnostics certainly would be needed, once that issue occurs. given that youll need physical access to the server once it happens or you trigger a reboot, syslog server needs to be setup beforehand

That behavior is usually pretty common with powertop. it just simply turns the nic of, once theres no more network activity and never turns it back on.