Beta firmware broke web interface 6.10.5-T11 (Beta 1)

[SebastianNielse]

I recently got 6.10.5-T11 (Beta 1) firmware.

Problem is now, that the web interface is in endless loop.

I type my username/password, then it says "Connecting to the admin page for ReadyNAS".

Once the progress bar is full, then it asks for username/password again.

Typing the wrong password will give a immidiate repeat of the password dialog, so I know its the correct password, since only the correct password gives the progress bar.

[StephenB]

Did you try rebooting the NAS?

[SebastianNielse]

Yes.
Note that its not possible to reboot from the web interface, but only by pulling the wall plug or pressing the physical button (hard reboot), as the web interface is in endless loop.

[StephenB]

I'd suggest trying

• clearing the browser cache
• incognito mode
• using a different browser

Maybe also disable any ad blockers or internet security software.

---

@SebastianNielse wrote:

Note that its not possible to reboot from the web interface, but only by pulling the wall plug or pressing the physical button (hard reboot), as the web interface is in endless loop.

---

A clean shutdown from the front panel should also be possible.  Two short presses of the power button will trigger a clean shutdown.  A 5-second press does the forced shutdown. Details for various desktop ReadyNAS are here: https://www.downloads.netgear.com/files/GDC/READYNAS-100/ReadyNAS_%20OS6_Desktop_HM_EN.pdf

It'd be helpful to know if the clean shutdown is working.

[SebastianNielse]

I have tried both (clearing cookies and browser cache, and also clean shutdown), nothing helps.

Tried in old browser (Internet Explorer 11) and that worked, but all "new" browsers trigger the inifinite loop.

I think this needs to be fixed ASAP. It seems to be some broken "automatic inactivity logout" code that only permit a few seconds of inactivity, as you see the actual admin page for a few seconds before throwing up the "Connecting to the admin page of ReadyNAS" progress bar.

[StephenB]

---

@SebastianNielse wrote:

I think this needs to be fixed ASAP. 

---

I agree, and I'm thinking I won't try the beta until I get some info on the resolution.

You can of course downgrade back to 6.10.4 (since IE works).

[Sandshark]

I'm running Beta 1 on a Pro2, which is my "sandbox NAS", and have no problems with Chrome or Edge.  Do you have any apps installed that might be contributing to the problem?

[mdgm]

I just tried on a RN204 that had been factory reset on 6.9.4 and upgraded directly from that to 6.10.5-T11 and have no problems access the web admin interface using the latest Chrome and Firefox.

As well as indicating what apps you are running you may also wish to download the logs and post your initrd.log

Another possibility is that there could be old config from an old firmware causing issues.

[SebastianNielse]

Only app im running is SMB Plus, nothing more.
Also it stopped working on IE 11 aswell now, now all my browsers just refresh.

[Nibbles0522]

I too have this problem and cannot now access Frontview as admin as It continually loops. I have tried 3 different browsers: Firefox & Chromium from Linux Mint and MS Edge from Windows 10, Clearing caches and incognito mode makes no difference.

I have a 12TB raid (4x4TB drives) and am trying to copy off the 6TB data before doing a factory reset to get the NAS working properly. I tried copying the /data directory to an 8TB USB attached disk, using rsync as admin via ssh, but there were too many files not copied due to permissions errors for that to be a reliable data copy. I am now using NFS shares to copy the data over the network but is is a painfully slow process.  This is not helped by the fact that I had set up a power profile that turns the NAS off at midnight and I can't find how to disable that via SSH.

Is there any way I can downgrade the firmware without doing a factory reset and thereby reformatting the drives and losing the data?

Failing that, how can I disable the power schedule via SSH and how can I copy the data to a USB disk without all the permissions issues?

As mentioned alsewhere in this thread, this is clearly a firmware issue and the Beta upgrade needs pulling befor any more damage gets done.

[mdgm]

You can downgrade the firmware using SSH, but before you do that it would be a good idea to try to see if what's going on can be easily identified.

Try accessing the web admin page then do e.g.

# journalctl -an100 -uapache2.service

