× NETGEAR will be terminating ReadyCLOUD service by April 1st, 2023. For more details click here.
Reply

ReadyNAS admin page no longer accessible after 6.9.3 upgrade

rapple
Aspirant

ReadyNAS admin page no longer accessible after 6.9.3 upgrade

I have what seems to be a fairly common issue after looking through forum.
No access to admin page after update to 6.9.3. All else appears to be working correctly.

Cycles through connecting to admin page , then back to the admin page for a couple of seconds - can even click links which are active then back to connecting msg.

Read all the topics I can find similar, but all closed, hence this new one.

I have already: Flushed Cache, tried different browsers, tried Raidar - mgt service offline message displayed.

Just need to get admin page back.

I see two options, but not sure what's best or how best to do them because of course all official links are spattered with at your own risk and wait for advice, so advice sought...

I think I can either downgrade to 6.9.2 or upgrade to 6.9.4 beta (which appears to be fairly close to the end of beta from teh comments/release notes to date)

I think I can do this either via USB boot or pulling disks and in safe mode.

Pulling disks doesn't sound clever, especially as I've seen some refs to this previously that show up further issues when firmware and disk images of software are out of line. So I think...

Go for USB recovery using one of the two above.
Anyone care to comment with reasonable authority as to which is best route please.

Oh BTW. No Internet connectivity and not likely as both ports are set static IP with incorrect gateway set - deliberately.
It's a security decision, sorry I dislike units with ability to initiate sessions across the net at will, no matter how well intentioned scans of apps etc are there's no guarantee of security.

Thanks.

Model: RN10400|ReadyNAS 100 Series 4- Bay (Diskless)
Message 1 of 14
rapple
Aspirant

Re: ReadyNAS admin page no longer accessible after 6.9.3 upgrade

Sorry, I forgot to ask, but may as well. Given that there are some of these issues and that most of the forum posts were in March and judging by the docs 6.9.3 was released in March, why didn't someone at least put up a warning about this on the download page.

