Unable to establish Webrtc-connection via own AWS-EC2-TURN-Server, please help.

[Tobias Stein]

Hi folks,

I am currently trying to setup a small demo, where I am running signaling server, turn server and my Webrtc-Application in AWS EC2 instances. Finally I want to connect via my local web-browser (firefox) to my application and receive a webrtc-video-stream. Running this setup works fine locally, but via AWS I currently fail on the TURN server. I have attached the logs of the server-side Webrtc-Application and the firefox webrtc-dump. I am not an expert, but my by someone can explain what is wrong? 

Also here is the log from the Turn (corturn) server:

0: log file opened: /var/log/turn_898_2019-06-09.log

0: pid file created: /var/run/turnserver.pid

0: IO method (main listener thread): epoll (with changelist)

0: Wait for relay ports initialization...

0:   relay 172.31.41.243 initialization...

0:   relay 172.31.41.243 initialization done

0:   relay ::1 initialization...

0:   relay ::1 initialization done

0: Relay ports initialization done

0: IO method (general relay thread): epoll (with changelist)

0: turn server id=1 created

0: IO method (general relay thread): epoll (with changelist)

0: turn server id=0 created

0: IPv4. UDP listener opened on: 127.0.0.1:3478

0: IPv4. UDP listener opened on: 127.0.0.1:3479

0: IPv4. UDP listener opened on: 172.31.41.243:3478

0: IPv4. UDP listener opened on: 172.31.41.243:3479

0: IPv6. UDP listener opened on: ::1:3478

0: IPv6. UDP listener opened on: ::1:3479

0: Total General servers: 2

0: IO method (admin thread): epoll (with changelist)

0: IO method (auth thread): epoll (with changelist)

0: IO method (auth thread): epoll (with changelist)

0: IPv4. SCTP listener opened on : 127.0.0.1:3478

0: IPv4. TCP listener opened on : 127.0.0.1:3478

0: IPv4. SCTP listener opened on : 127.0.0.1:3479

0: IPv4. TCP listener opened on : 127.0.0.1:3479

0: IPv4. SCTP listener opened on : 172.31.41.243:3478

0: IPv4. TCP listener opened on : 172.31.41.243:3478

0: IPv4. SCTP listener opened on : 172.31.41.243:3479

0: IPv4. TCP listener opened on : 172.31.41.243:3479

0: IPv6. SCTP listener opened on : ::1:3478

0: IPv6. TCP listener opened on : ::1:3478

0: IPv6. SCTP listener opened on : ::1:3479

0: IPv6. TCP listener opened on : ::1:3479

0: IPv4. TCP listener opened on : 127.0.0.1:3478

0: IPv4. TCP listener opened on : 127.0.0.1:3479

0: IPv4. TCP listener opened on : 172.31.41.243:3478

0: IPv4. TCP listener opened on : 172.31.41.243:3479

0: IPv6. TCP listener opened on : ::1:3478

0: IPv6. TCP listener opened on : ::1:3479

0: SQLite DB connection success: /var/lib/turn/turndb

194: IPv4. tcp or tls connected to: 188.192.83.90:56317

194: IPv4. tcp or tls connected to: 188.192.83.90:56316

194: session 001000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized

194: session 001000000000000002: realm <> user <>: incoming packet message processed, error 401: Unauthorized

194: session 001000000000000001: TCP socket closed remotely 188.192.83.90:56317

194: session 001000000000000001: closed (2nd stage), user <> realm <> origin <>, local 172.31.41.243:3478, remote 188.192.83.90:56317, reason: TCP connection closed by client (callback)

194: session 001000000000000002: TCP socket closed remotely 188.192.83.90:56316

194: session 001000000000000002: closed (2nd stage), user <> realm <> origin <>, local 172.31.41.243:3478, remote 188.192.83.90:56316, reason: TCP connection closed by client (callback)

531: handle_udp_packet: New UDP endpoint: local addr 172.31.41.243:3478, remote addr 18.184.222.32:53085

531: session 001000000000000003: realm <> user <>: incoming packet BINDING processed, success

531: handle_udp_packet: New UDP endpoint: local addr 172.31.41.243:3478, remote addr 18.184.222.32:53087

531: session 000000000000000001: realm <> user <>: incoming packet BINDING processed, success

531: handle_udp_packet: New UDP endpoint: local addr 172.31.41.243:3478, remote addr 188.192.83.90:60762

531: session 001000000000000004: realm <> user <>: incoming packet message processed, error 401: Unauthorized

531: session 001000000000000003: realm <> user <>: incoming packet message processed, error 401: Unauthorized

531: IPv4. tcp or tls connected to: 18.184.222.32:49694

531: session 000000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized

531: session 000000000000000002: realm <> user <>: incoming packet message processed, error 401: Unauthorized

531: IPv4. tcp or tls connected to: 18.184.222.32:49695

531: session 001000000000000003: realm <> user <>: incoming packet message processed, error 401: Unauthorized

531: session 001000000000000005: realm <> user <>: incoming packet message processed, error 401: Unauthorized

531: session 000000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized

531: session 001000000000000003: realm <> user <>: incoming packet message processed, error 401: Unauthorized

531: session 000000000000000002: realm <> user <>: incoming packet message processed, error 401: Unauthorized

531: session 001000000000000003: realm <> user <>: incoming packet message processed, error 401: Unauthorized

531: session 001000000000000005: realm <> user <>: incoming packet message processed, error 401: Unauthorized

531: session 001000000000000006: realm <> user <>: incoming packet message processed, error 401: Unauthorized

531: IPv4. Local relay addr: 172.31.41.243:51244

531: session 001000000000000004: new, realm=<>, username=<webrtc>, lifetime=3600

531: session 001000000000000004: realm <> user <webrtc>: incoming packet ALLOCATE processed, success

531: session 000000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized

531: session 000000000000000002: realm <> user <>: incoming packet message processed, error 401: Unauthorized

531: session 001000000000000003: realm <> user <>: incoming packet message processed, error 401: Unauthorized

531: session 001000000000000005: realm <> user <>: incoming packet message processed, error 401: Unauthorized

531: session 000000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized

531: session 000000000000000002: realm <> user <>: incoming packet message processed, error 401: Unauthorized

531: session 001000000000000003: realm <> user <>: incoming packet message processed, error 401: Unauthorized

531: session 001000000000000005: realm <> user <>: incoming packet message processed, error 401: Unauthorized

531: session 001000000000000005: TCP socket error: Connection reset by peer 18.184.222.32:49695

531: session 001000000000000005: closed (2nd stage), user <> realm <> origin <>, local 172.31.41.243:3478, remote 18.184.222.32:49695, reason: TCP socket buffer operation error (callback)

531: session 000000000000000002: realm <> user <>: incoming packet message processed, error 401: Unauthorized

531: session 001000000000000003: realm <> user <>: incoming packet message processed, error 401: Unauthorized

531: session 000000000000000002: realm <> user <>: incoming packet message processed, error 401: Unauthorized

...

Cheers,

Tobs.

[nilesh]

Hi Tobias,

I have same setup like you and i am facing the same issue. Did you found some solution ?

It would be very helpful for me. Thanks!!

regards 

Nilesh 

[Tobias Stein]

hi mate,

the first thing i changed was using secured connection with a self-signed certificate. Apparently you can not use webrtc without tls/ssl except for localnetworks. Another thing which got in my way was the NET httplister, it somehow refused any https connections. Also make sure your Router forwards ports and you firwall allows connections for the ports you are using. Good luck.

Cheers,

Tobs