Revision history [back]

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:

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

As I don't think one of the above is the issue, I'm hoping for help here. Any ideas?

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:

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:

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

As 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?

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:

1. The phone is online (which it is via WiFi)
2. If there is a browser-plugin installed blocking WebRTC
3. 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?

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

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.

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:

1. The phone is online (which it is via WiFi)
2. If there is a browser-plugin installed blocking WebRTC
3. 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...