Connection to WebDAV not working
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Área
- mobile-dev, networking
Línea de trabajo
The failure is a socket connect timeout on the initial OPTIONS request, which is logged from WebDavClient.kt:243 and passes through ConnectionHandlerHandlerImpl.kt:53 and WebDavImpl.kt:147. Start by reading the connection check in WebDavClient.kt and reproducing against a local WebDAV server, since the cause may be the user's network or server rather than the code. Done means the connection succeeds against a reachable server, or the timeout is reported clearly to the user, with a test covering the path.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Please agree to the following
- I have searched existing issues for duplicates
- I agree to follow this project's Code of Conduct
Summary
Cannot connect to WebDAV Server since v2.x
System Setup
- Android: android 17 / API37 using a Pixel 10 Pro
- Cryptomator: Cryptomator v2.1.0-beta1 (3157) "F-Droid Main Repo Edition"
Cloud Type
WebDAV
Steps to Reproduce
- Open Cryptomator
- Klick on an existing WebDAV connection
Expected Behavior
Safe should be opened.
Actual Behavior
Nothing happens.
Reproducibility
Always
Relevant Log Output
V 20261016181148.911 Progress AUTHENTICATION -1%
D 20261016181148.912 ConnectToWebDavUseCase started 4579fd0b
D 20261016181148.913 OkHttp --> OPTIONS http://192.168.168.212:55005/ http/1.1 (unknown length)
D 20261016181148.913 OkHttp --> END OPTIONS
D 20261016181248.976 OkHttp <-- HTTP FAILED: java.net.SocketTimeoutException: failed to connect to /192.168.168.212 (port 55005) from /192.168.168.42 (port 48064) after 60000ms
D 20261016181248.978 ConnectToWebDavUseCase failed 4579fd0b
V 20261016181249.004 Progress COMPLETED -1%
D 20261016181249.008 ExceptionHandler Unexpected error
org.cryptomator.domain.exception.NetworkConnectionException: org.cryptomator.domain.exception.FatalBackendException: java.net.SocketTimeoutException: failed to connect to /192.168.168.212 (port 55005) from /192.168.168.42 (port 48064) after 60000ms
at org.cryptomator.data.cloud.webdav.WebDavCloudContentRepository.throwNetworkConnectionExceptionIfRequired(WebDavCloudContentRepository.kt:91)
at org.cryptomator.data.cloud.webdav.WebDavCloudContentRepository.throwWrappedIfRequired(WebDavCloudContentRepository.kt:41)
at org.cryptomator.data.cloud.InterceptingCloudContentRepository.checkAuthenticationAndRetrieveCurrentAccount(InterceptingCloudContentRepository.kt:199)
at org.cryptomator.data.repository.DispatchingCloudContentRepository.checkAuthenticationAndRetrieveCurrentAccount(DispatchingCloudContentRepository.kt:182)
at org.cryptomator.domain.usecases.cloud.ConnectToWebDav.execute(ConnectToWebDav.java:21)
at org.cryptomator.domain.usecases.cloud.ConnectToWebDavUseCase$Launcher$2.call(ConnectToWebDavUseCase.java:92)
at io.reactivex.internal.operators.flowable.FlowableFromCallable.subscribeActual(FlowableFromCallable.java:39)
at io.reactivex.Flowable.subscribe(Flowable.java:14935)
at io.reactivex.Flowable.subscribe(Flowable.java:14882)
at io.reactivex.internal.operators.flowable.FlowableSubscribeOn$SubscribeOnSubscriber.run(FlowableSubscribeOn.java:82)
at io.reactivex.internal.schedulers.ExecutorScheduler$ExecutorWorker$BooleanRunnable.run(ExecutorScheduler.java:288)
at io.reactivex.internal.schedulers.ExecutorScheduler$ExecutorWorker.run(ExecutorScheduler.java:253)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1100)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:1571)
Caused by: org.cryptomator.domain.exception.FatalBackendException: java.net.SocketTimeoutException: failed to connect to /192.168.168.212 (port 55005) from /192.168.168.42 (port 48064) after 60000ms
at org.cryptomator.data.cloud.webdav.network.WebDavClient.checkAuthenticationAndServerCompatibility(WebDavClient.kt:243)
at org.cryptomator.data.cloud.webdav.network.ConnectionHandlerHandlerImpl.checkAuthenticationAndServerCompatibility(ConnectionHandlerHandlerImpl.kt:53)
at org.cryptomator.data.cloud.webdav.WebDavImpl.checkAuthenticationAndServerCompatibility(WebDavImpl.kt:147)
at org.cryptomator.data.cloud.webdav.WebDavImpl.currentAccount(WebDavImpl.kt:186)
at org.cryptomator.data.cloud.webdav.WebDavCloudContentRepository$Intercepted.checkAuthenticationAndRetrieveCurrentAccount(WebDavCloudContentRepository.kt:221)
at org.cryptomator.data.cloud.webdav.WebDavCloudContentRepository$Intercepted.checkAuthenticationAndRetrieveCurrentAccount(WebDavCloudContentRepository.kt:95)
at org.cryptomator.data.cloud.InterceptingCloudContentRepository.checkAuthenticationAndRetrieveCurrentAccount(InterceptingCloudContentRepository.kt:194)
... 12 more
Caused by: java.net.SocketTimeoutException: failed to connect to /192.168.168.212 (port 55005) from /192.168.168.42 (port 48064) after 60000ms
at libcore.io.IoBridge.connectErrno(IoBridge.java:232)
at libcore.io.IoBridge.connect(IoBridge.java:176)
at java.net.PlainSocketImpl.socketConnect(PlainSocketImpl.java:142)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:390)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:230)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:212)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:436)
at java.net.Socket.connect(Socket.java:646)
at okhttp3.internal.platform.Platform.connectSocket(Platform.kt:173)
at okhttp3.internal.connection.ConnectPlan.connectSocket(ConnectPlan.kt:283)
at okhttp3.internal.connection.ConnectPlan.connectTcp(ConnectPlan.kt:144)
at okhttp3.internal.connection.FastFallbackExchangeFinder$launchTcpConnect$1.runOnce(FastFallbackExchangeFinder.kt:147)
at okhttp3.internal.concurrent.TaskRunner$runnable$1.run(TaskRunner.kt:81)
... 3 more
ErrorCode: 1JA0:T89J
D 20261016181249.009 ExceptionHandler org.cryptomator.domain.exception.NetworkConnectionException: org.cryptomator.domain.exception.FatalBackendException: java.net.SocketTimeoutException: failed to connect to /192.168.168.212 (port 55005) from /192.168.168.42 (port 48064) after 60000ms
at org.cryptomator.data.cloud.webdav.WebDavCloudContentRepository.throwNetworkConnectionExceptionIfRequired(WebDavCloudContentRepository.kt:91)
at org.cryptomator.data.cloud.webdav.WebDavCloudContentRepository.throwWrappedIfRequired(WebDavCloudContentRepository.kt:41)
at org.cryptomator.data.cloud.InterceptingCloudContentRepository.checkAuthenticationAndRetrieveCurrentAccount(InterceptingCloudContentRepository.kt:199)
at org.cryptomator.data.repository.DispatchingCloudContentRepository.checkAuthenticationAndRetrieveCurrentAccount(DispatchingCloudContentRepository.kt:182)
at org.cryptomator.domain.usecases.cloud.ConnectToWebDav.execute(ConnectToWebDav.java:21)
at org.cryptomator.domain.usecases.cloud.ConnectToWebDavUseCase$Launcher$2.call(ConnectToWebDavUseCase.java:92)
at io.reactivex.internal.operators.flowable.FlowableFromCallable.subscribeActual(FlowableFromCallable.java:39)
at io.reactivex.Flowable.subscribe(Flowable.java:14935)
at io.reactivex.Flowable.subscribe(Flowable.java:14882)
at io.reactivex.internal.operators.flowable.FlowableSubscribeOn$SubscribeOnSubscriber.run(FlowableSubscribeOn.java:82)
at io.reactivex.internal.schedulers.ExecutorScheduler$ExecutorWorker$BooleanRunnable.run(ExecutorScheduler.java:288)
at io.reactivex.internal.schedulers.ExecutorScheduler$ExecutorWorker.run(ExecutorScheduler.java:253)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1100)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:1571)
Caused by: org.cryptomator.domain.exception.FatalBackendException: java.net.SocketTimeoutException: failed to connect to /192.168.168.212 (port 55005) from /192.168.168.42 (port 48064) after 60000ms
at org.cryptomator.data.cloud.webdav.network.WebDavClient.checkAuthenticationAndServerCompatibility(WebDavClient.kt:243)
at org.cryptomator.data.cloud.webdav.network.ConnectionHandlerHandlerImpl.checkAuthenticationAndServerCompatibility(ConnectionHandlerHandlerImpl.kt:53)
at org.cryptomator.data.cloud.webdav.WebDavImpl.checkAuthenticationAndServerCompatibility(WebDavImpl.kt:147)
at org.cryptomator.data.cloud.webdav.WebDavImpl.currentAccount(WebDavImpl.kt:186)
at org.cryptomator.data.cloud.webdav.WebDavCloudContentRepository$Intercepted.checkAuthenticationAndRetrieveCurrentAccount(WebDavCloudContentRepository.kt:221)
at org.cryptomator.data.cloud.webdav.WebDavCloudContentRepository$Intercepted.checkAuthenticationAndRetrieveCurrentAccount(WebDavCloudContentRepository.kt:95)
at org.cryptomator.data.cloud.InterceptingCloudContentRepository.checkAuthenticationAndRetrieveCurrentAccount(InterceptingCloudContentRepository.kt:194)
... 12 more
Caused by: java.net.SocketTimeoutException: failed to connect to /192.168.168.212 (port 55005) from /192.168.168.42 (port 48064) after 60000ms
at libcore.io.IoBridge.connectErrno(IoBridge.java:232)
at libcore.io.IoBridge.connect(IoBridge.java:176)
at java.net.PlainSocketImpl.socketConnect(PlainSocketImpl.java:142)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:390)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:230)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:212)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:436)
at java.net.Socket.connect(Socket.java:646)
at okhttp3.internal.platform.Platform.connectSocket(Platform.kt:173)
at okhttp3.internal.connection.ConnectPlan.connectSocket(ConnectPlan.kt:283)
at okhttp3.internal.connection.ConnectPlan.connectTcp(ConnectPlan.kt:144)
at okhttp3.internal.connection.FastFallbackExchangeFinder$launchTcpConnect$1.runOnce(FastFallbackExchangeFinder.kt:147)
at okhttp3.internal.concurrent.TaskRunner$runnable$1.run(TaskRunner.kt:81)
... 3 more
ErrorCode: 1JA0:T89J
W 20261016181249.014 Message Keine Internetverbindung
Anything else?
- Lenguaje dominante
- Kotlin
- Estrellas
- 1.2k
- Forks
- 218
- Merge medio
- 2 d 3 h
- PR fusionados (30 d)
- 10
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de cryptomator/android
-
Increase Cache Size?Abiertotype:feature-request
Dificultad 3/5 1-2 días Aptitud para principiantes 48/100
cryptomator/android#666 ·
Los mantenedores suelen responder en 1 día
-
misc:hub
Dificultad 5/5 Más de una semana Aptitud para principiantes 45/100
cryptomator/android#657 ·
Los mantenedores suelen responder en 1 día
-
"Keep unlocked" advanced setting on Android app doesn't release Vault after files are closedAbierto
Dificultad 3/5 1-2 días Aptitud para principiantes 55/100
cryptomator/android#656 ·
Los mantenedores suelen responder en 1 día
-
state:to-be-confirmed type:bug
Dificultad 4/5 3-5 días Aptitud para principiantes 68/100
cryptomator/android#654 ·
Los mantenedores suelen responder en 1 día
-
Using custom CA certificatesAbiertotype:feature-request
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
cryptomator/android#653 · 1 reacción ·
Los mantenedores suelen responder en 1 día
Todos los issues de cryptomator/android
Issues similares
-
cr:missing-repro cr:platform:android missing-repro platform:android
Dificultad 2/5 1-3 horas Aptitud para principiantes 90/100
software-mansion/react-native-screens#4950 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 80/100
software-mansion/enriched-markdown#1033 ·
Los mantenedores suelen responder en 2 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 67/100
Los mantenedores suelen responder en 1 día