× NETGEAR will be terminating ReadyCLOUD service by July 1st, 2023. For more details click here.
Orbi WiFi 7 RBE973
Reply

ReadyCLOUD link in ReadyNASOS 6.5.0 release still points to test environment

TWilson
Aspirant

ReadyCLOUD link in ReadyNASOS 6.5.0 release still points to test environment

I just updated 2 devices from the beta 6.5.0 RC3 to the 6.5.0 release and found that the ReadyCLOUD link on the Cloud page still points to https://readycloud-test3.netgear.com (see picture below).  

 

Following the update, the devices were still listed on the https://readycloud-test3.netgear.com site but were no longer accessible from it (showed as being offline).  Before I figured out that the URL hadn't been updated, I had tried to leave and rejoin both devices to ReadyCloud in an attempt to fix.

 

Once I figured this out, I logged into the http://readycloud.netgear.com site using the new MyNetGear account and found both device listed and accessible there. 

 

I then went back to https://readycloud-test3.netgear.com and removed the devices from there.

 

It appears that this link was not updated before the firmware was released.

 

Link.jpg

Model: ReadyNAS-OS6|
Message 1 of 4

Accepted Solutions
Leia
NETGEAR Employee Retired

Re: ReadyCLOUD link in ReadyNASOS 6.5.0 release still points to test environment

Please clear the cache of the browser, and try again.

View solution in original post

Message 3 of 4

All Replies
mdgm-ntgr
NETGEAR Employee Retired

Re: ReadyCLOUD link in ReadyNASOS 6.5.0 release still points to test environment

The link works fine for me. Sounds like you need to clear your web browser cache. Try clearing your web browser cache, close your web browser then reopen it. You should find the link works as expected after doing that.

Message 2 of 4
Leia
NETGEAR Employee Retired

Re: ReadyCLOUD link in ReadyNASOS 6.5.0 release still points to test environment

Please clear the cache of the browser, and try again.

Message 3 of 4
TWilson
Aspirant

Re: ReadyCLOUD link in ReadyNASOS 6.5.0 release still points to test environment

It was IE 11.  I just tried Chrome and it was correct.  Clearing the IE cache fixed IE.  Thanks, I overlooked that.

 

Regards, 

Tom

Message 4 of 4
Top Contributors
Discussion stats
  • 3 replies
  • 5244 views
  • 2 kudos
  • 3 in conversation
Announcements