ginjaninja 539 Posted July 3, 2017 Share Posted July 3, 2017 (edited) so although my client is happily working and playing content syncing is not. i have sync only on wifi enabled...i am on wifi..i have 20Mbits of bandwidth to server. i authenticated with client using emby connect. not sure how the sync task records authentication. im on latest beta. is internet syncing supported? 07:47:00.718 [main] INFO App - file:///android_asset/www/index.html#!#dlg1499064412086: Line 0 : Uncaught (in promise) undefined 07:47:01.544 [main] INFO App - file:///android_asset/www/index.html#!/itemdetails.html?id=3bf170341b87bc987ff8ae4184e9f345: Line 0 : Uncaught (in promise) undefined 07:47:13.897 [main] INFO App - MainActivity.onPause 07:47:17.826 [JavaBridge] INFO App - Executing chromecast action emitAllRoutes request id: 11 07:47:21.824 [JavaBridge] INFO App - Executing chromecast action emitAllRoutes request id: 12 07:47:31.828 [JavaBridge] INFO App - Executing chromecast action emitAllRoutes request id: 13 07:48:01.911 [syncAdapterThread-2] DEBUG App - Checking network connection 07:48:01.915 [syncAdapterThread-2] DEBUG App - Local Network Connected 07:48:01.916 [syncAdapterThread-2] INFO App - MediaSyncAdapter starting 07:48:01.964 [syncAdapterThread-2] DEBUG App - AndroidSyncFileRepository started. syncPath: content://com.android.externalstorage.documents/tree/3032-6333%3Aemby 07:48:01.966 [syncAdapterThread-2] DEBUG App - Testing local device network connection 07:48:01.970 [syncAdapterThread-2] DEBUG App - Android device is connected to a network 07:48:01.971 [syncAdapterThread-2] DEBUG App - Adding request to queue: http://192.168.4.162:8096/emby/system/info/public?format=json 07:48:12.048 [main] ERROR App - VolleyError com.android.volley.TimeoutError: nullcom.android.volley.TimeoutErrorcom.android.volley.toolbox.BasicNetwork.performRequest(BasicNetwork.java:147)com.android.volley.NetworkDispatcher.run(NetworkDispatcher.java:114) 07:48:12.052 [main] DEBUG App - Adding request to queue: 07:48:12.126 [main] ERROR App - VolleyError com.android.volley.NoConnectionError: javax.net.ssl.SSLHandshakeException: java.security.cert.CertPathValidatorException: Trust anchor for certification path not found.com.android.volley.NoConnectionErrorcom.android.volley.toolbox.BasicNetwork.performRequest(BasicNetwork.java:158)com.android.volley.NetworkDispatcher.run(NetworkDispatcher.java:114)caused by javax.net.ssl.SSLHandshakeExceptioncom.android.org.conscrypt.OpenSSLSocketImpl.startHandshake(OpenSSLSocketImpl.java:368)okhttp3.internal.connection.RealConnection.connectTls(RealConnection.java:281)okhttp3.internal.connection.RealConnection.establishProtocol(RealConnection.java:251)okhttp3.internal.connection.RealConnection.connect(RealConnection.java:151)okhttp3.internal.connection.StreamAllocation.findConnection(StreamAllocation.java:195)okhttp3.internal.connection.StreamAllocation.findHealthyConnection(StreamAllocation.java:121)okhttp3.internal.connection.StreamAllocation.newStream(StreamAllocation.java:100)okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:42)okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:93)okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.java:93)okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:120)okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)okhttp3.internal.huc.OkHttpURLConnection$UnexpectedException$1.intercept(OkHttpURLConnection.java:564)okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:185)okhttp3.RealCall.execute(RealCall.java:69)okhttp3.internal.huc.OkHttpURLConnection.getResponse(OkHttpURLConnection.java:436)okhttp3.internal.huc.OkHttpURLConnection.getResponseCode(OkHttpURLConnection.java:473)okhttp3.internal.huc.DelegatingHttpsURLConnection.getResponseCode(DelegatingHttpsURLConnection.java:106)okhttp3.internal.huc.OkHttpsURLConnection.getResponseCode(OkHttpsURLConnection.java:26)com.android.volley.toolbox.HurlStack.performRequest(HurlStack.java:110)com.android.volley.toolbox.BasicNetwork.performRequest(BasicNetwork.java:97)com.android.volley.NetworkDispatcher.run(NetworkDispatcher.java:114) 07:48:12.127 [main] DEBUG App - No server available 07:48:12.127 [main] INFO App - Skipping sync process for server X99. No server authentication information available. 07:48:12.127 [main] INFO App - MultiServerSync complete 07:48:38.679 [main] INFO App - MainActivity.onPause Sent from my SM-G955F using Tapatalk Edited July 3, 2017 by ginjaninja Link to comment Share on other sites More sharing options...
Luke 37254 Posted July 3, 2017 Share Posted July 3, 2017 it's connecting, but not accepting your ssl cert. you may have accepted the cert manually previously but the background sync process is disconnected from that. we will have to get that hooked in to accept your previous confirmation. as always though for best results consider a cert that the device will accept such as lets encrypt. Link to comment Share on other sites More sharing options...
ginjaninja 539 Posted July 3, 2017 Author Share Posted July 3, 2017 interesting maybe this is related to why my sync seems patchy on the lan. With emby connect how does the client reference the server on and off the LAN? by internal IP? and external IP? lets encrypt cant issue certs for ips ive read...so ill turn off https and try again... Link to comment Share on other sites More sharing options...
ginjaninja 539 Posted July 4, 2017 Author Share Posted July 4, 2017 the syncing is working on http, thank you Luke, i wonder Link to comment Share on other sites More sharing options...
Luke 37254 Posted July 4, 2017 Share Posted July 4, 2017 Thanks for the feedback. Yes it is purely SSL cert related. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now