This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
Urgent: Cannot install applications + Access Web UI too long, and turn-off unit too long
Hi,
My uTorrent stopped downloading torrents.
I uninstalled, reinstalled it and finally tried a package I was using on my RNDU2000. It was a recent package with same 3.3 version as the one from Netgear app page. It was a deb package I got from super poussin dropbox, but it is no longer there now
After that, I couldn't uninstall uTorrent. I had to reboot and then uninstall could resume.
However, now, I cannot install any application from app pages. I get an error: Can't install application "app_name"
Uploading a deb package of teh app also fails to install
Also, since this issue:
- on boot, accessing the web UI needs a very long delay
- turn off the unit now takes a very long time where it would turn off in a few seconds
Also, check your router settings to see if you have it set up to block new connections (or have some other ACL which is preventing the NAS from reaching the internet).
Re: Urgent: Cannot install applications + Access Web UI too long, and turn-off unit too long
Sent you a PM with following info:
I ended up with a factory reset as I noticed all my internet connection from NAS is down, that's why utorrent won't work, you cannot connect remotely, my baikal server cannot sync and apps cannot install unless uploaded from my disk as a deb package
However, issue is still same after a factory reset, format volumes and create a new empty one:
- very long time to access GUI once booted
- very long time to turn off
I also noticed 2 issues:
- sending test mail fails with error 5008010003
- Apps page doesn't show any app
I now recall that I did not receive any email alerts since yesterday when the issues started, so it was probably already present
It is just like the NAS can connect to my local network as I can see it and look at shares from PC, but it cannot connect to the WAN
Nothing changed at the router side or switch
I downloaded logs before factory reset and I can download other logs from current state
Please help me fix the issue or check if it is hardware fault and really needs an RMA. This will cost me a lot of time however, so if it is not needed it will be great
The LAN interface is on DHCP, the gateway adress looks good and the NAS correctly picks the right internal IP assigned via static config at the router side
www.google.com is certainly not 10.0.0.1. 10.0.0.1 is a private IP address. So something is definitely wrong with your DNS setup. Try ping 8.8.8.8 and see if that responds.
Do you have DNS servers configured on the NAS? If so, start by deleting them, and see if the issue resolves. If it doesn't try adding 8.8.8.8 as a DNS server (it is google's public DNS server).
- I tried with manually setting DHCP to 8.8.8.8 on the NAS LAN ports
That has no chance of working. 8.8.8.8 is a DNS server. That is NOT the same as a DHCP server.
Let's slow down, and take a smaller step. Set the NAS back to the way it was before you changed the settings. If you have two ethernet cables connected to the NAS, then please disconnect one.
Then ssh into the NAS, and tell us what happens with you enter ping 8.8.8.8
Sorry, my message was wrong: I set 8.8.8.8 as DNS server, not DHCP obviously
When you setup the NAS behind a router which is serving as DHCP and DNS server, the DNS always gets auto assigned to the gateway adress, in my case 10.0.0.1
Here's a pic of my network setup, same unchanged from my Ultra 2 times...
I just put back my cables as before. I only have the 1GB LAN port connected:
ping 8.8.8.8 gives same failure message as my post above whith the setup in below screenshot
root@NAS-01:~# ping 10.0.0.33
PING 10.0.0.33 (10.0.0.33): 56 data bytes
64 bytes from 10.0.0.33: seq=0 ttl=128 time=0.461 ms
64 bytes from 10.0.0.33: seq=1 ttl=128 time=0.274 ms
64 bytes from 10.0.0.33: seq=2 ttl=128 time=0.263 ms
64 bytes from 10.0.0.33: seq=3 ttl=128 time=0.349 ms
64 bytes from 10.0.0.33: seq=4 ttl=128 time=0.496 ms
64 bytes from 10.0.0.33: seq=5 ttl=128 time=0.471 ms
64 bytes from 10.0.0.33: seq=6 ttl=128 time=0.238 ms
64 bytes from 10.0.0.33: seq=7 ttl=128 time=0.367 ms
64 bytes from 10.0.0.33: seq=8 ttl=128 time=0.517 ms
64 bytes from 10.0.0.33: seq=9 ttl=128 time=0.422 ms
64 bytes from 10.0.0.33: seq=10 ttl=128 time=0.562 ms
64 bytes from 10.0.0.33: seq=11 ttl=128 time=0.489 ms
64 bytes from 10.0.0.33: seq=12 ttl=128 time=0.522 ms
64 bytes from 10.0.0.33: seq=13 ttl=128 time=0.443 ms
--- 10.0.0.33 ping statistics ---
14 packets transmitted, 14 packets received, 0% packet loss
round-trip min/avg/max = 0.238/0.419/0.562 ms
root@NAS-01:~#
Ping seems to work properly here, really wired
My setup:
- Router behind modem
- Switch behind the router
- Every device connected to the Switch, nothing directly to the router
However, as stated above, I tried connecting directly to the router without fixing the issue
Also, check your router settings to see if you have it set up to block new connections (or have some other ACL which is preventing the NAS from reaching the internet).
factory reset made it possible to refresh the apps page
Maybe another solution exists, or I should turned off or it is a timed refresh setting...
Any info on this from a NAS tech support ?
Many thanks again really for pointing me to the issue. It was a stupid thing, probably on my side. I now remember I had visits for which I enabled the wifi guest access exactly the 06.06.2017, 2 days ago. I clearly remember now that I turned on block new devices. My new NAS got blocked at that moment. I thought that a device with a static IP could not be blocked and I remember also a discussion we had that wired blocked devices have only their WAN access cut, not the LAN access
