Master Server offline?

Guest shared this idea 23 months ago
Completed

Today my Zipatile tells me that "Master Server is offline"

But if I check the du devices the cloud server is online but the virtual server is offline? Why?

I thought this is running locally


bc11d3ac2c6e1f36996904abd24a0a91

Replies (9)

photo
1

Still no connection.. Nearly all my rules are not working

photo
2

I have the same issue!

photo
2

Got to know! Because I created a ticket and Zipato support told me that this is because my Zipatile have no connection to the internet. Which is definitly working!

Now I can stop to check my network and Zipato need to start work on it!

photo
photo
1

Hello,

@tomu My colleague is working on this so please have some patience and it will be resolved.

@Max Mustermann Feel free to open a ticket and we will check it out.

Regards

photo
1

I found the problem, but must be solved by Zipato. It seems to be that a SSL certificate is expired and Zipatile cannot login remotely:


SSL handshake terminated: ssl=0xa11f5c00: Failure in SSL library, usually a protocol error

error:14094415:SSL routines:SSL3_READ_BYTES:sslv3 alert certificate expired (external/openssl/ssl/s3_pkt.c:1286 0xa10feca0:0x00000003)

at com.android.org.conscrypt.NativeCrypto.SSL_do_handshake(Native Method) ~[na:0.0]

at com.android.org.conscrypt.OpenSSLSocketImpl.startHandshake(OpenSSLSocketImpl.java:302) ~[na:0.0]

... 44 common frames omitted

19:50:43.216 [Cloud.scheduler.1] INFO com.zipato.cloud.bootstrap.Boot - trying http://my.zipato.com:8080/zipato-web/remoting/

19:50:43.331 [Cloud.scheduler.1] INFO com.zipato.cloud.bootstrap.Boot - trying https://my3.zipato.com:9443/zipato-web/remoting/

19:50:43.603 [Cloud.scheduler.1] ERROR com.zipato.cloud.bootstrap.Boot - Handshake failed

javax.net.ssl.SSLHandshakeException: Handshake failed

at com.android.org.conscrypt.OpenSSLSocketImpl.startHandshake(OpenSSLSocketImpl.java:374) ~[na:0.0]

at okhttp3.internal.connection.RealConnection.connectTls(RealConnection.java:242) ~[na:0.0]

at okhttp3.internal.connection.RealConnection.establishProtocol(RealConnection.java:200) ~[na:0.0]

at okhttp3.internal.connection.RealConnection.buildConnection(RealConnection.java:174) ~[na:0.0]

at okhttp3.internal.connection.RealConnection.connect(RealConnection.java:114) ~[na:0.0]

at okhttp3.internal.connection.StreamAllocation.findConnection(StreamAllocation.java:196) ~[na:0.0]

at okhttp3.internal.connection.StreamAllocation.findHealthyConnection(StreamAllocation.java:132) ~[na:0.0]

at okhttp3.internal.connection.StreamAllocation.newStream(StreamAllocation.java:101) ~[na:0.0]

at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:42) ~[na:0.0]

at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92) ~[na:0.0]

at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67) ~[na:0.0]

at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:93) ~[na:0.0]

at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92) ~[na:0.0]

at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67) ~[na:0.0]

at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.java:93) ~[na:0.0]

at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92) ~[na:0.0]

at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:120) ~[na:0.0]

at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92) ~[na:0.0]

at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67) ~[na:0.0]

at com.zipato.util.TaggerInterceptor.intercept(TaggerInterceptor.java:14) ~[na:0.0]

at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92) ~[na:0.0]

at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67) ~[na:0.0]

at com.zipato.util.RedirectInterceptor.intercept(RedirectInterceptor.java:14) ~[na:0.0]

at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92) ~[na:0.0]

at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67) ~[na:0.0]

at com.zipato.util.TaggerInterceptor.intercept(TaggerInterceptor.java:14) ~[na:0.0]

