Re: Is the update server down?

tigerten · ‎2023-09-09

StephenB · ‎2023-09-09

Looks like it. I am also seeing that error.

tkevans · ‎2023-09-10

This happened last Summer; see https://community.netgear.com/t5/New-ReadyNAS-Users-General/DNS-error-message-6001010060-readycloud-...

It was fixed at that time, and that thread is closed for further comment.

StephenB · ‎2023-09-10

@AnishaA - is Netgear aware that the update server is down?

AnishaA · ‎2023-09-10

Hello @tigerten ,

And welcome to the NETGEAR Community! 🙂

Could you please explain whether your volume is active and also check your network connectivity once again?

@StephenB, Yes we are aware of it and we have fixed it already could you please check from your end once and revert us? If still it occurs we will check again

Have a lovely day,
Anisha A
Netgear Team

BrianTopp · ‎2023-09-11

I'm not the OP, but also noticed this problem this morning. My volume is active and network connectivity is fine (I can send a test alert email from the admin UI).

Is it possible that it's still not fixed, or has become broken again?

AnishaA · ‎2023-09-11

Hello @BrianTopp ,

we would need to confirm whether the issue is with the device or server. Could you please tell me when you get this error?

Have a lovely day,
Anisha A
Netgear Team

StephenB · ‎2023-09-11

@AnishaA wrote:

@StephenB, Yes we are aware of it and we have fixed it already could you please check from your end once and revert us? If still it occurs we will check again

@AnishaA - it is still giving me the "communication error"

BrianTopp · ‎2023-09-11

@AnishaA wrote:
Could you please tell me when you get this error?

It appears after I click the 'Check for Updates' link on the "System" tab of the "Admin Page".

I'm using a RN102. The same error dialog appears was appearing in firmware 6.10.8 this morning, and still now in version 6.10.9.

tigerten · ‎2023-09-11

Thanks @AnishaA for looking into it.

Unfortunately, as other users are experiencing, it is still not fixed on my end yet.

the internet is active. I am accessing via the zerotier network away from home.

The volumes are active as well.

Can you also add the OS 6.10.9 to the update server as well?

Thanks

tkevans · ‎2023-09-11

Still seeing this as of 08:13EDT today.

chri6020 · ‎2023-09-11

Same issue here on both 6.10.8 and 6.10.9.

darekkor · ‎2023-09-12

It's the same on my two devices (6.10.8 and 6.10.9). FW 6.10.9 was updated manually.

darekkor · ‎2023-09-12

!!!!!!!! Can you finally do something about this update service? !!!!!!!!

schumaku · ‎2023-09-12

What is the point? Forget this live update somebody messed up while attempting to add this 6.10.9 - nothing will follow due to EoL. Download the current and most likely the last ever 6.10.9 from https://www.netgear.com/support/product/readynas_os_6#download and all is fine.

StephenB · ‎2023-09-12

@AnishaA - the update server is still unreachable.

AnishaA · ‎2023-09-12

Hello @tigerten ,

We are looking into it. Will get back to you.

Have a lovely day,
Anisha A
Netgear Team

jah313 · ‎2023-09-19

I am having the same problem on an RN516 running 6.10.8

schumaku · ‎2023-09-19

@jah313 wrote:

I am having the same problem on an RN516 running 6.10.8

6.10.8 was made available - for manual download only - months ago. Cumbersome, some manual config changes have to be applied to make the APT update working again:

https://community.netgear.com/t5/Using-your-ReadyNAS-in-Business/How-I-got-apt-update-and-install-to...

Beyond, of this: The horse is dead, very unlikely there will ever be future updates. It moot checking the live update...

StephenB · ‎2023-09-20

@schumaku wrote:

@jah313 wrote:

I am having the same problem on an RN516 running 6.10.8

6.10.8 was made available - for manual download only - months ago. Cumbersome, some manual config changes have to be applied to make the APT update working again:

I think you meant 6.10.9.

But @jah313's issue is different. The check-for-updates function in the OS-6 web ui is returning a communications error.

The simple workaround is to manually install 6.10.9 from

https://kb.netgear.com/000065653/ReadyNAS-OS-Software-Version-6-10-9

But it would be good for Netgear to fix the problem with the server (and to start pushing 6.10.9).

treborpeg · ‎2023-09-20

Just for info I've been having this issue recently and still have it today on my RN202 - I checked the system logs and noticed this in fwbroker.log:

Sep 20 2023 17:55:56 INFO:AAGET_LOCAL_INFO: sinfo .model=ReadyNAS, model_num=202, .serial=45Y2535900564, .firmware_name=(null), .firmware_version=6.10.9
Sep 20 2023 17:55:56 INFO:AAGET_REMOTE_INFO(STEP 1 URL:) https://update.readynas.com/download/ReadyNASOS-arm/index?key=xxxxxxxxxxxxxxxx&model=ReadyNAS&model_...
Sep 20 2023 17:55:56 ERROR:GET_REMOTE_INFO: Error Curl=SSL peer certificate or SSH remote key was not OK
Sep 20 2023 17:55:56 ERROR:REQUEST_ERROR: HTTP Code=0
Sep 20 2023 17:55:56 WARNING:fwbroker.c:747:aquery_for_update::Success
Sep 20 2023 17:55:56 INFO:SEND_ERROR: err=60 cause=Error Curl details=SSL peer certificate or SSH remote key was not OK

So I tried going to the URL in the logs directly and I got the following certificate error:

Firefox detected an issue and did not continue to update.readynas.com.
SEC_ERROR_EXPIRED_CERTIFICATE

I guess this is the cause of the issue connecting to the update server?

schumaku · ‎2023-09-21

@StephenB wrote:

@schumaku wrote:

@jah313 wrote:

I am having the same problem on an RN516 running 6.10.8

6.10.8 was made available - for manual download only - months ago. Cumbersome, some manual config changes have to be applied to make the APT update working again:

I think you meant 6.10.9...

Sorry, my bad. Yes, of course.

@StephenB wrote:
The simple workaround is to manually install 6.10.9 from

https://kb.netgear.com/000065653/ReadyNAS-OS-Software-Version-6-10-9.

Our common standard advise for months 8-)

@StephenB wrote:
But it would be good for Netgear to fix the problem with the server (and to start pushing 6.10.9).

And include the patches required, so we don't have to continue this tragedy for another half year, binding and wasting a lot of resources

StephenB · ‎2023-09-21

@treborpeg wrote:

Firefox detected an issue and did not continue to update.readynas.com.
SEC_ERROR_EXPIRED_CERTIFICATE

That would explain it. Chrome says the cert expired two weeks ago.

@AnishaA , @NiveditaP - can you check on this?

treborpeg · ‎2023-10-01

Seems to be working again for me today 👍