[Solved] Unable to connect to Zentyal Cloud, but admin page shows connected.

[Escorpiom]

There are reports of similar issues on the forum, but at the moment I don't know what is the status of this issue.
Zentyal Cloud is still not working, it shows connected on the admin page but the VPN log states:

Code: [Select]

Tue Jun  5 20:54:13 2012 TCP: connect to [AF_INET]92.243.6.103:1194 failed, will try again in 5 seconds: Connection timed out
It's best to add some images to this post.
I've been unsubscribing and subscribing my server over and over again, sometimes it works for two days but it always drops offline after a while.
The cloud module was updated some days ago, and now it always shows connected but it does not reflect the real connection status.






Still hoping for a solution, some day.

Cheers.

[Escorpiom]

Work is underway, at this moment I'm connected:

Code: [Select]

Wed Jun  6 19:12:46 2012 Attempting to establish TCP connection with [AF_INET]92.243.6.103:1194 [nonblock]
Wed Jun  6 19:12:56 2012 TCP connection established with [AF_INET]92.243.6.103:1194
Wed Jun  6 19:12:56 2012 Socket Buffers: R=[87380->131072] S=[16384->131072]
Wed Jun  6 19:12:56 2012 TCPv4_CLIENT link local (bound): [AF_INET]172.30.30.4:60172
Wed Jun  6 19:12:56 2012 TCPv4_CLIENT link remote: [AF_INET]92.243.6.103:1194
Wed Jun  6 19:12:58 2012 TLS: Initial packet from [AF_INET]92.243.6.103:1194, sid=ef72fa9d d6c0aba3
Wed Jun  6 19:13:13 2012 VERIFY OK: depth=1, /C=ES/ST=Nation/L=Nowhere/O=ebox-controlcenter.com/CN=Certification_Authority_Certificate
Wed Jun  6 19:13:13 2012 VERIFY OK: depth=0, /C=ES/ST=Nation/L=Nowhere/O=ebox-controlcenter.com/CN=vpn1.cloud.zentyal.com
Wed Jun  6 19:13:34 2012 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Wed Jun  6 19:13:34 2012 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed Jun  6 19:13:34 2012 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Wed Jun  6 19:13:34 2012 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed Jun  6 19:13:34 2012 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Wed Jun  6 19:13:34 2012 [vpn1.cloud.zentyal.com] Peer Connection Initiated with [AF_INET]92.243.6.103:1194
Wed Jun  6 19:13:36 2012 SENT CONTROL [vpn1.cloud.zentyal.com]: 'PUSH_REQUEST' (status=1)
Wed Jun  6 19:13:41 2012 SENT CONTROL [vpn1.cloud.zentyal.com]: 'PUSH_REQUEST' (status=1)
Wed Jun  6 19:13:43 2012 PUSH: Received control message: 'PUSH_REPLY,route 10.200.0.0 255.255.0.0,route-gateway 10.201.64.1,ping 30,ping-restart 360,ifconfig 10.201.71.39 255.255.192.0'
Wed Jun  6 19:13:43 2012 OPTIONS IMPORT: timers and/or timeouts modified
Wed Jun  6 19:13:43 2012 OPTIONS IMPORT: --ifconfig/up options modified
Wed Jun  6 19:13:43 2012 OPTIONS IMPORT: route options modified
Wed Jun  6 19:13:43 2012 OPTIONS IMPORT: route-related options modified
Wed Jun  6 19:13:43 2012 ROUTE: default_gateway=UNDEF
Wed Jun  6 19:13:43 2012 TUN/TAP device tap0 opened
Wed Jun  6 19:13:43 2012 TUN/TAP TX queue length set to 100
Wed Jun  6 19:13:43 2012 /sbin/ifconfig tap0 10.201.71.39 netmask 255.255.192.0 mtu 1500 broadcast 10.201.127.255
Wed Jun  6 19:13:43 2012 /sbin/route add -net 10.200.0.0 netmask 255.255.0.0 gw 10.201.64.1
Wed Jun  6 19:13:43 2012 Initialization Sequence Completed
Wed Jun  6 19:13:43 2012 PUSH: Received control message: 'PUSH_REPLY,route 10.200.0.0 255.255.0.0,route-gateway 10.201.64.1,ping 30,ping-restart 360,ifconfig 10.201.71.39 255.255.192.0'
Will test for the next days to see how it holds up. Thanks!

[Escorpiom]

Connection refused by Zentyal Cloud:

Code: [Select]

