rjstott

Bonieni, Frank1940, Thanks for all that. I am going to say that as far as I can tell the edit has fixed the problem and we can now connect to the internet from core activities including updates and terminal! My curiosity is still asking what changed in the new releases to cause the problem. But we have at last moved on and I have an up to date release. For some reason none of the OS X file tags show up but although I religously set these I never found a good use!

Hi bonieni, I think to do this I have to remove the flash drive and edit the file through my Mac. Before I do this, there are two entries because there is an on board Realtek ethernet port and I have a PCIe network card with the Intel chip. There was some suggestion a long while back that the Realtel card was the issue so I added the Intel. As far as I can see eth1 is disabled (though where this setting is I don’t know). In any event there is currently no ethernet plugged into eth1 so it must be disabled? Additionally the Network.cfg file is identical between 6.6.7 and 6.7.7 so is there a difference between how the two versions use the .cfg data. I could believe that your suggestion could well fix this but being a curious old fart I like to know why? Any thought? Regards Richard

Tried again with the latest 6.7 release and same problem, internat access is gone. Someone on the unRaid team must know of changes to networking that might have caused the problem. I've gone back, again, to 6,6,7 and network access is working again. My diagnostice are on this thread! One more crumb, I'm fairly certain that internet access is working for Dockers. It just seems to be unRaid core functionality like updates and checking for them!

When I look in Network Settings the gateway is already set? Did you do something different.

Did a quick update again, same problems. Have attached the diagnostics from the 6.7.0.rc7. In the meantime I reverted back and its working again! tower-diagnostics-20190412-2155.zip

I saw that suggestion in another thread so I tried it even though it can't possbly solve the problem if the server won't ping 8.8.8.8. It would resolve a problem with named sites of course. It didn't work when I tried it. I have added the diagnostics but of course they are for the reverted 6.6.7 but I guess all the basic data should be the same between the two releases! I note that the 8.8.8.8 is still resident in the first DNS entry and I must remember to put it back to my SmartDNS setting! tower-diagnostics-20190410-1315.zip

I just upgraded to 6.7.0 rc7 and I lost internet access from unraid. The rest of my network is fine, I can access the GUI and I can ping my router from unraid. I can't ping 8.8.8.8 or any other internet address and some unraid functionality is lost such as docker updates (access to GitHub). A downgrade to 6.6.7 brings it all back! Any ideas?

I would but things have changed. Now I can login but the camera shows as "disconnected" and reports firmware not supported. Firmware v4.8.40 which is the camera? Docker is 3.9.11? I can not login to the camera so perhaps I will restart it when I next visit the site!

I'm having the same issue. It was working nicely and then it said there was an update which got it stuck as the update port isn't definable (7441?). So I reloaded the docker and then had endless problems as system.properties was missing and I'm guessing a simple typo has the wrong name system.propetties for recovery. Now I get stuck as above.

Just thought I'd update this thread. It is three days now without a problem so 'fingers crossed' I guess we should attribute this failure to the Realtek drivers in the latest releases. I can't honestly say the problem is solved because I've got around it by adding a replacement Ethernet card. I would also add that the Plex issue has also gone away. Just in case this is tripping anyone else up it manifests itself as either a reset of the the Plex client application (on my Samsung TV) or a network error stopping the media playing. No amount of changing the source of the material or how it was presented to the client fixed the issue. Now 1/11/2018 and no further failures. So the Realtek problem is I guess not fixed in 6.6.3 (at least for me)

I don't think we've proved the network card as the culprit yet have we? However, coincidentally my Plex problem has gone away and that did look like a network issue! Let's give it a couple more days. I hear what you say about Realtek but they are very common chips on Asus boards. I agree that fixing a Hackintosh problem which also runs on an Asus board did take a very long time!!

So here is an update. I upgraded the BIOS but it made no difference as far as I can tell. I still got a crash. (I can not say that all these crashes are identical but the symptoms are). So I have now added an Intel PCI network card as the main network interface and I guess the other interface is at least not being used. I am running 6.6.3 so I now need to wait and see. 48 hours was about the limit previously so we're at 7hrs and counting.

Second crash as before. Diagnostics attached. I have reverted to 6.5.3 meantime to check that this is still functioning reliably. I have a network card somewhere that may not be Realtek and I will put this into the server. How would I disable the Realtek card or do I just not connect ethernet to it? media-diagnostics-20181023-1036.zip

I'll bear that in mind but without any evidence that this would fix something that a roll-back wouldn't do I prefer the rollback? I have these errors in my log: Oct 20 19:26:39 Media nginx: 2018/10/20 19:26:39 [error] 13954#13954: *10747 readv() failed (104: Connection reset by peer) while reading upstream, client: 192.168.1.11, server: , request: "POST /webGui/include/DashUpdate.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.103", referrer: "http://192.168.1.103/Dashboard" Oct 20 20:22:44 Media nginx: 2018/10/20 20:22:44 [error] 13954#13954: *20244 readv() failed (104: Connection reset by peer) while reading upstream, client: 192.168.1.11, server: , request: "POST /webGui/include/Notify.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.103", referrer: "http://192.168.1.103/Dashboard" 192.168.1.11 is my iMac usually displaying the unRaid Dashbooard in Firefox whilst 103 is the server. Any ideas? As for now I'll leave the server on 6.6.2 unless crashes become more frequent. I could with some effort move my drives across to a spare system with a completely different motherboard. But that is a can of new worms too!

[6.2.2] Crashed (i.e. nor User acess via web interface and all server connections dropped) I have attached the diagnostics file but this is only since restart? At this point it seems identical to previous faills but I was moving a 12Gb file at the time! media-diagnostics-20181020-1824.zip