This would provide the last 100 log entries for the apache2 service (used for http/s).

To get the last 100 log entries (for example) more generally you could do e.g.

# journalctl -an100

[Nibbles0522]

This seems to be the relevent extract from the

journalctl -an100 -uapache2.service

Apr 28 09:01:51 ReadyNas-01 apachectl[5598]: AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using fe80::eafc:afff:fee4:d253. Set the 'ServerName' directive globally to suppress this message

Apr 28 09:01:51 ReadyNas-01 systemd[1]: Reloaded The Apache HTTP Server.
Apr 28 09:01:51 ReadyNas-01 apache2[2566]: [ssl:warn] [pid 2566] AH01909: fe80::eafc:afff:fee4:d253:443:0 server certificate does NOT include an ID which matches the server name
Apr 28 09:01:51 ReadyNas-01 apache2[2566]: [mpm_prefork:warn] [pid 2566] AH00167: long lost child came home! (pid 2943)
Apr 28 09:01:51 ReadyNas-01 apache2[2566]: [mpm_prefork:warn] [pid 2566] AH00167: long lost child came home! (pid 2944)
Apr 28 09:01:51 ReadyNas-01 apache2[2566]: [mpm_prefork:warn] [pid 2566] AH00167: long lost child came home! (pid 2947)
Apr 28 10:27:08 ReadyNas-01 systemd[1]: Reloading The Apache HTTP Server.

... and this from the Journalctl -an100 command

