Ich versuche Threema Web mit dem neuesten Firefox zu verwenden. Zuerst sieht alles gut aus, aber das Verbinden bleibt bei 60% hängen. Woran kann das liegen?
Threema Web verbindet nicht
-
-
16. Februar 2017 um 09:41 -
Erledigt
Stelle deine Frage öffentlich an die Threema-Forum-Community - über 4.800 Mitglieder helfen dir weiter. > Frage stellen <
-
-
Ich habe genau das gleiche Problem. Hat jemand Hilfe?
-
Könnt ihr folgende Fragen beantworten?
- Welchen Browser mit Version verwendet ihr?
- Welche Addons habt ihr installiert (z. B. NoScript)?
- In welchem Netzwerk habt ihr es ausprobiert? Daheim hinter einem normalen Router? In der Firma, etc.?
-
* Ich verwende Firefox 51.0.1
* Ich habe eben geguckt. Da war nur ein Addon, Yahoo Mail. Habe ich entfernt
* Ich bin in meinem eigenen kleinen Büro. Das Handy ist über WLAN mit demselben verbunden. Ich denke ich habe einen Router im Keller (...??) -
advoba: Alles klar.
Kannst du bitte mal folgendes machen:
1. Geh auf about:webrtc in Firefox
2. Auf Debug-Modus starten klicken
3. Historie und Log erstmal löschen
4. Geh auf https://web.threema.ch und versuche eine Sitzung zu starten
5. Warte 1-2 Minuten während die Web-App bei 60 % hängen bleibt
6. Geh in einem anderen Tab wieder auf about:webrtc
7. Poste die Sitzungsstatistik & Log -
PeerConnection-ID: 1487238429208000 (id=67 url=https://web.threema.ch/#/welcome)
ICE-Statistiken
Lokaler Kandidat Externer Kandidat ICE-Status Priorität Nominiert Ausgewählt
192.168.0.19:56654/udp(host) 198.18.9.54:39214/udp(host) failed 9114756780654461000
192.168.0.19:56654/udp(host) 192.168.0.27:45240/udp(host) failed 9114475305677750000
5.148.175.222:52359/udp(relayed-udp) 198.18.9.54:39214/udp(host) failed 396069377041776100
5.148.175.222:52359/udp(relayed-udp) 192.168.0.27:45240/udp(host) failed 396069377041645060
87.167.2.36:56654/udp(serverreflexive)
fc00:fed0:0:1002::104c:39008/udp(host)
::1:44051/udp(host)
127.0.0.1:43233/udp(host)
fc00:fed0:0:1002::104c:39597/tcp(host)
198.18.9.54:46749/tcp(host)
192.168.0.27:41967/tcp(host)
::1:48624/tcp(host)
127.0.0.1:46728/tcp(host)
SDP
Lokales SDPv=0
o=mozilla...THIS_IS_SDPARTA-51.0.1 1882832088680462931 0 IN IP4 0.0.0.0
s=-
t=0 0
a=sendrecv
a=fingerprint:sha-256 D5:67:9E:A3:41:A8:D4:6A:A2:5D:F1:3A:FC:6C:49:D9:59:6E:45:3B:CE:D7:8C:9B:F2:D4:DE:77:A3:0D:8D:07
a=ice-options:trickle
a=msid-semantic:WMS *
m=application 52359 DTLS/SCTP 5000
c=IN IP4 5.148.175.222
a=candidate:0 1 UDP 2122252543 192.168.0.19 56654 typ host
a=candidate:1 1 UDP 1686052863 87.167.2.36 56654 typ srflx raddr 192.168.0.19 rport 56654
a=candidate:3 1 UDP 92217087 5.148.175.222 52359 typ relay raddr 5.148.175.222 rport 52359
a=sendrecv
a=end-of-candidates
a=ice-pwd:76d8d0e12172c6a10db66585313b9472
a=ice-ufrag:e40cb58e
a=mid:sdparta_0
a=sctpmap:5000 webrtc-datachannel 256
a=setup:actpass
a=ssrc:1430814263 cname:{9f58a6dc-de5a-410a-a9f9-8a9b4feb520c}
Externes SDP
v=0
o=- 4530519073936962839 2 IN IP4 127.0.0.1
s=-
t=0 0
a=sendrecv
a=msid-semantic:WMS
m=application 9 DTLS/SCTP 5000
c=IN IP4 0.0.0.0
b=AS:30
a=candidate:3294058170 1 udp 2122265343 fc00:fed0:0:1002::104c 39008 typ host generation 0 ufrag rFG4 network-id 4 network-cost 50
a=candidate:1807820786 1 udp 2122194687 198.18.9.54 39214 typ host generation 0 ufrag rFG4 network-id 3 network-cost 50
a=candidate:2399860533 1 udp 2122129151 192.168.0.27 45240 typ host generation 0 ufrag rFG4 network-id 5 network-cost 10
a=candidate:559267639 1 udp 2122071295 ::1 44051 typ host generation 0 ufrag rFG4 network-id 2
a=candidate:1510613869 1 udp 2121998079 127.0.0.1 43233 typ host generation 0 ufrag rFG4 network-id 1
a=candidate:2329193034 1 tcp 1518285567 fc00:fed0:0:1002::104c 39597 typ host tcptype passive generation 0 ufrag rFG4 network-id 4 network-cost 50
a=candidate:625138434 1 tcp 1518214911 198.18.9.54 46749 typ host tcptype passive generation 0 ufrag rFG4 network-id 3 network-cost 50
a=candidate:3246984133 1 tcp 1518149375 192.168.0.27 41967 typ host tcptype passive generation 0 ufrag rFG4 network-id 5 network-cost 10
a=candidate:1876313031 1 tcp 1518091519 ::1 48624 typ host tcptype passive generation 0 ufrag rFG4 network-id 2
a=candidate:344579997 1 tcp 1518018303 127.0.0.1 46728 typ host tcptype passive generation 0 ufrag rFG4 network-id 1
a=sendrecv
a=fingerprint:sha-256 7E:DF:F1:3D:83:8A:84:F7:73:74:6B:3A:A1:14:95:85:CB:00:BD:43:56:AA:2F:51:04:51:9E:03:C4:FA:76:07
a=ice-options:renomination
a=ice-pwd:QWK8m06LWzw/XXs9vmjKdUIJ
a=ice-ufrag:rFG4
a=mid:sdparta_0
a=sctpmap:5000 webrtc-datachannel 1024
a=setup:active
RTP-Statistiken
[hr]
(stun/INFO) STUN-CLIENT(relay(IP4:192.168.0.19:56654/UDP|turn.threema.ch:443)::TURN): Received response; processing(stun/WARNING) STUN-CLIENT(relay(IP4:192.168.0.19:56654/UDP|turn.threema.ch:443)::TURN): Error processing response: Retry may be possible, stun error code 401.
(stun/INFO) Unrecognized attribute: 0x802b
(stun/INFO) Unrecognized attribute: 0x802c
(stun/WARNING) Inconsistent message method: 101 expected 003
(stun/INFO) Unrecognized attribute: 0x802b
(stun/INFO) Unrecognized attribute: 0x802c
(stun/INFO) STUN-CLIENT(srflx(IP4:192.168.0.19:56654/UDP|stun.threema.ch:443)): Received response; processing
(stun/INFO) STUN-CLIENT(relay(IP4:192.168.0.19:56654/UDP|turn.threema.ch:443)::TURN): Received response; processing
(turn/INFO) TURN(relay(IP4:192.168.0.19:56654/UDP|turn.threema.ch:443)): Succesfully allocated addr IP4:5.148.175.222:52359/UDP lifetime=3600
(ice/NOTICE) ICE(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome)): peer (PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome):default) no streams with non-empty check lists
(ice/NOTICE) ICE(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome)): peer (PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome):default) no streams with pre-answer requests
(ice/NOTICE) ICE(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome)): peer (PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome):default) no checks to start
(ice/INFO) ICE-PEER(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome):default)/ICE-STREAM(0-1487238429208000 (id=67 url=https://web.threema.ch/#/welcome) aLevel=0): Starting check timer for stream.
(ice/WARNING) ICE-PEER(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome):default): no pairs for 0-1487238429208000 (id=67 url=https://web.threema.ch/#/welcome) aLevel=0
(ice/NOTICE) ICE(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome)): peer (PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome):default) is now checking
(ice/INFO) ICE-PEER(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome):default)/CAND-PAIR(l/wK): setting pair to state FROZEN: l/wK|IP4:192.168.0.19:56654/UDP|IP4:198.18.9.54:39214/UDP(host(IP4:192.168.0.19:56654/UDP)|candidate:1807820786 1 udp 2122194687 198.18.9.54 39214 typ host generation 0 ufrag rFG4 network-id 3 network-cost 50)
(ice/INFO) ICE(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome))/CAND-PAIR(l/wK): Pairing candidate IP4:192.168.0.19:56654/UDP (7e7f00ff):IP4:198.18.9.54:39214/UDP (7e7e1eff) priority=9114756780654461439 (7e7e1efffcfe01ff)
(ice/INFO) ICE-PEER(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome):default)/ICE-STREAM(0-1487238429208000 (id=67 url=https://web.threema.ch/#/welcome) aLevel=0): Starting check timer for stream.
(ice/INFO) ICE-PEER(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome):default)/CAND-PAIR(l/wK): setting pair to state WAITING: l/wK|IP4:192.168.0.19:56654/UDP|IP4:198.18.9.54:39214/UDP(host(IP4:192.168.0.19:56654/UDP)|candidate:1807820786 1 udp 2122194687 198.18.9.54 39214 typ host generation 0 ufrag rFG4 network-id 3 network-cost 50)
(ice/INFO) ICE-PEER(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome):default)/CAND-PAIR(l/wK): setting pair to state IN_PROGRESS: l/wK|IP4:192.168.0.19:56654/UDP|IP4:198.18.9.54:39214/UDP(host(IP4:192.168.0.19:56654/UDP)|candidate:1807820786 1 udp 2122194687 198.18.9.54 39214 typ host generation 0 ufrag rFG4 network-id 3 network-cost 50)
(ice/INFO) ICE-PEER(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome):default)/CAND-PAIR(XYg/): setting pair to state FROZEN: XYg/|IP4:5.148.175.222:52359/UDP|IP4:198.18.9.54:39214/UDP(turn-relay(IP4:192.168.0.19:56654/UDP|IP4:5.148.175.222:52359/UDP)|candidate:1807820786 1 udp 2122194687 198.18.9.54 39214 typ host generation 0 ufrag rFG4 network-id 3 network-cost 50)
(ice/INFO) ICE(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome))/CAND-PAIR(XYg/): Pairing candidate IP4:5.148.175.222:52359/UDP (57f1eff):IP4:198.18.9.54:39214/UDP (7e7e1eff) priority=396069377041776126 (57f1efffcfc3dfe)
(ice/INFO) ICE-PEER(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome):default)/CAND-PAIR(XYg/): setting pair to state WAITING: XYg/|IP4:5.148.175.222:52359/UDP|IP4:198.18.9.54:39214/UDP(turn-relay(IP4:192.168.0.19:56654/UDP|IP4:5.148.175.222:52359/UDP)|candidate:1807820786 1 udp 2122194687 198.18.9.54 39214 typ host generation 0 ufrag rFG4 network-id 3 network-cost 50)
(ice/INFO) ICE-PEER(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome):default)/CAND-PAIR(XYg/): setting pair to state IN_PROGRESS: XYg/|IP4:5.148.175.222:52359/UDP|IP4:198.18.9.54:39214/UDP(turn-relay(IP4:192.168.0.19:56654/UDP|IP4:5.148.175.222:52359/UDP)|candidate:1807820786 1 udp 2122194687 198.18.9.54 39214 typ host generation 0 ufrag rFG4 network-id 3 network-cost 50)
(turn/INFO) TURN(relay(IP4:192.168.0.19:56654/UDP|turn.threema.ch:443)): Creating permission for IP4:198.18.9.54:39214/UDP
(ice/WARNING) ICE-PEER(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome):default): no pairs for 0-1487238429208000 (id=67 url=https://web.threema.ch/#/welcome) aLevel=0
(stun/INFO) STUN-CLIENT(relay(IP4:192.168.0.19:56654/UDP|turn.threema.ch:443)::TURN): Received response; processing
(ice/INFO) ICE-PEER(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome):default)/CAND-PAIR(yXvH): setting pair to state FROZEN: yXvH|IP4:192.168.0.19:56654/UDP|IP4:192.168.0.27:45240/UDP(host(IP4:192.168.0.19:56654/UDP)|candidate:2399860533 1 udp 2122129151 192.168.0.27 45240 typ host generation 0 ufrag rFG4 network-id 5 network-cost 10)
(ice/INFO) ICE(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome))/CAND-PAIR(yXvH): Pairing candidate IP4:192.168.0.19:56654/UDP (7e7f00ff):IP4:192.168.0.27:45240/UDP (7e7d1eff) priority=9114475305677750783 (7e7d1efffcfe01ff)
(ice/INFO) ICE-PEER(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome):default)/ICE-STREAM(0-1487238429208000 (id=67 url=https://web.threema.ch/#/welcome) aLevel=0): Starting check timer for stream.
(ice/INFO) ICE-PEER(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome):default)/CAND-PAIR(yXvH): setting pair to state WAITING: yXvH|IP4:192.168.0.19:56654/UDP|IP4:192.168.0.27:45240/UDP(host(IP4:192.168.0.19:56654/UDP)|candidate:2399860533 1 udp 2122129151 192.168.0.27 45240 typ host generation 0 ufrag rFG4 network-id 5 network-cost 10)
(ice/INFO) ICE-PEER(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome):default)/CAND-PAIR(yXvH): setting pair to state IN_PROGRESS: yXvH|IP4:192.168.0.19:56654/UDP|IP4:192.168.0.27:45240/UDP(host(IP4:192.168.0.19:56654/UDP)|candidate:2399860533 1 udp 2122129151 192.168.0.27 45240 typ host generation 0 ufrag rFG4 network-id 5 network-cost 10)
(ice/INFO) ICE-PEER(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome):default)/CAND-PAIR(vF9E): setting pair to state FROZEN: vF9E|IP4:5.148.175.222:52359/UDP|IP4:192.168.0.27:45240/UDP(turn-relay(IP4:192.168.0.19:56654/UDP|IP4:5.148.175.222:52359/UDP)|candidate:2399860533 1 udp 2122129151 192.168.0.27 45240 typ host generation 0 ufrag rFG4 network-id 5 network-cost 10)
(ice/INFO) ICE(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome))/CAND-PAIR(vF9E): Pairing candidate IP4:5.148.175.222:52359/UDP (57f1eff):IP4:192.168.0.27:45240/UDP (7e7d1eff) priority=396069377041645054 (57f1efffcfa3dfe)
(ice/INFO) ICE-PEER(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome):default)/CAND-PAIR(vF9E): setting pair to state WAITING: vF9E|IP4:5.148.175.222:52359/UDP|IP4:192.168.0.27:45240/UDP(turn-relay(IP4:192.168.0.19:56654/UDP|IP4:5.148.175.222:52359/UDP)|candidate:2399860533 1 udp 2122129151 192.168.0.27 45240 typ host generation 0 ufrag rFG4 network-id 5 network-cost 10)
(ice/INFO) ICE-PEER(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome):default)/CAND-PAIR(vF9E): setting pair to state IN_PROGRESS: vF9E|IP4:5.148.175.222:52359/UDP|IP4:192.168.0.27:45240/UDP(turn-relay(IP4:192.168.0.19:56654/UDP|IP4:5.148.175.222:52359/UDP)|candidate:2399860533 1 udp 2122129151 192.168.0.27 45240 typ host generation 0 ufrag rFG4 network-id 5 network-cost 10)
(turn/INFO) TURN(relay(IP4:192.168.0.19:56654/UDP|turn.threema.ch:443)): Creating permission for IP4:192.168.0.27:45240/UDP
(ice/WARNING) ICE-PEER(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome):default): no pairs for 0-1487238429208000 (id=67 url=https://web.threema.ch/#/welcome) aLevel=0
(stun/INFO) STUN-CLIENT(relay(IP4:192.168.0.19:56654/UDP|turn.threema.ch:443)::TURN): Received response; processing
(ice/INFO) ICE-PEER(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome):default)/ICE-STREAM(0-1487238429208000 (id=67 url=https://web.threema.ch/#/welcome) aLevel=0): Starting check timer for stream.
(ice/WARNING) ICE-PEER(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome):default): no pairs for 0-1487238429208000 (id=67 url=https://web.threema.ch/#/welcome) aLevel=0
(ice/INFO) ICE-PEER(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome):default)/ICE-STREAM(0-1487238429208000 (id=67 url=https://web.threema.ch/#/welcome) aLevel=0): Starting check timer for stream.
(ice/WARNING) ICE-PEER(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome):default): no pairs for 0-1487238429208000 (id=67 url=https://web.threema.ch/#/welcome) aLevel=0
(ice/INFO) ICE-PEER(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome):default)/ICE-STREAM(0-1487238429208000 (id=67 url=https://web.threema.ch/#/welcome) aLevel=0): Starting check timer for stream.
(ice/WARNING) ICE-PEER(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome):default): no pairs for 0-1487238429208000 (id=67 url=https://web.threema.ch/#/welcome) aLevel=0
(ice/INFO) ICE-PEER(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome):default)/ICE-STREAM(0-1487238429208000 (id=67 url=https://web.threema.ch/#/welcome) aLevel=0): Starting check timer for stream.
(ice/WARNING) ICE-PEER(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome):default): no pairs for 0-1487238429208000 (id=67 url=https://web.threema.ch/#/welcome) aLevel=0
(ice/INFO) ICE-PEER(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome):default)/ICE-STREAM(0-1487238429208000 (id=67 url=https://web.threema.ch/#/welcome) aLevel=0): Starting check timer for stream.
(ice/WARNING) ICE-PEER(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome):default): no pairs for 0-1487238429208000 (id=67 url=https://web.threema.ch/#/welcome) aLevel=0
(ice/INFO) ICE-PEER(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome):default)/ICE-STREAM(0-1487238429208000 (id=67 url=https://web.threema.ch/#/welcome) aLevel=0): Starting check timer for stream.
(ice/WARNING) ICE-PEER(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome):default): no pairs for 0-1487238429208000 (id=67 url=https://web.threema.ch/#/welcome) aLevel=0
(ice/INFO) ICE(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome)): peer (PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome):default) Trickle grace period is over; marking every component with only failed pairs as failed.
(stun/INFO) STUN-CLIENT(l/wK|IP4:192.168.0.19:56654/UDP|IP4:198.18.9.54:39214/UDP(host(IP4:192.168.0.19:56654/UDP)|candidate:1807820786 1 udp 2122194687 198.18.9.54 39214 typ host generation 0 ufrag rFG4 network-id 3 network-cost 50)): Timed out
(ice/INFO) ICE-PEER(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome):default)/CAND-PAIR(l/wK): setting pair to state FAILED: l/wK|IP4:192.168.0.19:56654/UDP|IP4:198.18.9.54:39214/UDP(host(IP4:192.168.0.19:56654/UDP)|candidate:1807820786 1 udp 2122194687 198.18.9.54 39214 typ host generation 0 ufrag rFG4 network-id 3 network-cost 50)
(stun/INFO) STUN-CLIENT(XYg/|IP4:5.148.175.222:52359/UDP|IP4:198.18.9.54:39214/UDP(turn-relay(IP4:192.168.0.19:56654/UDP|IP4:5.148.175.222:52359/UDP)|candidate:1807820786 1 udp 2122194687 198.18.9.54 39214 typ host generation 0 ufrag rFG4 network-id 3 network-cost 50)): Timed out
(ice/INFO) ICE-PEER(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome):default)/CAND-PAIR(XYg/): setting pair to state FAILED: XYg/|IP4:5.148.175.222:52359/UDP|IP4:198.18.9.54:39214/UDP(turn-relay(IP4:192.168.0.19:56654/UDP|IP4:5.148.175.222:52359/UDP)|candidate:1807820786 1 udp 2122194687 198.18.9.54 39214 typ host generation 0 ufrag rFG4 network-id 3 network-cost 50)
(stun/INFO) STUN-CLIENT(yXvH|IP4:192.168.0.19:56654/UDP|IP4:192.168.0.27:45240/UDP(host(IP4:192.168.0.19:56654/UDP)|candidate:2399860533 1 udp 2122129151 192.168.0.27 45240 typ host generation 0 ufrag rFG4 network-id 5 network-cost 10)): Timed out
(ice/INFO) ICE-PEER(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome):default)/CAND-PAIR(yXvH): setting pair to state FAILED: yXvH|IP4:192.168.0.19:56654/UDP|IP4:192.168.0.27:45240/UDP(host(IP4:192.168.0.19:56654/UDP)|candidate:2399860533 1 udp 2122129151 192.168.0.27 45240 typ host generation 0 ufrag rFG4 network-id 5 network-cost 10)
(stun/INFO) STUN-CLIENT(vF9E|IP4:5.148.175.222:52359/UDP|IP4:192.168.0.27:45240/UDP(turn-relay(IP4:192.168.0.19:56654/UDP|IP4:5.148.175.222:52359/UDP)|candidate:2399860533 1 udp 2122129151 192.168.0.27 45240 typ host generation 0 ufrag rFG4 network-id 5 network-cost 10)): Timed out
(ice/INFO) ICE-PEER(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome):default)/CAND-PAIR(vF9E): setting pair to state FAILED: vF9E|IP4:5.148.175.222:52359/UDP|IP4:192.168.0.27:45240/UDP(turn-relay(IP4:192.168.0.19:56654/UDP|IP4:5.148.175.222:52359/UDP)|candidate:2399860533 1 udp 2122129151 192.168.0.27 45240 typ host generation 0 ufrag rFG4 network-id 5 network-cost 10)
(ice/INFO) ICE-PEER(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome):default)/STREAM(0-1487238429208000 (id=67 url=https://web.threema.ch/#/welcome) aLevel=0)/COMP(1): All pairs are failed, and grace period has elapsed. Marking component as failed.
(ice/INFO) ICE-PEER(PC:1487238429208000 (id=67 url=https://web.threema.ch/#/welcome):default): all checks completed success=0 fail=1
+++++++ END ++++++++
-
Danke schonmal. Bitte versuche sowas in einen Codeblock zu packen, dann ist es etwas leichter zu lesen.
Kannst du vielleicht noch folgendes machen?
1. Geh auf https://web.threema.ch
2. Drücke F12
3. Geh auf "Konsole" -> "Logbuch"
4. Erstmal Inhalt leeren
5. Jetzt versuchen eine Sitzung mit Threema Web zu starten
6. Poste LogNoch eine Frage:
- Schau mal unter about:config welchen Wert du bei "media.peerconnection.enabled" hast
-
Könnt ihr folgende Fragen beantworten?- Welchen Browser mit Version verwendet ihr?
- Welche Addons habt ihr installiert (z. B. NoScript)?
- In welchem Netzwerk habt ihr es ausprobiert? Daheim hinter einem normalen Router? In der Firma, etc.?
Ich habe das genau gleiche Problem.
Firefox 51.0.1 für Windows
Addon zum Löschen von LSO/SuperCookies/HTML5 DOM
FirmaSehr ähnliches Debug-Log.
about:config
media.peerconnection.enabled:
Standard, boolean, true -
sstork:
Kannst du auch mal gucken, welchen Wert du bei media.peerconnection.enabled unter about:config hast? Und dann mal den Log posten (F12, siehe Post oben). -
about:config
media.peerconnection.enabled:
Standard, boolean, true -
sstork:
Was sagt Firefox so (F12 -> Konsole -> Logbuch)?Bei Firmen halte ich es für möglich, dass es Probleme gibt mit P2P-Verbindungen (Firewall, etc.).
-
Danke Crixus! Sorry, ich kenne mich nicht so aus. Was ist ein Codeblock? Ich habe das jetzt wie zuletzt beschrieben. Hier kommt jetzt der Log:
[SaltyRTC.Initiator] Closed WebSocket connection saltyrtc-client.es5.js:995:17
[SaltyRTC.Client] New event: state-change saltyrtc-client.es5.js:2934:13
[SaltyRTC.Client] New event: state-change:closed saltyrtc-client.es5.js:2934:13
[SaltyRTC.Client] New event: connection-closed saltyrtc-client.es5.js:2934:13
Connection closed: Object { type: "connection-closed", data: 1001 } angular.js:14199:18
[SaltyRTC.Initiator] Websocket close reason: Server is being shut down saltyrtc-client.es5.js:999:28
[StateService] Connection buildup state: waiting => closed angular.js:14199:18
[StateService] Signaling connection state: peer-handshake => closed angular.js:14199:18
[StateService] Reset angular.js:14199:18
Detected browser: Firefox 51 angular.js:14199:18
Initialize session by scanning QR code... angular.js:14199:18
[StateService] Reset angular.js:14199:18
[SaltyRTC.KeyStore] New public key: cd500f1f3a04a63a31d295c0f1f0a4434b719909a8b97408743fde4c85b3322f saltyrtc-client.es5.js:467:13
[SaltyRTC.AuthToken] Generated auth token saltyrtc-client.es5.js:526:13
Starting WebClientService... angular.js:14199:18
[SaltyRTC.Client] New event: state-change saltyrtc-client.es5.js:2934:13
[SaltyRTC.Client] New event: state-change:new saltyrtc-client.es5.js:2934:13
[SaltyRTC.Client] New event: state-change saltyrtc-client.es5.js:2934:13
[SaltyRTC.Client] New event: state-change:ws-connecting saltyrtc-client.es5.js:2934:13
[SaltyRTC.Initiator] Opening WebSocket connection to wss://saltyrtc-cd.threema.ch:443/cd500f1f3a04a63a31d295c0f1f0a4434b719909a8b97408743fde4c85b3322f saltyrtc-client.es5.js:1172:13
[StateService] Signaling connection state: new => new angular.js:14199:18
[StateService] Signaling connection state: new => ws-connecting angular.js:14199:18
[SaltyRTC.Initiator] Opened connection saltyrtc-client.es5.js:984:13
[SaltyRTC.Client] New event: state-change saltyrtc-client.es5.js:2934:13
[SaltyRTC.Client] New event: state-change:server-handshake saltyrtc-client.es5.js:2934:13
[StateService] Signaling connection state: ws-connecting => server-handshake angular.js:14199:18
[SaltyRTC.Initiator] New ws message (81 bytes) saltyrtc-client.es5.js:1027:13
[SaltyRTC.Initiator] Received server-hello saltyrtc-client.es5.js:1189:21
[SaltyRTC.Initiator] Sending client-auth saltyrtc-client.es5.js:1273:13
[SaltyRTC.Initiator] New ws message (194 bytes) saltyrtc-client.es5.js:1027:13
[SaltyRTC.Initiator] Received server-auth saltyrtc-client.es5.js:1200:21
[SaltyRTC.Initiator] Expected server public permanent key is b1337fc8402f7db8ea639e05ed05d65463e24809792f91eca29e88101b4a2171 saltyrtc-client.es5.js:1435:13
[SaltyRTC.Initiator] Server public session key is 8c3da75f6cc1343571a2740d575f08047901564c8b43fbedf70e7a023c3e4d31 saltyrtc-client.es5.js:1436:13
[SaltyRTC.Initiator] 0 responders connected saltyrtc-client.es5.js:1928:13
[SaltyRTC.Client] New event: state-change saltyrtc-client.es5.js:2934:13
[SaltyRTC.Client] New event: state-change:peer-handshake saltyrtc-client.es5.js:2934:13
[SaltyRTC.Initiator] Server handshake done saltyrtc-client.es5.js:1210:17
[StateService] Connection buildup state: connecting => waiting angular.js:14199:18
[StateService] Signaling connection state: server-handshake => peer-handshake angular.js:14199:18
[SaltyRTC.Initiator] New ws message (64 bytes) saltyrtc-client.es5.js:1027:13
[SaltyRTC.Initiator] Received new-responder 0x02 saltyrtc-client.es5.js:1809:25
[SaltyRTC.KeyStore] New public key: 0cf5b40514ad4f8d940c9fc22130de38b651e6f8395e6bc60d6cd9bd39bfde22 saltyrtc-client.es5.js:467:13
[SaltyRTC.Client] New event: new-responder saltyrtc-client.es5.js:2934:13
[StateService] Connection buildup state: waiting => peer_handshake angular.js:14199:18
[SaltyRTC.Initiator] New ws message (90 bytes) saltyrtc-client.es5.js:1027:13
[SaltyRTC.Initiator] Received token saltyrtc-client.es5.js:1838:25
[SaltyRTC.Initiator] New ws message (88 bytes) saltyrtc-client.es5.js:1027:13
[SaltyRTC.Initiator] Received key saltyrtc-client.es5.js:1854:25
[SaltyRTC.Initiator] Sending key saltyrtc-client.es5.js:1962:13
[SaltyRTC.Initiator] New ws message (193 bytes) saltyrtc-client.es5.js:1027:13
[SaltyRTC.Initiator] Received auth saltyrtc-client.es5.js:1861:25
[SaltyRTC.Initiator] Task v0.webrtc.tasks.saltyrtc.org has been selected saltyrtc-client.es5.js:2001:17
[SaltyRTC.WebRTC] Max packet size: We requested 16384 bytes, peer requested 65536 bytes. Using 16384. saltyrtc-task-webrtc.es5.js:706:13
[SaltyRTC.Initiator] Responder 0x02 authenticated saltyrtc-client.es5.js:2004:13
[SaltyRTC.Initiator] Sending auth saltyrtc-client.es5.js:1981:13
[SaltyRTC.Initiator] Dropping 0 other responders. saltyrtc-client.es5.js:2038:13
[SaltyRTC.Client] New event: state-change saltyrtc-client.es5.js:2934:13
[SaltyRTC.Client] New event: state-change:task saltyrtc-client.es5.js:2934:13
Initialize WebRTC PeerConnection angular.js:14199:18
[PeerConnectionHelper] Setting up ICE candidate handling angular.js:14199:18
[SaltyRTC.WebRTC.initiator] Initiate handover saltyrtc-task-webrtc.es5.js:948:13
[PeerConnectionHelper] RTCPeerConnection: negotiation needed angular.js:14199:18
[SaltyRTC.Initiator] Peer handshake done saltyrtc-client.es5.js:1869:25
[StateService] Signaling connection state: peer-handshake => task angular.js:14199:18
[PeerConnectionHelper] Signaling state change: have-local-offer angular.js:14199:18
[PeerConnectionHelper] Created offer, set local description angular.js:14199:18
[SaltyRTC.WebRTC.initiator] Sending offer saltyrtc-task-webrtc.es5.js:874:13
[SaltyRTC.Initiator] Sending task message through ws saltyrtc-client.es5.js:1592:17
[SaltyRTC.WebRTC.initiator] Buffering 1 candidate(s) saltyrtc-task-webrtc.es5.js:920:13
[SaltyRTC.WebRTC.initiator] Sending 1 candidate(s) saltyrtc-task-webrtc.es5.js:924:21
[SaltyRTC.Initiator] Sending task message through ws saltyrtc-client.es5.js:1592:17
[SaltyRTC.WebRTC.initiator] Buffering 1 candidate(s) saltyrtc-task-webrtc.es5.js:920:13
[SaltyRTC.WebRTC.initiator] Sending 1 candidate(s) saltyrtc-task-webrtc.es5.js:924:21
[SaltyRTC.Initiator] Sending task message through ws saltyrtc-client.es5.js:1592:17
[SaltyRTC.WebRTC.initiator] Buffering 1 candidate(s) saltyrtc-task-webrtc.es5.js:920:13
[SaltyRTC.WebRTC.initiator] Sending 1 candidate(s) saltyrtc-task-webrtc.es5.js:924:21
[SaltyRTC.Initiator] Sending task message through ws saltyrtc-client.es5.js:1592:17
[SaltyRTC.Initiator] New ws message (496 bytes) saltyrtc-client.es5.js:1027:13
[SaltyRTC.Initiator] Message received saltyrtc-client.es5.js:1217:13
[SaltyRTC.Initiator] Received answer [v0.webrtc.tasks.saltyrtc.org] saltyrtc-client.es5.js:1246:17
[SaltyRTC.WebRTC.initiator] New task message arrived: answer saltyrtc-task-webrtc.es5.js:721:13
[SaltyRTC.WebRTC.initiator] New event: answer saltyrtc-task-webrtc.es5.js:1051:13
[PeerConnectionHelper] Signaling state change: stable angular.js:14199:18
[PeerConnectionHelper] Received answer, set remote description angular.js:14199:18
[PeerConnectionHelper] Initiator flow done angular.js:14199:18
[SaltyRTC.Initiator] New ws message (242 bytes) saltyrtc-client.es5.js:1027:13
[SaltyRTC.Initiator] Message received saltyrtc-client.es5.js:1217:13
[SaltyRTC.Initiator] Received candidates [v0.webrtc.tasks.saltyrtc.org] saltyrtc-client.es5.js:1246:17
[SaltyRTC.WebRTC.initiator] New task message arrived: candidates saltyrtc-task-webrtc.es5.js:721:13
[SaltyRTC.WebRTC.initiator] New event: candidates saltyrtc-task-webrtc.es5.js:1051:13
[PeerConnectionHelper] ICE connection state change: checking angular.js:14199:18
[StateService] RTC connection state: new => connecting angular.js:14199:18
[SaltyRTC.Initiator] New ws message (231 bytes) saltyrtc-client.es5.js:1027:13
[SaltyRTC.Initiator] Message received saltyrtc-client.es5.js:1217:13
[SaltyRTC.Initiator] Received candidates [v0.webrtc.tasks.saltyrtc.org] saltyrtc-client.es5.js:1246:17
[SaltyRTC.WebRTC.initiator] New task message arrived: candidates saltyrtc-task-webrtc.es5.js:721:13
[SaltyRTC.WebRTC.initiator] New event: candidates saltyrtc-task-webrtc.es5.js:1051:13
[SaltyRTC.Initiator] New ws message (232 bytes) saltyrtc-client.es5.js:1027:13
[SaltyRTC.Initiator] Message received saltyrtc-client.es5.js:1217:13
[SaltyRTC.Initiator] Received candidates [v0.webrtc.tasks.saltyrtc.org] saltyrtc-client.es5.js:1246:17
[SaltyRTC.WebRTC.initiator] New task message arrived: candidates saltyrtc-task-webrtc.es5.js:721:13
[SaltyRTC.WebRTC.initiator] New event: candidates saltyrtc-task-webrtc.es5.js:1051:13
[SaltyRTC.Initiator] New ws message (206 bytes) saltyrtc-client.es5.js:1027:13
[SaltyRTC.Initiator] Message received saltyrtc-client.es5.js:1217:13
[SaltyRTC.Initiator] Received candidates [v0.webrtc.tasks.saltyrtc.org] saltyrtc-client.es5.js:1246:17
[SaltyRTC.WebRTC.initiator] New task message arrived: candidates saltyrtc-task-webrtc.es5.js:721:13
[SaltyRTC.WebRTC.initiator] New event: candidates saltyrtc-task-webrtc.es5.js:1051:13
[SaltyRTC.Initiator] New ws message (213 bytes) saltyrtc-client.es5.js:1027:13
[SaltyRTC.Initiator] Message received saltyrtc-client.es5.js:1217:13
[SaltyRTC.Initiator] Received candidates [v0.webrtc.tasks.saltyrtc.org] saltyrtc-client.es5.js:1246:17
[SaltyRTC.WebRTC.initiator] New task message arrived: candidates saltyrtc-task-webrtc.es5.js:721:13
[SaltyRTC.WebRTC.initiator] New event: candidates saltyrtc-task-webrtc.es5.js:1051:13
[SaltyRTC.Initiator] New ws message (258 bytes) saltyrtc-client.es5.js:1027:13
[SaltyRTC.Initiator] Message received saltyrtc-client.es5.js:1217:13
[SaltyRTC.Initiator] Received candidates [v0.webrtc.tasks.saltyrtc.org] saltyrtc-client.es5.js:1246:17
[SaltyRTC.WebRTC.initiator] New task message arrived: candidates saltyrtc-task-webrtc.es5.js:721:13
[SaltyRTC.WebRTC.initiator] New event: candidates saltyrtc-task-webrtc.es5.js:1051:13
[SaltyRTC.Initiator] New ws message (246 bytes) saltyrtc-client.es5.js:1027:13
[SaltyRTC.Initiator] Message received saltyrtc-client.es5.js:1217:13
[SaltyRTC.Initiator] Received candidates [v0.webrtc.tasks.saltyrtc.org] saltyrtc-client.es5.js:1246:17
[SaltyRTC.WebRTC.initiator] New task message arrived: candidates saltyrtc-task-webrtc.es5.js:721:13
[SaltyRTC.WebRTC.initiator] New event: candidates saltyrtc-task-webrtc.es5.js:1051:13
[SaltyRTC.Initiator] New ws message (248 bytes) saltyrtc-client.es5.js:1027:13
[SaltyRTC.Initiator] Message received saltyrtc-client.es5.js:1217:13
[SaltyRTC.Initiator] Received candidates [v0.webrtc.tasks.saltyrtc.org] saltyrtc-client.es5.js:1246:17
[SaltyRTC.WebRTC.initiator] New task message arrived: candidates saltyrtc-task-webrtc.es5.js:721:13
[SaltyRTC.WebRTC.initiator] New event: candidates saltyrtc-task-webrtc.es5.js:1051:13
[SaltyRTC.Initiator] New ws message (223 bytes) saltyrtc-client.es5.js:1027:13
[SaltyRTC.Initiator] Message received saltyrtc-client.es5.js:1217:13
[SaltyRTC.Initiator] Received candidates [v0.webrtc.tasks.saltyrtc.org] saltyrtc-client.es5.js:1246:17
[SaltyRTC.WebRTC.initiator] New task message arrived: candidates saltyrtc-task-webrtc.es5.js:721:13
[SaltyRTC.WebRTC.initiator] New event: candidates saltyrtc-task-webrtc.es5.js:1051:13
[SaltyRTC.Initiator] New ws message (228 bytes) saltyrtc-client.es5.js:1027:13
[SaltyRTC.Initiator] Message received saltyrtc-client.es5.js:1217:13
[SaltyRTC.Initiator] Received candidates [v0.webrtc.tasks.saltyrtc.org] saltyrtc-client.es5.js:1246:17
[SaltyRTC.WebRTC.initiator] New task message arrived: candidates saltyrtc-task-webrtc.es5.js:721:13
[SaltyRTC.WebRTC.initiator] New event: candidates saltyrtc-task-webrtc.es5.js:1051:13
[PeerConnectionHelper] ICE connection state change: failed angular.js:14199:18
ICE failed, see about:webrtc for more details (unbekannt)
[StateService] RTC connection state: connecting => disconnected angular.js:14199:18
TypeError: plugin.setSuspendState is not a function[Weitere Informationen] nuanria.SpeechHost.js:153:5
[hr]
Und hier noch:
media.peerconnection.enabled;Standard; boolean;true -
-
Danke für die Hilfe!!! Wobei mir jetzt nicht klar ist, was mich noch machen soll, damit es klappt.
-
Danke für die Hilfe!!! Wobei mir jetzt nicht klar ist, was mich noch machen soll, damit es klappt.
@"dbrgn" wird sich das mit Sicherheit mal anschauen. Das einzige, das du jetzt wohl machen kannst, ist wohl zu warten.
Siehe auch hier: https://github.com/threema-ch/threema-web/issues/43 -
Über keinen der ICE Candidates kann eine Verbindung aufgebaut werden. Wenn beide wirklich im gleichen Netz sind und du verifizieren kannst, dass beide miteinander reden können (bspw. du hast einen Server auf deinem PC laufen und kannst diesen über dein Handy erreichen), dann wäre die Frage, ob es eine Firewall auf einem der Geräte gibt oder der Router bestimmte Pakete filtert.
-
Bei mir sind beide Geräte garantiert im gleichen Netz. Ich kann beispielsweise problemlos vom Handy auf die im Netzwerk freigegebenen Dateien des PCs zugreifen. Auf dem PC läuft Windows 7 mit der Standard-Windows-Firewall (deaktivieren hilft auch nicht). Das Handy ist ein Sony Xperia ZL mit Android 5.1.1 und Cyanogenmod. Der Router ist ein älterer Speedport ohne spezielle Filter.
-
Ich komme immer bis 99 %, dann ist Schluss. Egal ob Firefox, Cliqz, Iron oder Chrome. Beide Geräte sind definitiv im selben WLAN.
-
Ich komme immer bis 99 %, dann ist Schluss. Egal ob Firefox, Cliqz, Iron oder Chrome. Beide Geräte sind definitiv im selben WLAN.Welches Handy und welche Android-Version verwendest du?
-
Hallo,
gestern abend ging das noch mit dem Web Client. Heute nicht mehr....
Dauernd kommt "ungültiger Barcode" beim Abfotographieren. Handy (WLAN) und Notebook (Win7, LAN) sind im gleichen Netz.
Threema Web ist aktiv auf dem Handy.
Was kann das sein?
Gruss,
Ralph
