I have been getting this daily since fixing other issues brought up by upgrading to 6.12.x

seems resolve on its own after 10 - 60 minutes, no dockers have internet access, can't see apps page, cant ping out, etc.

If I use "unraid-api restart", I get a different error message, something about "cant connected to mothership", but the issue persists until it decides to go away.

I am running pfsense and pfblockerng but there is nothing in the logs there pertaining to anything from the unraid server being blocked, and firewall rules are set to pass the traffic. At least as far as I can tell, I obviously am doing something wrong since I'm having an issue.

syslog towerofdoom-diagnostics-20230626-2116.zip

I think I have the same issue. Are you saying that you can get into your webui but unraid itself cannot get out to the internet?

I fixed my issue. I browsed to /boot/config and renamed the network.cfg to network.cfg.old and rebooted. It forced unraid to recreate the file and now everything works.

14 hours ago, veritas2884 said:

I fixed my issue. I browsed to /boot/config and renamed the network.cfg to network.cfg.old and rebooted. It forced unraid to recreate the file and now everything works.

 

Thank you so much! This fixed the issue for me too. Only noticed it yesterday when I was actually trying to access my server from outside my network and have been fighting with it since.

23 hours ago, veritas2884 said:

I fixed my issue. I browsed to /boot/config and renamed the network.cfg to network.cfg.old and rebooted. It forced unraid to recreate the file and now everything works.

how. i did the same restartet and it didnt came up again...?

Edited June 29, 20232 yr by nuhll

On 6/28/2023 at 3:32 PM, veritas2884 said:

I think I have the same issue. Are you saying that you can get into your webui but unraid itself cannot get out to the internet?

Precisely, I did just downgrade to 6.11.5, and rebuilt the docker.img, and that took me from about 90% downtime to 5% downtime.

 

The issue isn't presenting itself currently, but if it does again I'll give your fix a try. Thanks!

I have a strange error, and I follow the suggestions above but it solve partially my problem.

Some one can help me please?

logs.gz

its crashed, restart.

On 6/29/2023 at 9:33 AM, veritas2884 said:

I fixed my issue. I browsed to /boot/config and renamed the network.cfg to network.cfg.old and rebooted. It forced unraid to recreate the file and now everything works.

This is all it needed thank you so much!

I have a Similar error, when I followed the renaming of network.cfg in the /boot/config folder to network.cfg.old and rebooted the system. After 10 minutes, it stiil has NOT created a new network.cfg.

Any help would be appreciated. 

 

Error:

Unble to connect to https://mothership.unrid.netCLOUD:
sooket closed

8 hours ago, LyndochAVs said:

After 10 minutes, it stiil has NOT created a new network.cfg.

This file only gets created if you go the network settings and make a change there.   Until then it simply uses default settings.

Thank you, everyone. My issue has been resolved. The general idea was to reset the network settings.

Thanks for this 👍