Apr 29 12:23:58 ReadyNas-01 apache_access[2912]: 192.168.1.64 "GET /password_recovery/ HTTP/1.1" 200
Apr 29 12:23:58 ReadyNas-01 apache_access[2912]: 192.168.1.64 "GET /password_recovery/extjs/adapter/ext/ext-base.js HTTP/1.1" 200
Apr 29 12:23:58 ReadyNas-01 apache_access[2912]: 192.168.1.64 "GET /password_recovery/extjs/resources/css/ext-all.css HTTP/1.1" 200
Apr 29 12:23:58 ReadyNas-01 apache_access[2912]: 192.168.1.64 "GET /password_recovery/css/recovery_6.10.10671.610050004_base64.css HTTP/1.1" 200
Apr 29 12:23:59 ReadyNas-01 apache_access[2912]: 192.168.1.64 "GET /password_recovery/recovery_6.10.10671.610050004.js HTTP/1.1" 200
Apr 29 12:24:00 ReadyNas-01 apache_access[2912]: 192.168.1.64 "GET /password_recovery/extjs/ext-all.js HTTP/1.1" 200
Apr 29 12:24:00 ReadyNas-01 apache_access[2912]: 192.168.1.64 "GET /password_recovery/fonts/fostmedm-webfont.woff HTTP/1.1" 200
Apr 29 12:24:00 ReadyNas-01 apache_access[2912]: 192.168.1.64 "GET /password_recovery/extjs/resources/images/default/window/right-corners.png HTTP/1.1" 200
Apr 29 12:24:00 ReadyNas-01 apache_access[2912]: 192.168.1.64 "GET /password_recovery/extjs/resources/images/default/window/left-right.png HTTP/1.1" 200
Apr 29 12:24:00 ReadyNas-01 apache_access[2912]: 192.168.1.64 "GET /password_recovery/extjs/resources/images/default/window/top-bottom.png HTTP/1.1" 200
Apr 29 12:24:00 ReadyNas-01 apache_access[2912]: 192.168.1.64 "GET /password_recovery/extjs/resources/images/default/tabs/tab-strip-bg.gif HTTP/1.1" 200
Apr 29 12:24:00 ReadyNas-01 apache_access[2912]: 192.168.1.64 "GET /password_recovery/extjs/resources/images/default/tabs/tabs-sprite.gif HTTP/1.1" 200
Apr 29 12:24:00 ReadyNas-01 apache_access[2912]: 192.168.1.64 "GET /password_recovery/extjs/resources/images/default/toolbar/bg.gif HTTP/1.1" 200
Apr 29 12:24:00 ReadyNas-01 apache_access[2912]: 192.168.1.64 "GET /password_recovery/extjs/resources/images/default/grid/grid3-hrow.gif HTTP/1.1" 200
Apr 29 12:24:00 ReadyNas-01 apache_access[2912]: 192.168.1.64 "GET /password_recovery/extjs/resources/images/default/dd/drop-no.gif HTTP/1.1" 200
Apr 29 12:24:00 ReadyNas-01 apache_access[2912]: 192.168.1.64 "GET /password_recovery/extjs/resources/images/default/button/btn.gif HTTP/1.1" 200
Apr 29 12:24:00 ReadyNas-01 apache_access[2912]: 192.168.1.64 "GET /password_recovery/extjs/resources/images/default/window/left-corners.png HTTP/1.1" 200
Apr 29 12:24:00 ReadyNas-01 apache_access[2912]: 192.168.1.64 "GET /password_recovery/extjs/resources/images/default/form/trigger.gif HTTP/1.1" 200
Apr 29 12:24:00 ReadyNas-01 apache_access[2912]: 192.168.1.64 "GET /password_recovery/extjs/resources/images/default/grid/grid-blue-split.gif HTTP/1.1" 200
Apr 29 12:24:00 ReadyNas-01 apache_access[2912]: 192.168.1.64 "GET /password_recovery/extjs/resources/images/default/form/text-bg.gif HTTP/1.1" 200
Apr 29 12:24:00 ReadyNas-01 apache_access[2912]: 192.168.1.64 "GET /password_recovery/extjs/resources/images/default/layout/mini-bottom.gif HTTP/1.1" 200
Apr 29 12:24:00 ReadyNas-01 apache_access[2912]: 192.168.1.64 "GET /password_recovery/extjs/resources/images/default/sizer/s-handle.gif HTTP/1.1" 200
Apr 29 12:24:00 ReadyNas-01 apache_access[2912]: 192.168.1.64 "GET /password_recovery/extjs/resources/images/default/sizer/sw-handle.gif HTTP/1.1" 200
Apr 29 12:24:00 ReadyNas-01 apache_access[2912]: 192.168.1.64 "GET /password_recovery/extjs/resources/images/default/sizer/nw-handle.gif HTTP/1.1" 200
Apr 29 12:24:00 ReadyNas-01 apache_access[2912]: 192.168.1.64 "GET /password_recovery/extjs/resources/images/default/sizer/ne-handle.gif HTTP/1.1" 200
Apr 29 12:24:00 ReadyNas-01 apache_access[2912]: 192.168.1.64 "GET /password_recovery/extjs/resources/images/default/sizer/e-handle.gif HTTP/1.1" 200
Apr 29 12:24:00 ReadyNas-01 apache_access[2912]: 192.168.1.64 "POST /recover/ HTTP/1.1" 200

I'm not sure if I've got the relevent parts or not, but I could not find a way to attache the output files to this message.

Apr 29 12:24:02 ReadyNas-01 oauth2-vault[2829]: time="04-29-2021 12:24:02" level=error msg="Id is not available."

[mdgm]

Hmmm. It doesn't look like the apache logs indicate a problem. Perhaps the management service readynasd would be the next thing to check in the logs but I'm just guessing. In the journal you're looking for any entries around the time you reproduced the problem regardless of which service the log entry is for to try to see if a log entry may indicate what the problem is.

[Nibbles0522]

These are the only entries in readynasd around the time of a login loop, although there are plenty of similar ones at times when no login is being attempted:

Apr 29 18:26:38 ReadyNas-01 msmtpq[14046]: 49 more mails from queue failed to send with rc = 65
Apr 29 18:31:45 ReadyNas-01 msmtpq[14308]: mail [ 1 ] [ 2021-04-27-11.46.39 ] from queue ; send failed ; msmtp rc = 65

Paul N

[Nibbles0522]

Some more entrie in readynasd after I cancelled the Reset Password screen:

Apr 29 18:37:12 ReadyNas-01 readynasd[2529]: msmtp: envelope from address newberype@hotmail.co.uk not accepted by the server
Apr 29 18:37:12 ReadyNas-01 readynasd[2529]: msmtp: server message: 530 5.7.57 Client not authenticated to send mail. [HE1PR0301CA0015.eurprd03.prod.outlook.com]
Apr 29 18:37:12 ReadyNas-01 readynasd[2529]: msmtp: could not send mail (account default from /etc/msmtprc)
Apr 29 18:37:13 ReadyNas-01 msmtpq[15723]: mail for [ -C /etc/msmtprc newberype@hotmail.co.uk --timeout=60 ] : send was unsuccessful ; msmtp exit code was 65
Apr 29 18:37:13 ReadyNas-01 msmtpq[15725]: enqueued mail as : [ 2021-04-29-18.37.06 ] ( -C /etc/msmtprc newberype@hotmail.co.uk --timeout=60 )
Apr 29 18:37:13 ReadyNas-01 readynasd[2529]: NAS_SEND_MSMTP_RUN: Fail. (status=65. error_buf=(null))
Apr 29 18:37:13 ReadyNas-01 readynasd[2529]: Failed to issue method call: Invalid type / number of args
Apr 29 18:37:13 ReadyNas-01 readynasd[2529]: Could not send email

Paul N

[mdgm]

Still not seeing anything to indicate the problem. So either other log entries or maybe not in the logs.

[Stevep99]

I'm getting exactly he same issue with both chrome and edge browers. Can't stay loggd into the admin page long enough to make any changes 😞

[Nibbles0522]

OK, so how do you suggest we proceed? What other logs can I look at and what is the best way to let you see them in their entirety? Pastebin, email?

[mdgm]

Well it would probably be better if someone from NTGR wanted to have a look.

Though you could PM me a link if you like.

Hard to know which log to look at. It can be best to have them all available. Best thing if you can is to reproduce the problem then download the logs zip (e.g. using RAIDar). The most recent log entries should be from around the time that you reproduced the problem so if there's anything in the logs it hopefully wouldn't take long to find.

[calaba]

Houston, we have a problem ... today after updating to 6.10.5 (from 6.10.4) I am facing exactly the same problem as described here for the Beta release ... 

[StephenB]

---

@calaba wrote:

Houston, we have a problem ... today after updating to 6.10.5 (from 6.10.4) I am facing exactly the same problem as described here for the Beta release ... 

---

Using internet explorer works for some folks, so try that first.

[StevenED1964]

Good Afternoon All,

I realize that this is going to sound absurd and make no sense, but I have found the issue.  How this is related to the issue is well beyond my understanding and I leave it to someone MUCH smarter than I.

When I read a thread that said "it worked for IE" and then that same person later said "it no longer works for IE" I realized I had that SAME experience so there must be something to it.

When IE worked for me, it was a very small surface area as I do not ever use IE and so it was in its initial windowed state.

When IE stopped working for me, I had already maximized the IE surface area to see the entire admin web page.

The lightbulb lit and I tried something.  I put IE back into a small surface windowed state and eureka, the admin page was again working.

However, trying this trick with Edge does NOT work.  😞

So, I don't understand browsers.  I don't understand web page coding.  I don't understand why this trick works for IE but not Edge.

What I do know is that as unbelievable as THIS trick sounds and as hard as it is to comprehend that the IE window size has anything to do with the web page working or not working, using IE as a small window interface will allow you (or at least it does me) to gain access to your NAS and give you the ability to manipulate it!

[Sandshark]

That's clearly not "the solution", but hopefully it's a work-around that others can try and maybe it gives Netgear a clue as to what's different for the users with this problem, and it may not be in the NAS itself.  That could eventially point to root cause, which clearly is in the NAS.

[calaba]

Didn't work for me, IE, Edge, Chrome, small window, large window, keeps reloading after few seconds (login ok, shost 1st status page, detects data volume and afer fe seconds reloads ... and reloads ... and reloads ... 

[Matdub]

The only solution I have found is to revert to version 6.1 10.4 of the software if you want the procedure I can write it to you. Please excuse my english is bad