ReadyCLOUD NAS online (VPN Disconnected)

[drhjorgensen]

I am getting the dreaded ReadyNAS "Online (VPN Disconnected)" message for a single ReadyNAS. We have two identical ReadyNAS RN31200's in two different locations, each running the latest firmware. This had been working fine until this week. When I log into the latest ReadyCLOUD app (v1.20), I can connect fine to the BackupNAS, but the primary NAS shows Online (VPN Disconnected). I have rebooted the NAS, disconnected it ("Leave") ReadyCLOUD and re-attached it, all with no luck, I have also forwarded port 6300 from the router. Works fine from my iOS app, as well as through the web interface readycloud.netgear.com. Any suggestions?

[drhjorgensen]

Further to this, when I check the admin screen locally under the Cloud tab I see Services unavailable

[drhjorgensen]

I have downloaded the logs and here's what I see in leafp2p.log after a reboot of the NAS:

-- Reboot --
Nov 17 10:53:06 XXXNAS leafp2p[2633]: Starting leafp2p
Nov 17 10:53:06 XXXNAS leafp2p[2633]: Parsing config
Nov 17 10:53:06 XXXNAS leafp2p[2633]: Access rules valid 1
Nov 17 10:53:06 XXXNAS leafp2p[2633]: Service valid remote 1
Nov 17 10:53:06 XXXNAS leafp2p[2633]: service remote ReadyNAS Remote 0 1 0
Nov 17 10:53:06 XXXNAS leafp2p[2633]: Access rules valid 1
Nov 17 10:53:06 XXXNAS leafp2p[2633]: Service valid replication 1
Nov 17 10:53:06 XXXNAS leafp2p[2633]: service replication ReadyNAS Replication 1 0 0
Nov 17 10:53:06 XXXNAS leafp2p[2633]: Service config valid 1
Nov 17 10:53:06 XXXNAS leafp2p[2633]: P2P Created by Pramod Immaneni and Jeff Capone
Nov 17 10:53:06 XXXNAS leafp2p[2633]: P2P Designed and Developed by Pramod Immaneni
Nov 17 10:53:06 XXXNAS leafp2p[2633]: Started...
Nov 17 10:53:06 XXXNAS leafp2p[2633]: Accepting
Nov 17 10:53:47 XXXNAS leafp2p[2633]: SOAP 1.1 fault: SOAP-ENV:Client [no subcode]
Nov 17 10:53:47 XXXNAS leafp2p[2633]: "Name or service not known"
Nov 17 10:53:47 XXXNAS leafp2p[2633]: Detail: getaddrinfo failed in tcp_connect()
Nov 17 10:58:41 XXXNAS leafp2p[2633]: SOAP 1.1 fault: SOAP-ENV:Client [no subcode]
Nov 17 10:58:41 XXXNAS leafp2p[2633]: "Connection timed out"
Nov 17 10:58:41 XXXNAS leafp2p[2633]: Detail: connect failed in tcp_connect()
Nov 17 11:03:01 XXXNAS leafp2p[2633]: SOAP 1.1 fault: SOAP-ENV:Client [no subcode]
Nov 17 11:03:01 XXXNAS leafp2p[2633]: "Connection timed out"
Nov 17 11:03:01 XXXNAS leafp2p[2633]: Detail: connect failed in tcp_connect()
Nov 17 11:07:20 XXXNAS leafp2p[2633]: SOAP 1.1 fault: SOAP-ENV:Client [no subcode]
Nov 17 11:07:20 XXXNAS leafp2p[2633]: "Connection timed out"
Nov 17 11:07:20 XXXNAS leafp2p[2633]: Detail: connect failed in tcp_connect()
Nov 17 11:11:40 XXXNAS leafp2p[2633]: SOAP 1.1 fault: SOAP-ENV:Client [no subcode]
Nov 17 11:11:40 XXXNAS leafp2p[2633]: "Connection timed out"
Nov 17 11:11:40 XXXNAS leafp2p[2633]: Detail: connect failed in tcp_connect()
Nov 17 11:15:59 XXXNAS leafp2p[2633]: SOAP 1.1 fault: SOAP-ENV:Client [no subcode]
Nov 17 11:15:59 XXXNAS leafp2p[2633]: "Connection timed out"
Nov 17 11:15:59 XXXNAS leafp2p[2633]: Detail: connect failed in tcp_connect()
Nov 17 11:20:19 XXXNAS leafp2p[2633]: SOAP 1.1 fault: SOAP-ENV:Client [no subcode]
Nov 17 11:20:19 XXXNAS leafp2p[2633]: "Connection timed out"
Nov 17 11:20:19 XXXNAS leafp2p[2633]: Detail: connect failed in tcp_connect()

And the readycloud.log shows:

-- Reboot --
Nov 17 10:55:19 XXXNAS rcbrokerd[3474]: ERROR:handler.cpp:307: ERROR [syscmd:AddNetwork]: AddNetwork failed
Nov 17 10:55:19 XXXNAS rcbrokerd[3474]: ERROR:handler.cpp:1351: ERROR [syscmd:AddRemoteUserHandler] :AddRemoteUser XXX_sr failed with code=-1
Nov 17 10:55:19 XXXNAS rcbrokerd[3475]: ERROR:handler.cpp:307: ERROR [syscmd:AddNetwork]: AddNetwork failed
Nov 17 10:55:19 XXXNAS rcbrokerd[3475]: ERROR:handler.cpp:1351: ERROR [syscmd:AddRemoteUserHandler] :AddRemoteUser ZFNP-336-564pinfoXXX failed with code=-1

[Marc_V]

@drhjorgensen

Have you tried rebooting the NAS and also checking your NIC settings if you have any DNS Server addresses added?

You may also want to try toggling the ReadyCloud service from the Cloud tab

HTH

[drhjorgensen]

Yes, Mark, I've done all those things. Several times.

Changed DNS... normally I use DYN's 208.67.222.222 + .220 and I added Google's 8.8.8.8 for DNS

I've toggled the ReadyCloud service many times. Still getting "Services Unavailable" and no idea why... the log doesn't point to what address it's trying to connect to, for example...

Upgraded firmware on the Cisco RV110W router.

Still no luck.. and just out of the blue. 

I'm wondering about a Security Certificate problem?

At a loss here...

[CrossieRonnie]

I am having the same issue. With VPN Disconnected. I dont want to start changing settings until I know the change is going to work.

Looking back through the forum, this situation has happened before. But there was no solution! So i think its to do with Netgear servers or something on their end.

[drhjorgensen]

So we moved the BackupNAS we have to the office and connected it to the same network switch as the NAS that fails to connect to  ReadyCLOUD. The BackupNAS is working fine with ReadyCLOUD. So that tells me there is a problem with the NAS device itself, but nothing in the log points to what the problem might be...

Any ideas?

[StephenB]

Is the NAS using DHCP?

[drhjorgensen]

Have tried both static IP and DHCP. Currently on DHCP on suggestion of Netgear Tech. Still not working...

[StephenB]

---

@drhjorgensen wrote:
Have tried both static IP and DHCP. Currently on DHCP on suggestion of Netgear Tech. Still not working...

---

Maybe try using a different ReadyCloud port setting on that NAS?

[drhjorgensen]

We had to fully backup the NAS, reset to factory settings, pour the data back on, and reconfig the settings. NAS is now connected to ReadyCLOUD. 

[CrossieRonnie]

I can access the NAS drive via windows file manager & via any internet browser. It's the windows ready nas software that's not working. I have gone back one version, but still no change. So I've uninstalled the ready nas software & just use file manager.. Even VLC on my phone can access the drive!

[CrossieRonnie]

I really don't know if i fixed anything, but the ready cloud is now connetcing. i did some reconfiguring of the drives in the admin page.

Then reinstalled the readycloud software v1.20 after not using it for a wek and now it connects.

very strange!!