[Replicant] error while sending image with Conversations through Orbot

Adonay Felipe Nogueira adfeno at hyperbola.info
Mon Oct 4 13:08:14 UTC 2021


Em 04/10/2021 09:43, Fil Lupin via Replicant escreveu:
> looking further, I noticed that sending a MMS is also impossible (but sending SMS is OK).
> I got an adb logcat in case someone could help me with this problem.
> 
> I would think this is an access right issue, so I checked rights (read for owner, group and others) and tried to send an image from another directory (in fact same image, renaming filename to avoid space and special caracters), but error still remains.
> 
> Do you have any idea of tests I could do or what could possibly cause this error?
> My device is a Replicant 4.2 on GT-I9300.
> 
> Thank you,
> 
> - Fil Lupin.
> 
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Thursday, September 30th, 2021 at 10:30 PM, Fil Lupin via Replicant <replicant at osuosl.org> wrote:
> 
>> Hello,
>> I use a Galaxy S3 with Replicant 4.2
>> Using Conversations 2.9.3 through Orbot 16.4.1-RC2, I encounter an error while sending an image: "Failure to connect to SOCKS server".
>> When I look into my filesystem, I find the image in /storage/emulated/legacy/Conversations/Media/Conversations Images/fdc86176-f9ec-4b48-9b16-b220f9985bf3.jpg
>> Perhaps there is a rights issue.
>>
>> Here is output of logcat :
>> ---
>> D/conversations( 6999): send file message
>> D/conversations( 6999): using 12-byte IV for file transmission
>> I/Choreographer( 6999): Skipped 31 frames! The application may be doing too much work on its main thread.
>> D/conversations( 6999): uploading to https://xmpp.chapril.org/upload/cfee2913ce572d9ebb0a968a72b035ab87396582/e8glJguTZm0mF3fUbDcj/_chhdvnsS0ibFrIg-Zhb8w.jpg w/ read timeout of 56s
>> W/System.err( 6999): java.io.IOException: Failure to connect to SOCKS server
>> W/System.err( 6999): at java.net.PlainSocketImpl.socksRequestConnection(PlainSocketImpl.java:345)
>> W/System.err( 6999): at java.net.PlainSocketImpl.socksConnect(PlainSocketImpl.java:329)
>> W/System.err( 6999): at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:190)
>> W/System.err( 6999): at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:459)
>> W/System.err( 6999): at java.net.Socket.connect(Socket.java:842)
>> W/System.err( 6999): at libcore.net.http.HttpConnection.<init>(HttpConnection.java:76)
>> W/System.err( 6999): at libcore.net.http.HttpConnection.<init>(HttpConnection.java:50)
>> W/System.err( 6999): at libcore.net.http.HttpConnection$Address.connect(HttpConnection.java:340)
>> W/System.err( 6999): at libcore.net.http.HttpConnectionPool.get(HttpConnectionPool.java:87)
>> W/System.err( 6999): at libcore.net.http.HttpConnection.connect(HttpConnection.java:98)
>> W/System.err( 6999): at libcore.net.http.HttpEngine.openSocketConnection(HttpEngine.java:316)
>> W/System.err( 6999): at libcore.net.http.HttpsURLConnectionImpl$HttpsEngine.makeSslConnection(HttpsURLConnectionImpl.java:461)
>> W/System.err( 6999): at libcore.net.http.HttpsURLConnectionImpl$HttpsEngine.connect(HttpsURLConnectionImpl.java:442)
>> W/System.err( 6999): at libcore.net.http.HttpEngine.sendSocketRequest(HttpEngine.java:290)
>> W/System.err( 6999): at libcore.net.http.HttpEngine.sendRequest(HttpEngine.java:240)
>> W/System.err( 6999): at libcore.net.http.HttpURLConnectionImpl.connect(HttpURLConnectionImpl.java:81)
>> W/System.err( 6999): at libcore.net.http.HttpsURLConnectionImpl.connect(HttpsURLConnectionImpl.java:165)
>> W/System.err( 6999): at eu.siacs.conversations.http.HttpUploadConnection.upload(HttpUploadConnection.java:187)
>> W/System.err( 6999): at eu.siacs.conversations.http.HttpUploadConnection.access$300(HttpUploadConnection.java:30)
>> W/System.err( 6999): at eu.siacs.conversations.http.HttpUploadConnection$1.lambda$success$0(HttpUploadConnection.java:139)
>> W/System.err( 6999): at eu.siacs.conversations.http.-$$Lambda$HttpUploadConnection$1$ektaHXFqxgW3UQRYD5-n6pWZA0w.run(lambda)
>> W/System.err( 6999): at java.lang.Thread.run(Thread.java:856)
>> D/conversations( 6999): http upload failed Failure to connect to SOCKS server
>> W/InputMethodManagerService( 2264): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy at 41ee4838 attribute=null, token = android.os.BinderProxy at 41ecd1c0
>> D/conversations( 6999): xxx at xxx: suppressing failed delivery notification because conversation is open

If I recall, some things can't be sent over Tor, particularly anything
other than text.

Besides, it would also be good for you to contact Chapril and ask them
to further test their server setup, since there is no known compliance
tests for that service provider ([1]).


# References


[1]: https://compliance.conversations.im/server/xmpp.chapril.org/

-- 
* https://libreplanet.org/wiki/User:Adfeno
* Ativista do software livre
  * Não sou advogado e não avalio: vide seção #Inativas no endereço
    acima para saber quem faz
* Diga não às drogas… e ao JavaScript empurrado nas páginas da Internet
* Docs., planilhas e apresentações: use NBR ISO/IEC 26300:2008 e
  versões posteriores do OpenDocument
* Outros tipos de arquivos: vide endereço anterior
* Não assuma que eu tenho as mesmas fontes de texto que usas
* Mensagens secretas somente via
  * XMPP com OMEMO


More information about the Replicant mailing list