Holyhobgoblin Posted June 11 Share Posted June 11 Howdy peeps Been trying to install unRaid Connect over last few days and to update some dockers. This is from the output window when trying to install unRaid Connect "plugin: downloading: dynamix.unraid.net.plg ... done Executing hook script: pre_plugin_checks Installing dynamix.unraid.net.plg 2024.05.15.1138 with Unraid API 3.7.1 Checking DNS... ⚠️ Do not close this window yet plugin: downloading: unraid-api-3.7.1.tgz ... 15% plugin: unraid-api-3.7.1.tgz download failure: Network failure Executing hook script: post_plugin_checks" It download 15% then just stopped. I've also noticed the Community Applications/Apps tab states the follow "Backup Server Active. Some icons may not appear, and plugin installations may be affected" I assume there is an issue with Community Applications server or could this be my end? Any help would be appreciated. Thanx Quote Link to comment
JorgeB Posted June 11 Share Posted June 11 Could be on your end, post the output of: ping google.com Let it run to at least 50 tries, to make sure it's stable. Quote Link to comment
Holyhobgoblin Posted June 11 Author Share Posted June 11 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=6 ttl=116 time=16.3 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=7 ttl=116 time=15.4 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=8 ttl=116 time=15.6 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=9 ttl=116 time=15.7 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=10 ttl=116 time=15.8 ms I checked all my internet connection before posting and i cant see any issues I assume pinging google.com also comfirms my DNS is working? Quote Link to comment
JorgeB Posted June 11 Share Posted June 11 17 minutes ago, JorgeB said: Let it run to at least 50 tries, to make sure it's stable Quote Link to comment
Holyhobgoblin Posted June 11 Author Share Posted June 11 (edited) PING google.com (172.217.167.78) 56(84) bytes of data. 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=1 ttl=116 time=15.5 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=2 ttl=116 time=16.1 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=5 ttl=116 time=16.0 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=6 ttl=116 time=16.1 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=7 ttl=116 time=15.9 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=9 ttl=116 time=16.0 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=11 ttl=116 time=16.0 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=12 ttl=116 time=16.0 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=14 ttl=116 time=15.8 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=15 ttl=116 time=16.1 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=16 ttl=116 time=15.8 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=18 ttl=116 time=15.8 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=19 ttl=116 time=16.0 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=20 ttl=116 time=16.0 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=21 ttl=116 time=18.6 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=22 ttl=116 time=16.4 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=23 ttl=116 time=16.1 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=24 ttl=116 time=16.0 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=25 ttl=116 time=15.9 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=26 ttl=116 time=16.1 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=27 ttl=116 time=16.1 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=28 ttl=116 time=18.6 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=30 ttl=116 time=15.9 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=31 ttl=116 time=16.0 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=32 ttl=116 time=15.6 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=33 ttl=116 time=16.0 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=35 ttl=116 time=15.4 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=36 ttl=116 time=15.5 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=37 ttl=116 time=15.9 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=38 ttl=116 time=15.6 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=39 ttl=116 time=16.1 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=40 ttl=116 time=15.9 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=42 ttl=116 time=15.6 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=44 ttl=116 time=15.6 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=45 ttl=116 time=16.0 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=48 ttl=116 time=16.2 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=49 ttl=116 time=16.1 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=50 ttl=116 time=16.2 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=51 ttl=116 time=15.4 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=52 ttl=116 time=16.2 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=53 ttl=116 time=15.2 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=54 ttl=116 time=15.8 ms its missed one or two from the icmp_seq numbers ran it a bit longer here are the statistics --- google.com ping statistics --- 188 packets transmitted, 149 received, 20.7447% packet loss, time 409823ms rtt min/avg/max/mdev = 15.199/15.916/18.588/0.405 ms Edited June 11 by Holyhobgoblin Quote Link to comment
JorgeB Posted June 11 Share Posted June 11 22 minutes ago, Holyhobgoblin said: 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=2 ttl=116 time=16.1 ms 64 bytes from syd15s06-in-f14.1e100.net (172.217.167.78): icmp_seq=5 ttl=116 time=16.0 ms This should never happen if the network is networking correctly, it can happen if there are two devices with the same IP, make sure Unraid is set to DHCP, and there's nothing with a fixed IP in the DHCP range. Quote Link to comment
Holyhobgoblin Posted June 11 Author Share Posted June 11 Whilst looking into this issue i heard a loud bang outside, i accessed my security camera via my phone app. To my surprise i could not access the camera. Then it dawned on me the security camera and UnRaid share the same access point, last week i had air conditioning contractors in to install the new AC system. I suspect during the installation they have possibly damaged the Cat5e cable that feeds the Access Point. Looks like its time to start testing cables 1 Quote Link to comment
Holyhobgoblin Posted June 16 Author Share Posted June 16 Hi JorgeB Thanks for replying to my posts. Got it all working sweet now though i don't understand why i had issues. UnRaid has DHCP set to Auto and router gives it a static IP of 192.168.1.250 based on its MAC Address. I removed the static IP and rebooted server. Server now has an IP of 192.168.1.117 and still having the same issue and same issue with security cameras. Setup is as follows Router ------> 8 Port un-managed switch ------> Ethernet Lead to Wall Socket -------------> Wall Socket to Ethernet Lead --------------> 8 Port un-managed switch -------------> UnRaid |_____>Security Cameras Using an Ethernet cable tester, tested all cables between the 2 x un-managed switches and found nothing wrong, all cables good. I then reconnected everything and BOOM every working fine. I cannot explain this maybe a cable not pushed in properly is my best guess. So back to being and happy chappy. Again thank you for replying to my post. 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.