Mon Jun 11 13:17:10 2012 Attempting to establish TCP connection with [AF_INET]92.243.6.103:1194 [nonblock]
Mon Jun 11 13:17:11 2012 TCP: connect to [AF_INET]92.243.6.103:1194 failed, will try again in 5 seconds: Connection refused
Mon Jun 11 13:17:17 2012 TCP: connect to [AF_INET]92.243.6.103:1194 failed, will try again in 5 seconds: Connection refused
Mon Jun 11 13:17:23 2012 TCP: connect to [AF_INET]92.243.6.103:1194 failed, will try again in 5 seconds: Connection refused
Mon Jun 11 13:17:29 2012 TCP: connect to [AF_INET]92.243.6.103:1194 failed, will try again in 5 seconds: Connection refused
Mon Jun 11 13:17:35 2012 TCP: connect to [AF_INET]92.243.6.103:1194 failed, will try again in 5 seconds: Connection refused
Mon Jun 11 13:17:41 2012 TCP: connect to [AF_INET]92.243.6.103:1194 failed, will try again in 5 seconds: Connection refused
Mon Jun 11 13:17:47 2012 TCP: connect to [AF_INET]92.243.6.103:1194 failed, will try again in 5 seconds: Connection refused
Mon Jun 11 13:17:53 2012 TCP: connect to [AF_INET]92.243.6.103:1194 failed, will try again in 5 seconds: Connection refused
Mon Jun 11 13:17:59 2012 TCP: connect to [AF_INET]92.243.6.103:1194 failed, will try again in 5 seconds: Connection refused
Mon Jun 11 13:18:05 2012 TCP: connect to [AF_INET]92.243.6.103:1194 failed, will try again in 5 seconds: Connection refused
Mon Jun 11 13:18:11 2012 TCP: connect to [AF_INET]92.243.6.103:1194 failed, will try again in 5 seconds: Connection refused
Mon Jun 11 13:18:17 2012 TCP: connect to [AF_INET]92.243.6.103:1194 failed, will try again in 5 seconds: Connection refused
Mon Jun 11 13:18:23 2012 TCP: connect to [AF_INET]92.243.6.103:1194 failed, will try again in 5 seconds: Connection refused
Mon Jun 11 13:18:29 2012 TCP: connect to [AF_INET]92.243.6.103:1194 failed, will try again in 5 seconds: Connection refused
Mon Jun 11 13:18:35 2012 TCP: connect to [AF_INET]92.243.6.103:1194 failed, will try again in 5 seconds: Connection refused
Mon Jun 11 13:18:41 2012 TCP: connect to [AF_INET]92.243.6.103:1194 failed, will try again in 5 seconds: Connection refused
Mon Jun 11 13:18:47 2012 TCP: connect to [AF_INET]92.243.6.103:1194 failed, will try again in 5 seconds: Connection refused
Mon Jun 11 13:18:53 2012 TCP: connect to [AF_INET]92.243.6.103:1194 failed, will try again in 5 seconds: Connection refused
Still needs some more work I guess.

Cheers.

[Escorpiom]

It has been three days and I'm still connected! After the last Cloud module update it appears to have been fixed.
Let's test it for a couple of days to see if it holds up.

I'm still not sure if the web interface reflects the actual connection status, I'm still checking the logs from time to time.
Anyway, that's only cosmetic. Important thing is that the VPN works. 

Cheers.

[robb]

I have seen some misconnection too. Most of the time it was not a disconnection but rather a failed update of ddclient.

Connecting on IP address was no problem, but connecting on the zentyal.me subdomain was always timing out.
If this occurs, I fix that by manualy setting a false IP address for ddclient.

Code: [Select]

sudo ddclient -use=ip -ip=1.2.3.4 -daemon=0
After that ddclient updates correctly.

[Escorpiom]

Thanks robb, that trick may come in handy the next time.
I just had to reboot the system because of some DNS issue I wrote about in another post, and after the reboot the cloud connected perfectly, checked the logs and all was fine.
One issue still remains, the web interface does not reflect the connection status. This is how it looks at the moment:



But that's misleading, the cloud is connected just fine. I'm sure it will be solved by the devs over time.

Cheers.

[robb]

I've had that connection status not showing as connected several times. After restart the VPN service or after reboot.

If you wait a minute or 2 and refresh the dashboard, it shows as connected (at least, it did for my servers)

regards,
robb

[Escorpiom]

I'm sorry to report that as of today there seem to be problems on the other side, the Zentyal Cloud side I mean.

Code: [Select]

Sun Jul  1 00:09:37 2012 TCP: connect to [AF_INET]92.243.6.103:1194 failed, will try again in 5 seconds: Connection timed out
Sun Jul  1 00:09:52 2012 TCP: connect to [AF_INET]92.243.6.103:1194 failed, will try again in 5 seconds: Connection timed out
Sun Jul  1 00:10:07 2012 TCP: connect to [AF_INET]92.243.6.103:1194 failed, will try again in 5 seconds: Connection timed out
Sun Jul  1 00:10:22 2012 TCP: connect to [AF_INET]92.243.6.103:1194 failed, will try again in 5 seconds: Connection timed out
Sun Jul  1 00:10:37 2012 TCP: connect to [AF_INET]92.243.6.103:1194 failed, will try again in 5 seconds: Connection timed out
Sun Jul  1 00:10:52 2012 TCP: connect to [AF_INET]92.243.6.103:1194 failed, will try again in 5 seconds: Connection timed out
Sun Jul  1 00:10:58 2012 TCP connection established with [AF_INET]92.243.6.103:1194
Sun Jul  1 00:10:58 2012 Socket Buffers: R=[87380->131072] S=[16384->131072]
Sun Jul  1 00:10:58 2012 TCPv4_CLIENT link local (bound): [AF_INET]172.30.30.4:51846
Sun Jul  1 00:10:58 2012 TCPv4_CLIENT link remote: [AF_INET]92.243.6.103:1194
Sun Jul  1 00:11:17 2012 Connection reset, restarting [-1]
Sun Jul  1 00:11:17 2012 TCP/UDP: Closing socket
Sun Jul  1 00:11:17 2012 SIGUSR1[soft,connection-reset] received, process restarting
Sun Jul  1 00:11:17 2012 Restart pause, 5 second(s)
Basically it means that either it can't connect, or the connection is reset and the process starts over again.

Cheers.

[Escorpiom]

It's still mixed up 

The admin interface says I'm not connected
From the logs I can see I'm not connected (connection refused)
But the Cloud web page says I'm connected! But the IP does not correspond to my IP.

Perhaps I should give up and wait until Zentyal 3.0 - not far away now.

Cheers.

[Escorpiom]

OK I hope it's possible to say this.....
Zentyal Cloud has been working perfectly for the last week! 
At the end of this week, will mark it as solved. Thanks!

Cheers.

Edit: It has been flawless, even had a power outage today but everything connected again as it should. Marking this as solved.