- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
ReadyCLOUD link in ReadyNASOS 6.5.0 release still points to test environment
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
Solved! Go to Solution.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
All Replies
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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