I appreciate that there is always a decision to be made about such things based on numbers affected, reputation etc. but to me it really isn't right to rely on auto-patching behind the scenes and not telling customers. It's not whether or not you can get away with it (which in this instance you can't because most admins will go to the admin page post an upgrade) it's simply disrespectful to not give your customer a choice as to whether or not to take the risk of having facilities not available until a fix is made ready.

 

Click. - Grumpy old man mode off.

Message 2 of 14
mdgm-ntgr
NETGEAR Employee Retired

Re: ReadyNAS admin page no longer accessible after 6.9.3 upgrade

I understand your frustration with this. We believe that most users wouldn't both have last done a factory reset on very old firmware and not have their systems setup able to reach out to the internet to download patches.

 

6.9.4 is coming soon.

 

If you are comfortable with SSH (and already have that enabled) you could try:

# cd /apps/.freeapps

# rm -rf wordpress

 

Otherwise USB Boot Recovery or powering down, removing your disks (label order), upgrading the firmware using a scratch disk, verify update successful, power down, remove scratch disk, put disks back in same order as before would be the way forward for you.

Message 3 of 14
StephenB
Guru

Re: ReadyNAS admin page no longer accessible after 6.9.3 upgrade


@rapple wrote:


Oh BTW. No Internet connectivity and not likely as both ports are set static IP with incorrect gateway set - deliberately.


I think that's actually your problem - in particular that the NAS is stuck querying for hot fixes.  I believe it's resolved in 6.9.4.

 

I think another option is to do an OS reinstall to temporarily switch to DHCP (removing one of the ethernet cables).  I believe that will get you back into the admin ui.  Then immediately reconfigure the network to use your misconfigured static addresses.  The OS reinstall will also reset the admin password to password, and turn off the volume quota.  All of this is easily undone.

 

I don't think USB recovery to 6.9.2 will help.  Normally the NAS will detect that the OS on the disk is newer, and will then upgrade the flash to 6.9.3 again, instead of downgrading the disk to 6.9.2.  However, you could try going forward to 6.9.4 beta using that technique (or just use one of the methods proposed by @mdgm-ntgr).

 

Message 4 of 14
rapple
Aspirant

Re: ReadyNAS admin page no longer accessible after 6.9.3 upgrade

Thanks for the responses guys.

 


@mdgm-ntgr wrote:

I understand your frustration with this. We believe that most users wouldn't both have last done a factory reset on very old firmware and not have their systems setup able to reach out to the internet to download patches.


I take it that by factory reset you mean upgrade of firmware? As it happens I went from .4.1 to .5.2 as it wasn't entirely clear on release warnings if I could go straight to .9.3. It suggested so but I've been in IT so long I thought I'd be cautious...

Equally albeit I haven't read the manual for some time I saw no indication that auto updates were taking place so I wasn't even making a choice about not taking them I wasn't aware it was part of the offering. Not that I'd want to take it on a server device. I'm sure that accountability and recompense in a negative situation would not be what I would expect.


 

6.9.4 is coming soon.

 


Could you pls. define soon. To be specific, I have to survive this week without admin interface, then I'm on holiday for 2 weeks, back mid september. Could it be available on my return?

The only wrinkle is that the DLNA server is cr** at auto indexing the video partition and when stuck it needs to be re-nudged (It currently is - next job after upgrade). Strangely lack of access to this partition contents is more important to the rest of the household than accesing their documents, work, college papers etc. which is easy via SMB/CIFS, video to dedicated devices less so. Therefore I am on borrowed time courtesy of Netgear's

decision process to date!


If you are comfortable with SSH (and already have that enabled) you could try:

# cd /apps/.freeapps

# rm -rf wordpress

 

SSH enabled (from last support call) so had a look. Interesting thing to remove?? Why? As it happens there is no wordpress in that directory. Command issued anyway but no effect. Even with a reboot.



Otherwise USB Boot Recovery or powering down, removing your disks (label order), upgrading the firmware using a scratch disk, verify update successful, power down, remove scratch disk, put disks back in same order as before would be the way forward for you.


Sorry, could you just clarify is that (USB Boot recovery) OR (everything else) - I'm assuming it is.

 

...and I'm assuming that as @StephenB suggests with USB recovery this needs to be a forward to .9.4 to work.

 

Once again many thanks.


Message 5 of 14
StephenB
Guru

Re: ReadyNAS admin page no longer accessible after 6.9.3 upgrade


@rapple wrote:

 



Otherwise USB Boot Recovery or powering down, removing your disks (label order), upgrading the firmware using a scratch disk, verify update successful, power down, remove scratch disk, put disks back in same order as before would be the way forward for you.


Sorry, could you just clarify is that (USB Boot recovery) OR (everything else) - I'm assuming it is.

 



Yes, he means

 

Otherwise

  • USB Boot Recovery or
  • powering down, removing your disks (label order), upgrading the firmware using a scratch disk, verify update successful, power down, remove scratch disk, put disks back in same order as before 

These are two different ways of getting the OS loaded into the flash memory of the NAS (and from there installed onto your disks).  There should be no difference in the end result.

 

However, the USB recovery is very fussy about the thumb drive you use.  If it fails, then I suggest switching immediately to the second method (rather than hunting down more thumb drives to try until you find one that works).

Message 6 of 14
rapple
Aspirant

Re: ReadyNAS admin page no longer accessible after 6.9.3 upgrade

Cheers. I know what to try.

 

Got loads of USB drives from 10 years prior to the RN104 up to today and relatively to hand so worth a couple of shots. Just do I wait for formal release or take the beta then.

 

Didn't realise it loaded OS from disk. Always assumed as it was flashed it was a minimal customised Linux and just apps etc. went onto disk. For me it's an appliance that was easier to buy than rolling my own and worrying about performance and maintenance.

I started with a duo, moved on to this and have always been happy with my decision.

 

It's only when it goes wrong that you start to delve. Smiley Happy

 

Message 7 of 14
StephenB
Guru

Re: ReadyNAS admin page no longer accessible after 6.9.3 upgrade


@rapple wrote:

Just do I wait for formal release or take the beta then. 


I don't have any schedule information (I don't work for Netgear).  Usually they'll post an RC-1 (release candidate) before they actually release it - and we haven't seen that yet. 

Message 8 of 14
mdgm-ntgr
NETGEAR Employee Retired

Re: ReadyNAS admin page no longer accessible after 6.9.3 upgrade

Well if you can't find that wordpress directory then the problem is not what I expected it to be.

 

