Threema Web not working

Question

6

Threema Web not working

Tracked by Jolla (In progress)

asked 2019-03-25 21:40:56 +0300

This post is a wiki. Anyone with karma >75 is welcome to improve it.

updated 2019-03-26 17:26:54 +0300

markus_wes
36 ●3 ●5 ●9

I installed Threema via it's apk download on SailfishX 3.0.1.14 running on a Sony XA2. It works pretty well, except for threema web which seems to be unable to create a connection to the Sailfish phone.

Actually the connection process starts but then comes to an end at 60% asking whether:

The phone is online (which it is via WiFi)
If there is a browser-plugin installed blocking WebRTC
If there is an Ad-Blocker installed

I've tried with a Win10 PC using latest Firefox and Vivaldi browser. For both there is neither a adblocker active, nore I have WebRTC blocked. Therefore as I don't think one of the above is the issue, I'm hoping for help here. Any ideas?

EDIT due to @bomo:

I didn't know about the diagnostics until now, thanks for the hint!

The WebRTC Diagnostics outputs:

Starting Call Diagnostics...
Settings: force_turn=0
ICE Candidates found:
Done!

Threema Web Diagnostics outputs:

Starting Threema Web Diagnostics...
----------------
Networks (o):
----------------
Non-loopback interfaces (2):
- 192.168.x.x
- fe80::xxxx:xxxx:xxxx:xxxx%wlan0 [link-local]
----------------
+0ms Starting WS tests
+24ms Connecting to WebSocket
+25ms WS state changed to CONNECTING
+466ms WS state changed to OPEN
+475ms WS connected (192.168.x.x:45334 -> 5.148.189.211:443)
+476ms WS received 81 bytes
+483ms Received server-hello message!
+484ms WS state changed to CLOSING
+541ms WS state changed to CLOSED
+541ms WS closed by us with code 1000 (Normal closing)
+542ms WS tests complete (success=true)
----------------
+0ms Starting WebRTC tests
+0ms Setting: allowWebrtcIpv6=false
+76ms ICE renegotiation needed
+77ms SDP create success
+79ms PC signaling state change to HAVE_LOCAL_OFFER
+86ms SDP set success
+86ms ICE gathering state change to GATHERING
+92ms [host] udp ::1:58225
+92ms [host] udp ::1:58225
+93ms [host] udp 127.0.0.1:33106
+94ms [host] udp 127.0.0.1:33106
+206ms [host] tcp/active 192.168.x.x:9
+207ms [host] tcp/active 192.168.x.x:9
+208ms [host] tcp/passive ::1:59122
+208ms [host] tcp/passive ::1:59122
+209ms [host] tcp/passive 127.0.0.1:53149
+209ms [host] tcp/passive 127.0.0.1:53149
+11994ms WebRTC test timed out
+11995ms WebRTC tests complete (success=true)
----------------
Done.

Seem that WebRTC has timed out what doesn't look promising although it mentions a success at the end...

edit retag flag offensive close delete

Comments

I think it's the WebRTC.

Spark ( 2019-03-25 21:45:41 +0300 )edit

Did you check threema settings -> troubleshooting -> web and webrtc diagnostics?

bomo ( 2019-03-26 00:05:40 +0300 )edit

Just a stupid guess, but is it possible that the LXC container that runs aliendalvik on XA2 is not forwarding and/or blocking traffic? Maybe google around for how to enable forwarding from LXC to host etc.

bomo ( 2019-03-26 13:24:32 +0300 )edit

1

When I connect via 4G-Network I can use Threema Web, however the connection is rather fragile. With WIFI it doesn't work, in the Web-UI it starts loading the session and stops at 60% with the message that the connection takes too long.

jollajo ( 2019-03-26 13:28:30 +0300 )edit

1

Just realised that if I disable IPv6 for my Threema-Settings-TroubleShooting-IPv6 for calls and web it also works on Wifi. My mobile operator (Vodafone, Germany) only supports IPv4 so it seems be that IPv6 routing has an issue.

jollajo ( 2019-03-26 13:32:39 +0300 )edit

I think it's the WebRTC.
Spark ( 2019-03-25 21:45:41 +0300 )edit
Did you check threema settings -> troubleshooting -> web and webrtc diagnostics?
bomo ( 2019-03-26 00:05:40 +0300 )edit
Just a stupid guess, but is it possible that the LXC container that runs aliendalvik on XA2 is not forwarding and/or blocking traffic? Maybe google around for how to enable forwarding from LXC to host etc.
bomo ( 2019-03-26 13:24:32 +0300 )edit
When I connect via 4G-Network I can use Threema Web, however the connection is rather fragile. With WIFI it doesn't work, in the Web-UI it starts loading the session and stops at 60% with the message that the connection takes too long.
jollajo ( 2019-03-26 13:28:30 +0300 )edit
Just realised that if I disable IPv6 for my Threema-Settings-TroubleShooting-IPv6 for calls and web it also works on Wifi. My mobile operator (Vodafone, Germany) only supports IPv4 so it seems be that IPv6 routing has an issue.
jollajo ( 2019-03-26 13:32:39 +0300 )edit

