Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Could not Trickle ICE server using external IP #158

Closed
AmitKasundra opened this issue Jun 19, 2017 · 22 comments
Closed

Could not Trickle ICE server using external IP #158

AmitKasundra opened this issue Jun 19, 2017 · 22 comments

Comments

@AmitKasundra
Copy link

AmitKasundra commented Jun 19, 2017

Hello, I have setup Coturn server from Url https://www.webrtc-experiment.com/docs/TURN-server-installation-guide.html#coturn in Ubuntu.

Turnserver is working fine using local-ip, but when I try to trickle using exernal-ip I get error Not reachable?

If I access turnserver from browser url I can access it using external-ip. I get message.

TURN Server
https admin connection

To use the HTTPS admin connection, you have to set the database table admin_user with the admin user accounts.

My turnserver.conf looks like:

user=test:test123
listening-port=3478
tls-listening-port=5349
listening-ip=192.168.22.101
relay-ip=192.168.22.101
external-ip=202.137.12.10
realm=yourdomain.com
server-name=yourdomain.com
lt-cred-mech
userdb=/etc/turnuserdb.conf

cert=/etc/ssl/my-certificate.pem
pkey=/etc/ssl/my-private.key
no-stdout-log

My turnuserdb.conf looks like:

test:test123

I am starting turn server using command:

sudo turnserver -a

And I try to trickle using below format:

turn:202.137.12.10:3478[test:test123]

Trickle: https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/

Please tell me where I am going wrong.

@mvsvolkov
Copy link

mvsvolkov commented Jul 4, 2017

maybe it will helps, but problem likes we've got
in our situation we use router IP address and it start's to work, you could try something like this

external-ip=202.137.12.10/192.168.22.1 (your router ip if exists)

@AmitKasundra
Copy link
Author

AmitKasundra commented Jul 5, 2017

Hi mvsvolkov, I got what was going wrong, it turned out to be that UDP port 3478 was blocked.

Also I was able to get trickle if I used

turn:202.137.12.10:3478?transport=tcp[test:test123].

My external-ip looks like

external-ip=202.137.12.10 (public ip) /192.168.22.101 (local-ip)

@chanhbc
Copy link

chanhbc commented May 7, 2018

I have the same problem, I tried your way but did not work. Can you help me fix it?

listening-device=chanhbc
relay-device=chanhbc
listening-ip=192.168.1.109
listening-port=3478
tls-listening-port=5349
relay-ip=192.168.1.109
external-ip=27.72.61.237
relay-threads=50
lt-cred-mech
static-auth-secret=chanhbc
user=chanhbc:0x3dd53575688e2b9d126e89a336111b37
userdb=/etc/turnuserdb.conf
#max-bps=102400
pidfile="/var/run/turnserver.pid"
no-loopback-peers
no-multicast-peers
sha256
mobility
no-cli
cert=/etc/turn_server_cert.pem
pkey=/etc/turn_server_pkey.pem
stale-nonce
use-auth-secret
Verbose
fingerprint

@misi
Copy link
Contributor

misi commented May 7, 2018

Try to remove ALL of these options:

  • listening-device=chanhbc
  • relay-device=chanhbc
  • relay-threads=50
  • userdb=/etc/turnuserdb.conf # THIS IS NOT an SQLITE db I guess!!
  • mobility
  • stale-nonce

@chanhbc
Copy link

chanhbc commented May 8, 2018

My computer IP: 192.168.1.109
My public IP: 27.72.61.237
I edited file.
My /etc/turnserver.conf looks like:

user=chanhbc:chanhbc
listening-port=3478
tls-listening-port=5349
listening-ip=192.168.1.109
relay-ip=192.168.1.109
external-ip=27.72.61.237/192.168.1.109
realm=yourdomain.com
server-name=yourdomain.com
lt-cred-mech
userdb=/etc/turnuserdb.conf

cert=/etc/ssl/my-certificate.pem
pkey=/etc/ssl/my-private.key
no-stdout-log

My /etc/turnuserdb.conf looks like:

chanhbc:chanhbc

I starting server use command:

sudo turnserver -a

And I try to trickle using below format:

turn:192.168.1.109:3478[chanhbc:chanhbc]

Results returned on the same computer:
image

Results returned on another computer:
image

And If i try to trickle using below format:

turn:27.72.61.237:3478[chanhbc:chanhbc]

result:
image

image

Please tell me where I am going wrong. Sorry for my English not good.

@chanhbc
Copy link

chanhbc commented May 8, 2018

thank @misi i try but it not working

@MazenImara
Copy link

you have to configure you router port forwarding and add port map with port 3478 and your local ip

@chanhbc
Copy link

chanhbc commented Jul 27, 2018

thank @MazenImara, i install success on Server not on My Computer

@neo125874
Copy link

@chanhbc Hi, could you share how you solve this problem?

@chanhbc
Copy link

chanhbc commented Dec 20, 2018

i config after run my server ubuntu and it's working.

@neo125874
Copy link

@chanhbc what king of config? could you explain more? thanks!

@chanhbc
Copy link

chanhbc commented Dec 20, 2018

I will answer you tomorrow, because I do not remember my turnserver configuration

@neo125874
Copy link

@chanhbc many many thanks, hope to see the setting tomorrow, we ran into this situation recently...

@chanhbc
Copy link

chanhbc commented Dec 21, 2018

This project I did many months ago so I will try to answer if I remember.

I followed the instructions here: https://www.webrtc-experiment.com/docs/TURN-server-installation-guide.html#coturn
My configuration file:

listening-port=3478
tls-listening-port=5349

listening-ip=my-server-ip
relay-ip=my-server-ip
external-ip=my-server-ip

realm=coturn-ubuntu
server-name=my-server-ip:7812

lt-cred-mech
user=username:password

#cert=/etc/turn_server_cert.pem
#pkey=/etc/turn_server_pkey.pem

no-stdout-log

Results when I test in ICE trickle,
image

@neo125874
Copy link

@chanhbc hi, you mentioned above "server-ip", public or private? and you built the server then the mobile or broswer are in different wifi?

@chanhbc
Copy link

chanhbc commented Dec 21, 2018

That is the public ip (ip can access server control from another place) is usually the IP-WIFI of the server

@chanhbc
Copy link

chanhbc commented Dec 21, 2018

When you install turnserver on the server, it is accessible anywhere as long as there is a network (I have not tried it with ip6)

@neo125874
Copy link

@chanhbc did you have your server behind firewall? any further configuration?

@chanhbc
Copy link

chanhbc commented Dec 21, 2018

No, I do not have to configure the firewall on my server. I recommend running on a trial server (I can not install on google server)

@neo125874
Copy link

@chanhbc thanks for sharing, our issue happened cause of the firewall, but really appreciate for your config & testing pics.

@RamyaAshika
Copy link

Have you fixed it @neo125874 I'm also facing same problem

@OrionStark
Copy link

Perhaps this can help you:

  • Check your firewal for allowing TCP/UDP over your TURN server PORT

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants