That is the error it throws because it is broke.
It is set for dhcp and date and time showing are correct
PS: I should not have to learn how to ssh to ping from the box. If it fails from the DL that means something is broken in the DL4100
That won’t work because the DL4100 in it’s faulty condition is using production servers at WDC.
init0 wrote:
Guys,
If your units ran beta code at one time, then you registered the user name to the beta server and not wd2go.com
If memory serves me correct
* login to the WebUI
* delete the created user (not admin)
* set admin back to defaults with no email address and ensure he has the check by the name
* ssh into the unit
* rm /etc/.eula_accepted
* run this command to point your machine to the production server
wd2go.sh -p
* Reboot
* Login to the WebUI
* Leave admin without an email address but assign a password
* Create a normal user with email address which should register with wd2go.com
* All should be OK now
The time in the NAS is correct and the NAS has no problems accessing the Internet. Something within the Orion communications module is going wrong.
Joerg_A wrote:
If I take a look at your screenshots, the timestamp is completely wrong. Either you have set the time for a parallel univers or your NTP Network time protocol cannot reach the NTP servers.
Have you set the NAS to a Static IP address? Have you set the gateway and the DNS ip addresses too?
You wrote “I can ping wd2go.com from a PC”. Have you tried to ping wd2go.com from within the SSH-console of the NAS too?
Pining any IP from another machine than the one having problems is not a solution.
two DL here, both working without problems since their first day two months ago. I cannot confirm that the web access has any problems on DL, I am using this feature ervey day.
Just curious, are we supposed to be able to login to wd2go.com with emails and password created on the DL?
I can not
And i suppose you manually configured ports and forwarded them? Mine is set to auto. Been up almost 3 days now !!
Sorry Gramps,
I havn´t seen that I have sent only photo. I use auto settings too.
I just use one “admin” email, and so far, whenever I lost connection, I could still login to WDMyCloud.com with admin email.
Perhaps you have upnp enabled on your router?
But the account you login with at wdmycloud.com/wd2go.com, you had before you got a DL unit?
I did not have an account prior to the DL and cannot login online with any user names. (email addresses)
UPnP fully disabled. Manual port forwarding. Been there, done that ages ago. Still, thanks for the suggestion. I have two other WD NAS’s which work absolutly fine through my router.
Gramps wrote:
Perhaps you have upnp enabled on your router?
But the account you login with at wdmycloud.com/wd2go.com, you had before you got a DL unit?
I did not have an account prior to the DL and cannot login online with any user names. (email addresses)
To the looks of things, no. I have a MyBook Duo and a Personal MyCloud NAS that can be connected to and mapped via wd2go.com. The DL NASs don’t seem to have that, but the UI can be made available for access from the WAN side of the router (with corect port forwarding) to allow file management.
Gramps wrote:
Just curious, are we supposed to be able to login to wd2go.com with emails and password created on the DL?
I can not
Gramps wrote:
Perhaps you have upnp enabled on your router?
But the account you login with at wdmycloud.com/wd2go.com, you had before you got a DL unit?
I did not have an account prior to the DL and cannot login online with any user names. (email addresses)
I do have UPnP enabled router, but I didn´t have account at wdmycloud.
I created one using WEBUi of DL4100
and just to went beck trough all the process I created now additional one
with no problems.
I already got an account on wd2go.com, but on the DL I didn’t create or apply this. I prefer to authenticate when on the local area network where the DL4100 is located (easiest) or using an authentication code. wd2go,com is only protected by user-name and password and NAS’s tend to hold data that the individual would not trust on any other clouud storage service like DropBox, Elephant Drive, etc…
Here is the problem . . .
Jun 13 09:39:20 2015 6 ZEUS CommMgr: ConnectionManager::createRelayConnection() - deleted port mappings from server.
Jun 13 09:39:20 2015 6 ZEUS CommMgr: ConnectionManager::createRelayConnection() - attempting to open VPN relay connection.
Jun 13 09:39:20 2015 6 ZEUS CommMgr: Reload dynamicconfig.ini file.
Jun 13 09:39:20 2015 6 ZEUS CommMgr: VPNManager::openVPNConnection() - checking if openVPN is running...
Jun 13 09:39:20 2015 6 ZEUS CommMgr: VPNManager::openVPNConnection() - creating auth.txt
Jun 13 09:39:21 2015 6 ZEUS root: updateremote.sh: got relay servers from central server www.wd2go.com.
Jun 13 09:39:21 2015 5 ZEUS CommMgr: VPNManager::openVPNConnection() - httpGet openvpn client relay servers and other settings.
Jun 13 09:39:31 2015 6 ZEUS CommMgr: VPNManager::openVPNConnection() - openVPN initialization did not complete, waiting...
Jun 13 09:39:41 2015 6 ZEUS CommMgr: VPNManager::openVPNConnection() - openVPN initialization did not complete, waiting...
Jun 13 09:39:51 2015 6 ZEUS CommMgr: VPNManager::openVPNConnection() - openVPN initialization did not complete, waiting...
Jun 13 09:40:01 2015 6 ZEUS CommMgr: VPNManager::openVPNConnection() - openVPN initialization did not complete, waiting...
Jun 13 09:40:11 2015 6 ZEUS CommMgr: VPNManager::openVPNConnection() - openVPN initialization did not complete, waiting...
Jun 13 09:40:21 2015 6 ZEUS CommMgr: VPNManager::openVPNConnection() - openVPN initialization did not complete, waiting...
Jun 13 09:40:31 2015 6 ZEUS CommMgr: VPNManager::openVPNConnection() - openVPN initialization did not complete, waiting...
Jun 13 09:40:31 2015 3 ZEUS CommMgr: VPNManager::closeVPNConnection() - openVPN process is not running, so return true.
Jun 13 09:40:41 2015 6 ZEUS CommMgr: VPNManager::openVPNConnection() - openVPN initialization did not complete, waiting...
Jun 13 09:40:51 2015 6 ZEUS CommMgr: VPNManager::openVPNConnection() - openVPN initialization did not complete, waiting...
Jun 13 09:41:01 2015 6 ZEUS CommMgr: VPNManager::openVPNConnection() - openVPN initialization did not complete, waiting...
Jun 13 09:41:11 2015 6 ZEUS CommMgr: VPNManager::openVPNConnection() - openVPN initialization did not complete, waiting...
Jun 13 09:41:21 2015 6 ZEUS CommMgr: VPNManager::openVPNConnection() - openVPN initialization did not complete, waiting...
Jun 13 09:41:31 2015 6 ZEUS CommMgr: VPNManager::openVPNConnection() - openVPN initialization did not complete, waiting...
Jun 13 09:41:41 2015 6 ZEUS CommMgr: VPNManager::openVPNConnection() - openVPN initialization did not complete, waiting...
Jun 13 09:41:41 2015 3 ZEUS CommMgr: VPNManager::closeVPNConnection() - openVPN process is not running, so return true.
Jun 13 09:41:51 2015 6 ZEUS CommMgr: VPNManager::openVPNConnection() - openVPN initialization did not complete, waiting...
Jun 13 09:42:01 2015 6 ZEUS CommMgr: VPNManager::openVPNConnection() - openVPN initialization did not complete, waiting...
Jun 13 09:42:11 2015 6 ZEUS CommMgr: VPNManager::openVPNConnection() - openVPN initialization did not complete, waiting...
Jun 13 09:42:21 2015 6 ZEUS CommMgr: VPNManager::openVPNConnection() - openVPN initialization did not complete, waiting...
Jun 13 09:42:31 2015 6 ZEUS CommMgr: VPNManager::openVPNConnection() - openVPN initialization did not complete, waiting...
Jun 13 09:42:41 2015 6 ZEUS CommMgr: VPNManager::openVPNConnection() - openVPN initialization did not complete, waiting...
Jun 13 09:42:51 2015 6 ZEUS CommMgr: VPNManager::openVPNConnection() - openVPN initialization did not complete, waiting...
Jun 13 09:42:51 2015 3 ZEUS CommMgr: VPNManager::closeVPNConnection() - openVPN process is not running, so return true.
Jun 13 09:43:01 2015 6 ZEUS CommMgr: VPNManager::openVPNConnection() - openVPN initialization did not complete, waiting...
Jun 13 09:43:11 2015 6 ZEUS CommMgr: VPNManager::openVPNConnection() - openVPN initialization did not complete, waiting...
Jun 13 09:43:21 2015 6 ZEUS CommMgr: VPNManager::openVPNConnection() - openVPN initialization did not complete, waiting...
Jun 13 09:43:31 2015 6 ZEUS CommMgr: VPNManager::openVPNConnection() - openVPN initialization did not complete, waiting...
Jun 13 09:43:41 2015 6 ZEUS CommMgr: VPNManager::openVPNConnection() - openVPN initialization did not complete, waiting...
Jun 13 09:43:51 2015 6 ZEUS CommMgr: VPNManager::openVPNConnection() - openVPN initialization did not complete, waiting...
Jun 13 09:44:01 2015 6 ZEUS CommMgr: VPNManager::openVPNConnection() - openVPN initialization did not complete, waiting...
Jun 13 09:44:01 2015 3 ZEUS CommMgr: VPNManager::closeVPNConnection() - openVPN process is not running, so return true.
Jun 13 09:44:01 2015 3 ZEUS CommMgr: VPNManager::openVPNConnection() - Failed to establish VPN connection, retries exceeded
Jun 13 09:44:01 2015 3 ZEUS CommMgr: ConnectionManager::createRelayConnection() - failed to create VPN connection.
Jun 13 09:44:01 2015 6 ZEUS CommMgr: ConnectionManager::createConnection() - port test response remote external IP []
Jun 13 09:44:01 2015 6 ZEUS CommMgr: DaemonControl::run - sleep 120 secs.
Just goes round and round. Same thing repeating over and over. Establishing a VPN tunnel should not require port forwading as I do not have a problem creating a VPN PPTP tunnel with a remote Windows servier I manage. L2PT, PPTP and IPsec pass-through options are all enabled. Thatis the problem.
Thing is, I got manual port forwarding enabled, an Android MyCloud application already authorised and the app is still working. It looks like the main issue is the DL suddenly failing to create a VPN runnel to WDC’s servers. I guess if I was to use a relayed connection then the MyCloud app on the phone would not work?
Anyway, the issue’s been noticed by WDC and hopefully will be identified and sorted for Cloud OS 2. 
Is cloud OS 2 slated for release in 2020?
At this rate, quite possibly. I think it’s for official release either this month or the next.
FWIW I am still conected 11 days later after redoing it with a new/virgin email addy…
It can take a while for the failure. I think since the last system only restore it was about 1.5 to 2 months(ish) before the failure occured. I don’t exactly know the conditions leading up to the failure apart of the DL4100 is low use and once set-up I just left the thing alone.
Should the Android app had been affected then I could have had an idea when the failure occured, but the Android MyClous app is still working.
I’ve narrowed down the issue to OpenVPN. It’s failing to establist a VPN tunnel. WD is very much aware about this. Have provided information.
The faulure logged is . . . .
Wed Jun 17 23:03:02 2015 OpenVPN 2.3.0 x86_64-intel-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [eurephia] [MH] [IPv6] built on Oct 15 2014
Wed Jun 17 23:03:02 2015 NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Wed Jun 17 23:03:02 2015 Socket Buffers: R=[163840->131072] S=[163840->524288]
Wed Jun 17 23:03:02 2015 UDPv4 link local: [undef]
Wed Jun 17 23:03:02 2015 UDPv4 link remote: [AF_INET]54.77.149.152:14244
Wed Jun 17 23:03:02 2015 TLS: Initial packet from [AF_INET]54.77.149.152:14244, sid=324714e5 5d99d25b
Wed Jun 17 23:03:02 2015 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Wed Jun 17 23:03:02 2015 VERIFY OK: depth=1, C=US, ST=CA, L=SanFrancisco, O=WD, OU=Branded, CN=4grelay, name=Ben, emailAddress=ben.roque@wdc.com
Wed Jun 17 23:03:02 2015 VERIFY OK: nsCertType=SERVER
Wed Jun 17 23:03:02 2015 VERIFY OK: depth=0, C=US, ST=CA, L=SanFrancisco, O=WD, OU=Branded, CN=server, name=Ben, emailAddress=ben.roque@wdc.com
Wed Jun 17 23:03:03 2015 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Wed Jun 17 23:03:03 2015 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed Jun 17 23:03:03 2015 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Wed Jun 17 23:03:03 2015 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed Jun 17 23:03:03 2015 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Wed Jun 17 23:03:03 2015 [server] Peer Connection Initiated with [AF_INET]54.77.149.152:14244
Wed Jun 17 23:03:05 2015 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
Wed Jun 17 23:03:05 2015 AUTH: Received control message: AUTH_FAILED
Wed Jun 17 23:03:05 2015 SIGTERM received, sending exit notification to peer
Wed Jun 17 23:03:08 2015 SIGTERM[soft,exit-with-notification] received, process exiting
