Today after I upgrade my RN104 from 6.2.1 to 6.2.2, I installed two apps named "Selfoss" and "PyLoad" one by one. After that, I tried to use Selfoss and found it can not read my opml file, thus I thought it was no use for me and I uninstalled it. After I uninstalled it, I loss my connection to RN104 from web page. When I tried to access the frontview by typing https://ip address/admin, the Chrome and IE11 returned me a error messenge:ERR_CONNECTION_REFUSED.I can not access the frontview anymore. I even tried to access it from my iphone or another computer, it did not work. I can still access (copy, delete, open functions are still work) to my volume from windows explorer. Also I could see my device from RAIDar. Everything works well except the frontview. I did the next several things: I have tried the HTTP as well as the HTTPS addresses I tried to shut down RN104 and unplugged the power cable for a while, it did not solve the problem. At last,I have reset the RN104 to reinstall the firmware (faq.php#How_do_I_re-install_the_firmware%3F) Nothing has worked and the frontview was still inaccessible. I am a newbie and I did not open the SSH service so that I can not use any SSH tools to access RN104. Need some good advice or help! Please!
I had installed an app called rsyslog before the trouble, it seemed that all the syslogs had been recorded in my RN104. So I am glad to send the log files to someone who maybe help me for the trouble. Thanks! The log files include: kern.log debug.log user.log syslog and other log files. BTW: I called the support center for help today. They told me an information that there were other users who had reported the same trouble when uninstalling any app from system. It seemed that OS6.2.2 is a new version with some bugs. Do not uninstall any app when you are using this version!!!
I have the same problem. Uninstall an application and you can not enter nas website.
Luckily I have enabled SSH and I could access the NAS. The problem is that "apache" can not boot, to try to run "apache2" throws an error about an uninstalled program file. If you go to directiorio mentioning the error and delete that file, restarting the NAS everything works fine. Also you can reinstall the application deleted with the command apt-get install (application name).
I tried it with several aplicacions and all fails.
Hi,Dear algiam, thanks for the reply! You mean if SSH in RN104 had not been enabled, it has no way to access the NAS, it is right? For my case, the only way I can do is to do a factory default reset?
I had the same problem. In my case, I tried to uninstall bzeeetr6 app. And after that apache2 process did not start. If you have possibility to login by ssh to your NAS - you shuld:
1. cd /etc/apache2/sites-enabled
2. ls -la ,for me it was: lrwxrwxrwx 1 root root 36 Dec 9 21:51 000-fv-http -> /etc/apache2/sites-available/fv-http lrwxrwxrwx 1 root root 27 Dec 30 23:43 000-fv-https -> ../sites-available/fv-https lrwxrwxrwx 1 root root 24 Jan 1 17:29 090-bzeeetr6.conf -> /apps/bzeeetr6/http.conf
3. delete http.conf for app that you earlier removed , in my case : rm 090-bzeeetr6.conf
Hi Emhyr - just wanted to say thanks for your information - I had exactly the same problem after installing an App and then removing it when it did not do what I wanted. Your information worked for me as well (different app) after a reinstall of the OS had done nothing. Thanks heaps!
I had the same problem. In my case, I tried to uninstall bzeeetr6 app. And after that apache2 process did not start. If you have possibility to login by ssh to your NAS - you shuld:
1. cd /etc/apache2/sites-enabled
2. ls -la ,for me it was: lrwxrwxrwx 1 root root 36 Dec 9 21:51 000-fv-http -> /etc/apache2/sites-available/fv-http lrwxrwxrwx 1 root root 27 Dec 30 23:43 000-fv-https -> ../sites-available/fv-https lrwxrwxrwx 1 root root 24 Jan 1 17:29 090-bzeeetr6.conf -> /apps/bzeeetr6/http.conf
3. delete http.conf for app that you earlier removed , in my case : rm 090-bzeeetr6.conf
4. start apache : /etc/init.d/apache2 start
^^^THIS^^^ should be a sticky!!!
You da man!
New 316, tried to uninstall Ajaxplorer, bricked. (ok, not bricked, but GUI dead).
I ignored the draconian, "Thou shalt perish in the flaming pit of DENY SUPPORT if thou treadest upon enabling SSH" warning from the GUI early on when I read of all the OS 6.2.2 GUI/uninstall problems and enabled SSH just in case. Fortunately 😎
My uninstall attempt was from the GUI. I didn't try to configure the program, just changed my mind.
On 6.2.3 you should not run into this issue again.
Good to know. I see beta 2 is up. Glad NG isn't dragging their feet on this one, it is pretty major.
FWIW, a rewording of the SSH warning might warn about *changes* made via SSH may void your warranty instead of threatening users to dare not do it.
From what I've seen, enabling SSH is an ABSOLUTE MUST on these systems, with a rather extreme increase in risk for those who do not. 60 sec fix vs vendor support (some folks may not be under warranty and unnecessarily ties up lines anyways), back up with minor inconvenience vs major outage at the mercy of the support tech's disposition today.
From a Risk Assessment point of view, I would REQUIRE my IT guys to enable it, just in case. Simple risk abatement.
Anyways, that's my $.02 on the subject, if anyone cares to listen 😉
I wouldn't say an absolute must, I'd say that the majority of users never SSH to the box. But yeah, for advanced users it may be a good idea to have it enabled. For the less advanced users, they can just put it in to tech support mode and contact support.
I also think that the warning needs to be a bit harsh or people who don't really know what they're doing will go in there and destroy things, a proper warning will keep most of them away 😉
I want to try the OS 6.2.3 Beta because 6.2.2 corrupted Frontview. Can you please provide explicit instructions on how to install Firmware without Frontview via SSH? (I have never used SSH before!)
I can fix the interface for you quickly if you boot your device in to tech support mode and then send me the tech support code.. Boot menu instructions for you device can be found here: www.readynas.com/kb/faq/boot/how_do_i_use_the_boot_menu
and the tech support code can then (depending on your model) be found on the display of your device or in the RAIDar application.
Please PM me the code once you have it. You can then upgrade the FW from the GUI but please note that it is a beta firmware so if your device is in a live environment you may want to hold off until the final release. Frontview breaks when you uninstall and app so just avoid doing that.
The Frontview GUI crash is really a very basic problem and simple to fix. If you're not familiar with SSH, let the techs do it in about 30 secs and all will be like it was before 😉
6.2.3 (supposed to fix that uninstall bug) is already posted in Beta 2, I would expect it very soon. In the meantime, don't uninstall any apps and you're good to go.
(I'm not with netgear, just been through the problem)
And speaking of this problem.. how long does it take before support solves this on average..?? Yesterday the update to 6.2(?) has ruined a perfectly new RN104..
Netgear is aware of my issue, but I would like to get to work...
Hello, I am having the same issue. Updated to 6.2.2 FW then uninstalled an app and I am cannot log in via frontview anymore.
I tried to upgrade the beta firmware 6.2.3 via USB but I am probably doing something wrong and it doesn't seems to be working.
This is what I did: Copy the fw img file into the USB drive ( it is a 500Gb hdd) Boot in boot menu and chose the OS reinstall The FW upgrade process starts, but I am always stuck on the 6.2.2 version.
I am not even sure it is actually reading from the USB drive. I tried all the USB ports.
The 6.2.3 firmware will fix it so a subsequent app uninstall shouldn't break Frontview. However the fix for your current problem needs to be done remotely. Will send you a PM.
This just made my decision to 'dump' netgear for sure..
- Buy a new device. do an update that makes your hardware unusable (by fault of the manufacturer). contact support and you have to wait until someone is available. (in my case more than 30 hours)
- Or come here. and get it fixed in an hour.
The difference in support between those 2 should not exist.
There's only a few or so people visiting the forums that fix this issue. I don't have to do extra work on the weekend, but I do because I want to. If I happen to be online around the same time as someone posts then I may fix their problem quickly.
Whereas we have a large number of support agents who tend to have a number of cases on the go (supporting a range of products and with a huge installed user base it's inevitable that there will always be a small percentage of customers having issues at any time). Some cases can be quite complicated and take a lot of time to fix. Our agents do handle new cases that enter their queue as soon as they can.
With the forums the time taken to provide help if it is offered can be unpredictable. Sometimes a PM or a new post in a thread may be required to remind that there are still issues. Whereas with a support case our agents are reminded to contact you after an interval has elapsed.
I don't have a large number of cases on the go and don't need to handle the very complicated problems.
The app uninstallation problem can be fixed extremely quickly after logging into a system, but as always we never know for sure before looking at a system if there are other issues. I try to help out with what I think will be simple problems like this. But for complicated problems it is best to use support. The same people that handle e.g. data recovery cases (where e.g. multiple disks have failed and data may/may not be recoverable) also handle cases where an app uninstall breaks the apache config.