You could try accessing the web admin page again and then check the management service database log:

 

# journalctl -an100 CATEGORY=readynasd.log

 

and the http/s service log

# journalctl -an50 -uapache2.service

 

Between those two logs there should be an indication as to what is going on.

 

Also if you have SSH access you can update/downgrade the firmware using SSH e.g.

 

# cd /root

# wget URL

# ls -la

# unzip filename.zip

# rm *.zip *.html

# echo /root/ReadyNASOS-6.9.2-arm.img > /etc/.flash_update

# rn_shutdown -r

 

However depending what the problem is downgrading the firmware may not resolve it and if the problem is an unusual one we haven't observed it may come back when updating even to newer firmware so it'd be better to get an idea as to what's going on.

 

Message 9 of 14
rapple
Aspirant

Re: ReadyNAS admin page no longer accessible after 6.9.3 upgrade

OK, as it's an extract, and I can do all this by cutting and pasting from PuttY, below are the log segments you suggested. Both taken about 5 mins ago i.e. 22/8 around 12:40. Hope it's not too much or against etiquette for the forum.

I suspect the snapper issue in the first log is something to do with the home directories not having snapshots set up at ver 6.4.1.

The errors in the apache log I'm guessing are the cycling can't find admin page.

The other stuff seems to be around DNS and could be either due to I don't have an active DNS server locally or config errors perhaps on my part or something else entirely.

 

The warning on allowoverride I have no idea about.

The admin session that started and finished an hour apart, no idea what that was, certainly not a web based session to my knowledge although I s'pose you do have to log in to get to the cycling bit and I may not have closed the browser until later from the last time I tried.

I haven't tried to access the admin interface today.

 

Thanks. Rick.

 

 