at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92) ~[na:0.0]

at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67) ~[na:0.0]

at okhttp3.logging.HttpLoggingInterceptor.intercept(HttpLoggingInterceptor.java:145) ~[na:0.0]

at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92) ~[na:0.0]

at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67) ~[na:0.0]

at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:179) ~[na:0.0]

at okhttp3.RealCall.execute(RealCall.java:63) ~[na:0.0]

at com.zipato.cloud.bootstrap.Boot.discover(Boot.java:142) ~[na:0.0]

at com.zipato.cloud.bootstrap.Boot.discover(Boot.java:194) ~[na:0.0]

at com.zipato.cloud.bootstrap.Boot.discover(Boot.java:57) ~[na:0.0]

at com.zipato.cloud.bootstrap.Boot.discover(Boot.java:38) ~[na:0.0]

at com.zipato.runtime.Cloud.initServices(Cloud.java:132) ~[na:0.0]

at com.zipato.runtime.Cloud$6.run(Cloud.java:858) ~[na:0.0]

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:422) ~[na:0.0]

at java.util.concurrent.FutureTask.run(FutureTask.java:237) ~[na:0.0]

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:152) ~[na:0.0]

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:265) ~[na:0.0]

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112) ~[na:0.0]

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587) ~[na:0.0]

at java.lang.Thread.run(Thread.java:818) ~[na:0.0]

Caused by: javax.net.ssl.SSLProtocolException: SSL handshake terminated: ssl=0xa11f5a00: Failure in SSL library, usually a protocol error

error:14094415:SSL routines:SSL3_READ_BYTES:sslv3 alert certificate expired (external/openssl/ssl/s3_pkt.c:1286 0x9c3843a0:0x00000003)

at com.android.org.conscrypt.NativeCrypto.SSL_do_handshake(Native Method) ~[na:0.0]

at com.android.org.conscrypt.OpenSSLSocketImpl.startHandshake(OpenSSLSocketImpl.java:302) ~[na:0.0]

... 45 common frames omitted

19:50:43.615 [Cloud.scheduler.1] INFO com.zipato.cloud.bootstrap.Boot - trying https://54.194.72.219:9443/zipato-web/remoting/

19:50:43.859 [Cloud.scheduler.1] ERROR com.zipato.cloud.bootstrap.Boot - Handshake failed


But I´m wondering why there no more complains here?!? All users with a Zipatile must have this problem..

photo
2

yes, correct, my Zipatile often goes offline, so I force a refresh and it connects again. It seems to go into hibernation and turn off the WIFI radio. however it is a problem because when there is no one at home and you need to do remote commands, the commands do not work. Routines are also sometimes not executed and Alexa commands respond that they are not working.

photo
1

The same I have for last year.. reply from Zipato: check your internet connection

Actually this is happening only on one zips box, the other are ok… if it would be problem with internet I suppose it would happen on all servers…

photo
photo
1

I saw the error just once for a couple of seconds some time in the last couple of days. So I don't have this issue with my Zipatile 1 (running v3).

photo
1

I have tons of logs like this. The daily logfile is more than1GB and this every day with the same error message.

Still no solution from Zipato.

Nothing was changed on my Zipatile and nothing was changed in my network.

photo
1

I have still no solution and nothing works for me since one week. And last comment from Zipato was 4 days ago that I should try to restart it...

Yesterday I started to migrate to Home Assistant (running on a Synology in a Docker container). Now I have at least my roller shutter up and running again.

Actully, my plan was to upgrade to Zipatile 2 in the near future, but in the last 24 hours I made very good experiance with Home Assistant and I like it. E.g. to include Doorbird it takes less than 2 minutes and all features are working (camera, last user, last motion, binary switch).

photo
1

Same to me today.

photo
3

I have the same issue to more than a houndred client we have installed Zipato!

As it seems Zipato is probably bankrupt, they are no longer responding to tickets.

Leave a Comment
 
Attach a file