Answer 1

1

answered 2020-02-28 16:19:59 +0300

chris7chris
213 ●4 ●9 ●12

Threema.web does not work Neither wifi, nor through web. XA2, Nuuksio, Threema 4.2

edit flag offensive delete publish link

Comments

there is already Threema 4.3 out... i tried it yesterday and it worked fine! (Firefox) (XA2)

Raymaen ( 2020-02-28 17:38:53 +0300 )edit

@Raymaen have you tested it twice? with mobile data and with wifi?

h___m ( 2020-02-28 21:07:56 +0300 )edit

yes i testd that with wifi and with mobile data. works fine! but i had problems at work testing it with mobile data an the edge browser. but maybe there were some security limitations that blocked the connection... there was a message about not supporting something.... so check your settings and use firefox.

Raymaen ( 2020-02-28 22:24:01 +0300 )edit

I am at a loss.

I changed the device from XperiaX to XperiaXA2. Both SailfishX versions are 3.2.1.20. Threema is 4.3, both. On XperiaX ThreemaWeb works on wifi and mobile data. With the XA2 it works only with mobile data, on wifi it stucks at 60% as described above. Same PC, same Firefox browser, same Wifi network.

In Threema on XA2 are additional options for disabling IPv6. Changing this has no effect.

h___m ( 2020-02-29 11:04:17 +0300 )edit

Threema Web now also works for me on Wifi with Firefox, XA2+, SFOS 3.2.1. and the new Threema 4.3

Resuming a Session doesn't work, though.

jollajo ( 2020-02-29 12:56:16 +0300 )edit

Accepted Answer

2

answered 2019-07-25 10:17:27 +0300

markus_wes
36 ●3 ●5 ●9

Lately I was notified that there is an update of Threema to version 4.0.2. After installing the update Threema Web seems to work fine on Sailfish 3.0.3.10 via both WiFi and mobile data.

Anyone else to confirm this?

edit flag offensive delete publish link

Comments

Hm, seems it worked only a single time for me.

markus_wes ( 2019-07-25 13:18:05 +0300 )edit

works for me too now (Firefox 60esr). More than once :)

Spark ( 2019-07-25 14:31:21 +0300 )edit

I'm still on Threema 3.7 and Threema Web now works with SFOS 3.1.0 with Chromium. Unfortunately the Web-Session does not survive an Suspend-Resume cylcle of the PC.

jollajo ( 2019-07-25 15:18:42 +0300 )edit

I just installed SFOS 3.1.0.11 and it seems to work again now (with Firefox). I'll do some further testing and report when I have something reproducible...

markus_wes ( 2019-07-25 15:20:56 +0300 )edit

Same to me, works again also with wlan, tested for several times

triessner ( 2019-08-12 19:14:11 +0300 )edit

Answer 3

6

answered 2019-05-03 00:49:42 +0300

triessner

171 ●8 ●12 ●15

updated 2020-03-03 12:19:32 +0300

Spark
4216 ●67 ●91 ●99

I can confirm jollajo's observations. Threema web works with 4G and doesn't work with WLAN. I have a Xperia XA2 and SailfishOS 3.0.3.9. I've had contact to threema support and made some analytics for them. After that they said, that there is a problem during the phase of collecting some network information, so called ICE Candidates. Threema uses the STUN/TURN protokoll for that.

I hope, this information helps the Sailfish Team to solve the issue. I've opened a ticket at jolla support already.

[edit by Spark, 3 Feb 2020] Sorry to hijack this post, but I can specify this further by a Threema support answer: It seems that Sailfish is not able to collect reflexive and relay candidates when collecting ICE-candidates (interactive connectivity establishment) with a STUN/TURN-server. This might be related to the network protocol or the configuration of the network stack. Threema uses the WebRTC library for Threema Calls.

So this is not only the reason why threema web doesn't work properly but also Threema Calls.

edit flag offensive delete publish link

Comments

After installing 3.0.3.9 today I can confirm this behavior. Please keep us updated if there are any news on the ticket...

markus_wes ( 2019-05-07 23:04:12 +0300 )edit

The jolla team has marked this thread as "Tracked by Jolla" (see direct below the title "Threema Web not working"). But their response was not very promising:

Due to our limited resources, we cannot (usually) fix issues in the operation of individual Android apps on Sailfish OS. However, if the issue appears to be generic, meaning that it could be harmful to other apps, too, then we might be able to allocate the needed developer resources to fix the issue.

Hence the "tracking" tag here is not a promise of fixing it but an indication that a bug has been filed and the issue is in the backlog of our R&D.
Let's hope for the best.

triessner ( 2019-05-15 16:51:37 +0300 )edit

Threema Web not working

Comments

3 Answers

Comments

Comments

Comments

Question tools

Stats

Related questions

Threema Web not working

Comments

3 Answers

Comments

Comments

Comments

Question tools

Public thread

Stats

Related questions