root@netg-2:~# journalctl -an100 CATEGORY=readynasd.log
-- Logs begin at Sat 2018-07-07 22:42:33 GMT, end at Wed 2018-08-22 12:30:20 GMT. --
Aug 21 14:10:41 netg-2 readynasd[13029]: Could not get snapper config name for '/home/admin'
Aug 21 14:10:41 netg-2 readynasd[13029]: Could not get snapper config name for '/home/jackie'
Aug 21 14:10:41 netg-2 readynasd[13029]: Could not get snapper config name for '/home/rick'
Aug 21 14:24:01 netg-2 readynasd[13029]: ERROR: Radar: Maximum iteration exceeded
Aug 21 15:00:10 netg-2 readynasd[13029]: Snapshot c_1534863609 was successfully created for share or LUN Owncloud.
Aug 21 15:10:53 netg-2 readynasd[13029]: Snapshot prune worker successfully deleted snapshot 2018_08_19__15_00_30 from share or LUN Owncloud.
Aug 21 15:34:24 netg-2 readynasd[17768]: readynasd log started
Aug 21 15:34:28 netg-2 readynasd[17768]: readynasd started. (restarted=0)
Aug 21 15:34:58 netg-2 readynasd[17768]: Last run started at 1534860631 was aborted
Aug 21 15:34:58 netg-2 readynasd[17768]: Detect abnormal shutdown of readynasd and child. (readynasd)
Aug 21 15:34:58 netg-2 readynasd[17768]: ReadyNASOS service or process (readynasd) was restarted.
Aug 21 15:34:58 netg-2 readynasd[17768]: Using fan mode: quiet
Aug 21 15:35:02 netg-2 readynasd[17768]: ReadyNASOS background service started.
Aug 21 15:35:08 netg-2 readynasd[17768]: Could not get snapper config name for '/home/admin'
Aug 21 15:35:08 netg-2 readynasd[17768]: Could not get snapper config name for '/home/jackie'
Aug 21 15:35:09 netg-2 readynasd[17768]: Could not get snapper config name for '/home/rick'
Aug 21 15:35:23 netg-2 readynasd[18713]: readynasd log started
Aug 21 15:35:26 netg-2 readynasd[18713]: readynasd started. (restarted=0)
Aug 21 15:35:55 netg-2 readynasd[18713]: Last run started at 1534865698 was aborted
Aug 21 15:35:55 netg-2 readynasd[18713]: Detect abnormal shutdown of readynasd and child. (readynasd)
Aug 21 15:35:55 netg-2 readynasd[18713]: ReadyNASOS service or process (readynasd) was restarted.
Aug 21 15:35:56 netg-2 readynasd[18713]: Using fan mode: quiet
Aug 21 15:36:00 netg-2 readynasd[18713]: ReadyNASOS background service started.
Aug 21 15:36:05 netg-2 readynasd[18713]: Could not get snapper config name for '/home/admin'
Aug 21 15:36:05 netg-2 readynasd[18713]: Could not get snapper config name for '/home/jackie'
Aug 21 15:36:05 netg-2 readynasd[18713]: Could not get snapper config name for '/home/rick'
Aug 21 15:36:18 netg-2 readynasd[18713]: The system is shutting down.
Aug 21 15:36:22 netg-2 readynasd[19618]: readynasd log started
-- Reboot --
Aug 21 16:00:33 netg-2 readynasd[2389]: readynasd log started
Aug 21 16:00:44 netg-2 readynasd[2389]: readynasd started. (restarted=0)
Aug 21 16:01:46 netg-2 readynasd[2389]: Using fan mode: quiet
Aug 21 16:01:52 netg-2 readynasd[2389]: ReadyNASOS background service started.
Aug 21 16:02:08 netg-2 readynasd[2389]: Could not get snapper config name for '/home/admin'
Aug 21 16:02:08 netg-2 readynasd[2389]: Could not get snapper config name for '/home/jackie'
Aug 21 16:02:09 netg-2 readynasd[2389]: Could not get snapper config name for '/home/rick'
Aug 21 16:02:14 netg-2 readynasd[2389]: Snapshot prune worker successfully deleted snapshot 2018_08_19__16_00_37 from share or LUN Owncloud.
Aug 21 16:07:10 netg-2 readynasd[3823]: readynasd log started
Aug 21 16:07:13 netg-2 readynasd[3823]: readynasd started. (restarted=0)
Aug 21 16:07:42 netg-2 readynasd[3823]: Last run started at 1534867304 was aborted
Aug 21 16:07:42 netg-2 readynasd[3823]: Detect abnormal shutdown of readynasd and child. (readynasd)
Aug 21 16:07:42 netg-2 readynasd[3823]: ReadyNASOS service or process (readynasd) was restarted.
Aug 21 16:07:43 netg-2 readynasd[3823]: Using fan mode: quiet
Aug 21 16:07:47 netg-2 readynasd[3823]: ReadyNASOS background service started.
Aug 21 16:07:52 netg-2 readynasd[3823]: Could not get snapper config name for '/home/admin'
Aug 21 16:07:52 netg-2 readynasd[3823]: Could not get snapper config name for '/home/jackie'
Aug 21 16:07:52 netg-2 readynasd[3823]: Could not get snapper config name for '/home/rick'
Aug 21 16:21:13 netg-2 readynasd[3823]: ERROR: Radar: Maximum iteration exceeded
Aug 21 17:00:21 netg-2 readynasd[3823]: Snapshot c_1534870820 was successfully created for share or LUN Owncloud.
Aug 21 17:08:06 netg-2 readynasd[3823]: Snapshot prune worker successfully deleted snapshot 2018_08_19__17_00_45 from share or LUN Owncloud.
Aug 21 18:00:24 netg-2 readynasd[3823]: Snapshot c_1534874422 was successfully created for share or LUN Owncloud.
Aug 21 18:08:16 netg-2 readynasd[3823]: Snapshot prune worker successfully deleted snapshot 2018_08_19__18_00_52 from share or LUN Owncloud.
Aug 21 19:00:27 netg-2 readynasd[3823]: Snapshot c_1534878025 was successfully created for share or LUN Owncloud.
Aug 21 19:08:28 netg-2 readynasd[3823]: Snapshot prune worker successfully deleted snapshot 2018_08_19__19_01_00 from share or LUN Owncloud.
Aug 21 20:00:30 netg-2 readynasd[3823]: Snapshot c_1534881629 was successfully created for share or LUN Owncloud.
Aug 21 20:08:38 netg-2 readynasd[3823]: Snapshot prune worker successfully deleted snapshot 2018_08_19__20_00_07 from share or LUN Owncloud.
Aug 21 21:00:02 netg-2 readynasd[3823]: Snapshot c_1534885201 was successfully created for share or LUN Owncloud.
Aug 21 21:08:50 netg-2 readynasd[3823]: Snapshot prune worker successfully deleted snapshot 2018_08_19__21_00_14 from share or LUN Owncloud.
Aug 21 22:00:05 netg-2 readynasd[3823]: Snapshot c_1534888804 was successfully created for share or LUN Owncloud.
Aug 21 22:09:01 netg-2 readynasd[3823]: Snapshot prune worker successfully deleted snapshot 2018_08_19__22_00_22 from share or LUN Owncloud.
Aug 21 23:00:07 netg-2 readynasd[3823]: Snapshot c_1534892406 was successfully created for share or LUN Owncloud.
Aug 21 23:09:14 netg-2 readynasd[3823]: Snapshot prune worker successfully deleted snapshot 2018_08_19__23_00_27 from share or LUN Owncloud.
Aug 22 00:00:13 netg-2 readynasd[3823]: Snapshot c_1534896009 was successfully created for share or LUN GlobalW.
Aug 22 00:00:25 netg-2 readynasd[3823]: Snapshot c_1534896009 was successfully created for share or LUN music.
Aug 22 00:00:26 netg-2 readynasd[3823]: Snapshot c_1534896009 was successfully created for share or LUN Owncloud.
Aug 22 00:00:28 netg-2 readynasd[3823]: Snapshot c_1534896009 was successfully created for share or LUN Parents.
Aug 22 00:00:29 netg-2 readynasd[3823]: Snapshot c_1534896009 was successfully created for share or LUN Photos.
Aug 22 00:00:30 netg-2 readynasd[3823]: Snapshot c_1534896009 was successfully created for share or LUN video.
Aug 22 00:05:28 netg-2 readynasd[3823]: Successfully completed backup job Global Information.
Aug 22 00:06:21 netg-2 readynasd[3823]: Successfully completed backup job X Drive.
Aug 22 00:09:26 netg-2 readynasd[3823]: Snapshot prune worker successfully deleted snapshot 2018_07_25__00_00_05 from share or LUN GlobalW.
Aug 22 00:09:30 netg-2 readynasd[3823]: Snapshot prune worker successfully deleted snapshot 2018_07_25__00_00_07 from share or LUN music.
Aug 22 00:09:33 netg-2 readynasd[3823]: Snapshot prune worker successfully deleted snapshot 2018_07_25__00_00_09 from share or LUN Owncloud.
Aug 22 00:10:07 netg-2 readynasd[3823]: Snapshot prune worker successfully deleted snapshot 2018_07_25__00_00_10 from share or LUN Parents.
Aug 22 00:10:09 netg-2 readynasd[3823]: Snapshot prune worker successfully deleted snapshot 2018_07_25__00_00_11 from share or LUN Photos.
Aug 22 00:10:11 netg-2 readynasd[3823]: Snapshot prune worker successfully deleted snapshot 2018_07_25__00_00_12 from share or LUN video.
Aug 22 00:10:39 netg-2 readynasd[3823]: Successfully completed backup job Archive of Backups.
Aug 22 01:00:03 netg-2 readynasd[3823]: Snapshot c_1534899601 was successfully created for share or LUN Owncloud.
Aug 22 01:10:21 netg-2 readynasd[3823]: Snapshot prune worker successfully deleted snapshot 2018_08_20__01_00_51 from share or LUN Owncloud.
Aug 22 02:00:06 netg-2 readynasd[3823]: Snapshot c_1534903204 was successfully created for share or LUN Owncloud.
Aug 22 02:10:38 netg-2 readynasd[3823]: Snapshot prune worker successfully deleted snapshot 2018_08_20__02_00_57 from share or LUN Owncloud.
Aug 22 03:00:10 netg-2 readynasd[3823]: Snapshot c_1534906808 was successfully created for share or LUN Owncloud.
Aug 22 03:10:59 netg-2 readynasd[3823]: Snapshot prune worker successfully deleted snapshot 2018_08_20__03_00_17 from share or LUN Owncloud.
Aug 22 04:00:15 netg-2 readynasd[3823]: Snapshot c_1534910412 was successfully created for share or LUN Owncloud.
Aug 22 04:11:19 netg-2 readynasd[3823]: Snapshot prune worker successfully deleted snapshot 2018_08_20__04_01_50 from share or LUN Owncloud.
Aug 22 05:00:19 netg-2 readynasd[3823]: Snapshot c_1534914017 was successfully created for share or LUN Owncloud.
Aug 22 05:11:35 netg-2 readynasd[3823]: Snapshot prune worker successfully deleted snapshot 2018_08_20__05_01_15 from share or LUN Owncloud.
Aug 22 06:00:22 netg-2 readynasd[3823]: Snapshot c_1534917621 was successfully created for share or LUN Owncloud.
Aug 22 06:11:46 netg-2 readynasd[3823]: Snapshot prune worker successfully deleted snapshot 2018_08_20__06_00_20 from share or LUN Owncloud.
Aug 22 07:00:25 netg-2 readynasd[3823]: Snapshot c_1534921224 was successfully created for share or LUN Owncloud.
Aug 22 07:11:56 netg-2 readynasd[3823]: Snapshot prune worker successfully deleted snapshot 2018_08_20__07_00_26 from share or LUN Owncloud.
Aug 22 08:00:27 netg-2 readynasd[3823]: Snapshot c_1534924826 was successfully created for share or LUN Owncloud.
Aug 22 08:12:08 netg-2 readynasd[3823]: Snapshot prune worker successfully deleted snapshot 2018_08_20__08_00_31 from share or LUN Owncloud.
Aug 22 09:00:30 netg-2 readynasd[3823]: Snapshot c_1534928429 was successfully created for share or LUN Owncloud.
Aug 22 09:12:19 netg-2 readynasd[3823]: Snapshot prune worker successfully deleted snapshot 2018_08_20__09_00_37 from share or LUN Owncloud.
Aug 22 10:00:03 netg-2 readynasd[3823]: Snapshot c_1534932002 was successfully created for share or LUN Owncloud.
Aug 22 10:12:33 netg-2 readynasd[3823]: Snapshot prune worker successfully deleted snapshot 2018_08_20__10_00_42 from share or LUN Owncloud.
Aug 22 11:00:06 netg-2 readynasd[3823]: Snapshot c_1534935605 was successfully created for share or LUN Owncloud.
Aug 22 11:12:43 netg-2 readynasd[3823]: Snapshot prune worker successfully deleted snapshot 2018_08_20__11_00_48 from share or LUN Owncloud.
Aug 22 12:00:09 netg-2 readynasd[3823]: Snapshot c_1534939207 was successfully created for share or LUN Owncloud.
Aug 22 12:12:55 netg-2 readynasd[3823]: Snapshot prune worker successfully deleted snapshot 2018_08_20__12_00_53 from share or LUN Owncloud.
root@netg-2:~# journalctl -an50 -uapache2.service
-- Logs begin at Sat 2018-07-07 22:42:33 GMT, end at Wed 2018-08-22 12:30:20 GMT. --
Aug 21 16:01:00 netg-2 apache2[2356]: [error] [client 192.168.27.29] Connect rddclient failed, referer: https://192.168.27.232/admin/
Aug 21 16:01:03 netg-2 apache2[2357]: [error] [client 192.168.27.29] Connect rddclient failed, referer: https://192.168.27.232/admin/
Aug 21 16:01:06 netg-2 apache2[2359]: [error] [client 192.168.27.29] Connect rddclient failed, referer: https://192.168.27.232/admin/
Aug 21 16:01:09 netg-2 apache2[2362]: [error] [client 192.168.27.29] Connect rddclient failed, referer: https://192.168.27.232/admin/
Aug 21 16:01:15 netg-2 apache2[2361]: [error] [client 192.168.27.29] Connect rddclient failed, referer: https://192.168.27.232/admin/
Aug 21 16:01:21 netg-2 apache2[2403]: [error] [client 192.168.27.29] Connect rddclient failed, referer: https://192.168.27.232/admin/
Aug 21 16:01:27 netg-2 apache2[2356]: [error] [client 192.168.27.29] Connect rddclient failed, referer: https://192.168.27.232/admin/
Aug 21 16:01:27 netg-2 apache2[2357]: [error] [client 192.168.27.29] Connect rddclient failed, referer: https://192.168.27.232/admin/
Aug 21 16:01:33 netg-2 apache2[2359]: [error] [client 192.168.27.29] Connect rddclient failed, referer: https://192.168.27.232/admin/
Aug 21 16:01:39 netg-2 apache2[2362]: [error] [client 192.168.27.29] Connect rddclient failed, referer: https://192.168.27.232/admin/
Aug 21 16:01:45 netg-2 apache2[2361]: [error] [client 192.168.27.29] Connect rddclient failed, referer: https://192.168.27.232/admin/
Aug 21 16:01:48 netg-2 systemd[1]: Reloading The Apache HTTP Server.
Aug 21 16:01:48 netg-2 apache2[2403]: [error] [client 192.168.27.29] Connect rddclient failed, referer: https://192.168.27.232/admin/
Aug 21 16:01:49 netg-2 apache2[2693]: [Tue Aug 21 16:01:49 2018] [warn] Useless use of AllowOverride in line 4 of /etc/frontview/apache/apps-https.conf.
Aug 21 16:01:49 netg-2 apache2[2693]: [Tue Aug 21 16:01:49 2018] [warn] Useless use of AllowOverride in line 4 of /etc/frontview/apache/apps-https.conf.
Aug 21 16:01:49 netg-2 apache2[2693]: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
Aug 21 16:01:49 netg-2 apache2[2693]: Syntax OK
Aug 21 16:01:49 netg-2 systemd[1]: Reloaded The Apache HTTP Server.
Aug 21 16:01:50 netg-2 apache2[2352]: [warn] RSA server certificate CommonName (CN) `nas-36-68-3A.local' does NOT match server name!?
Aug 21 16:01:50 netg-2 apache2[2352]: [warn] long lost child came home! (pid 2353)
Aug 21 16:01:50 netg-2 apache2[2352]: [warn] long lost child came home! (pid 2354)
Aug 21 16:01:51 netg-2 apache2[2718]: [error] [client 192.168.27.29] Connect rddclient failed, referer: https://192.168.27.232/admin/
Aug 21 16:01:51 netg-2 apache_access[2711]: Admin session started from 192.168.27.29
Aug 21 16:07:09 netg-2 apache2[3748]: [error] [client 192.168.27.29] Connect rddclient failed, referer: https://192.168.27.232/admin/
Aug 21 16:07:09 netg-2 apache2[2719]: [error] [client 192.168.27.29] Connect rddclient failed, referer: https://192.168.27.232/admin/
Aug 21 16:07:09 netg-2 apache2[3801]: [error] [client 192.168.27.29] Connect rddclient failed, referer: https://192.168.27.232/admin/
Aug 21 16:07:09 netg-2 apache2[2717]: [error] [client 192.168.27.29] Connect rddclient failed, referer: https://192.168.27.232/admin/
Aug 21 16:07:09 netg-2 apache2[2764]: [error] [client 192.168.27.29] Connect rddclient failed, referer: https://192.168.27.232/admin/
Aug 21 16:07:09 netg-2 apache2[3770]: [error] [client 192.168.27.29] Connect rddclient failed, referer: https://192.168.27.232/admin/
Aug 21 16:07:09 netg-2 apache2[2772]: [error] [client 192.168.27.29] Connect rddclient failed, referer: https://192.168.27.232/admin/
Aug 21 16:07:09 netg-2 apache2[2721]: [error] [client 192.168.27.29] Connect rddclient failed, referer: https://192.168.27.232/admin/
Aug 21 16:07:09 netg-2 apache2[2720]: [error] [client 192.168.27.29] Connect rddclient failed, referer: https://192.168.27.232/admin/
Aug 21 16:07:14 netg-2 apache2[3649]: [error] [client 192.168.27.29] Connect rddclient failed, referer: https://192.168.27.232/admin/
Aug 21 16:07:20 netg-2 apache2[2717]: [error] [client 192.168.27.29] Connect rddclient failed, referer: https://192.168.27.232/admin/
Aug 21 16:07:26 netg-2 apache2[3770]: [error] [client 192.168.27.29] Connect rddclient failed, referer: https://192.168.27.232/admin/
Aug 21 16:07:30 netg-2 apache2[2772]: [error] [client 192.168.27.29] Connect rddclient failed, referer: https://192.168.27.232/admin/
Aug 21 16:07:32 netg-2 apache2[2721]: [error] [client 192.168.27.29] Connect rddclient failed, referer: https://192.168.27.232/admin/
Aug 21 16:07:38 netg-2 apache2[2720]: [error] [client 192.168.27.29] Connect rddclient failed, referer: https://192.168.27.232/admin/
Aug 21 16:07:44 netg-2 apache2[3748]: [error] [client 192.168.27.29] Connect rddclient failed, referer: https://192.168.27.232/admin/
Aug 21 16:07:44 netg-2 systemd[1]: Reloading The Apache HTTP Server.
Aug 21 16:07:46 netg-2 apache2[4072]: [Tue Aug 21 16:07:45 2018] [warn] Useless use of AllowOverride in line 4 of /etc/frontview/apache/apps-https.conf.
Aug 21 16:07:46 netg-2 apache2[4072]: [Tue Aug 21 16:07:46 2018] [warn] Useless use of AllowOverride in line 4 of /etc/frontview/apache/apps-https.conf.
Aug 21 16:07:46 netg-2 apache2[4072]: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
Aug 21 16:07:46 netg-2 apache2[4072]: Syntax OK
Aug 21 16:07:46 netg-2 systemd[1]: Reloaded The Apache HTTP Server.
Aug 21 16:07:46 netg-2 apache2[2352]: [warn] RSA server certificate CommonName (CN) `nas-36-68-3A.local' does NOT match server name!?
Aug 21 16:07:46 netg-2 apache2[2352]: [warn] long lost child came home! (pid 2711)
Aug 21 16:07:46 netg-2 apache2[2352]: [warn] long lost child came home! (pid 2714)
Aug 21 16:07:53 netg-2 apache_access[4105]: Admin session started from 192.168.27.29
Aug 21 17:10:54 netg-2 apache_access[4105]: Admin session from 192.168.27.29 ended after 1:03:01
root@netg-2:~#

Message 10 of 14
rapple
Aspirant

Re: ReadyNAS admin page no longer accessible after 6.9.3 upgrade

OK, Holiday been and gone, 6.9.4 has arrived, so I thought I'd give it a whirl.

Using the advice from mdgm-ntgr  I copied firmware using echo to /etc/.flash_update (which strangely didn't show up with ls -a once copied) but on reboot the unit did update the firmware - at least the login prompt for SSH shows it at 6.9.4.

 

However while this appears to have fixed the loop, any URL to the device now takes me to a page that does absolutely nothing. See attached screenshot. The "obvious" blue Reset password link doesn't appear to be a link at all so there's nothing to be done.

 

The NAS device still appears to be functioning fine using SMB and DLNA protocols, I just can't get to the admin pages.

 

Any further ideas?

 

 
Message 11 of 14
rapple
Aspirant

Re: ReadyNAS admin page no longer accessible after 6.9.3 upgrade

Scrub that, finally realised that the browser was defaulting HTTPS with the way I had entered the URL. Using HTTP cured the issue, admin pages back!

Message 12 of 14
StephenB
Guru

Re: ReadyNAS admin page no longer accessible after 6.9.3 upgrade


@rapple wrote:

Scrub that, finally realised that the browser was defaulting HTTPS with the way I had entered the URL. Using HTTP cured the issue, admin pages back!


Most browsers will redirect from http to https if that is available on the server.  https://192.168.27.232/admin should also have worked (though you'd likely need to click through a security exception).

 

Anyway, you can access it, which is the important thing.

Message 13 of 14
rapple
Aspirant

Re: ReadyNAS admin page no longer accessible after 6.9.3 upgrade

Indeed it should have.

The final thing is that as of this morning I can now access the admin through https!

I didn't try that last night once I was in, so I don't know whether this was a run once type of issue/fix  or whether something else has timed through on the NAS or whether it's a browser issue.

As the browser is set to do virtually nothing automatically (update cache clear etc) and the client windows were still in the same sessions as last night it's hard to see that anything's different on the client but hey!

At this point I'm in the just happy it appears to be fixed place.

Message 14 of 14
Top Contributors
Discussion stats
  • 13 replies
  • 1463 views
  • 0 kudos
  • 3 in conversation
Announcements