payload: {"action":"created","issue":{"url":"https://api.github.com/repos/coturn/coturn/issues/358","repository_url":"https://api.github.com/repos/coturn/coturn","labels_url":"https://api.github.com/repos/coturn/coturn/issues/358/labels{/name}","comments_url":"https://api.github.com/repos/coturn/coturn/issues/358/comments","events_url":"https://api.github.com/repos/coturn/coturn/issues/358/events","html_url":"https://github.com/coturn/coturn/issues/358","id":417937380,"node_id":"MDU6SXNzdWU0MTc5MzczODA=","number":358,"title":"ALTERNATE-SERVER with TLS","user":{"login":"asgoel","id":1323030,"node_id":"MDQ6VXNlcjEzMjMwMzA=","avatar_url":"https://avatars3.githubusercontent.com/u/1323030?v=4","gravatar_id":"","url":"https://api.github.com/users/asgoel","html_url":"https://github.com/asgoel","followers_url":"https://api.github.com/users/asgoel/followers","following_url":"https://api.github.com/users/asgoel/following{/other_user}","gists_url":"https://api.github.com/users/asgoel/gists{/gist_id}","starred_url":"https://api.github.com/users/asgoel/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/asgoel/subscriptions","organizations_url":"https://api.github.com/users/asgoel/orgs","repos_url":"https://api.github.com/users/asgoel/repos","events_url":"https://api.github.com/users/asgoel/events{/privacy}","received_events_url":"https://api.github.com/users/asgoel/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2019-03-06T18:01:59Z","updated_at":"2019-03-09T00:59:05Z","closed_at":null,"author_association":"NONE","body":"I am having trouble testing the trickle-ice feature https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/ on a coturn instance with a `tls-alternate-server` pointed to another `coturn` instance.\r\n\r\nTrickle ICE is only able to obtain the list of `host` candidates, not the `relay` candidates.\r\n\r\nOn the \"master\" TURN server, I see this in the logs:\r\n```\r\nMar 06 17:58:23 turn-server001 turnserver[23926]: 93: IPv4. tcp or tls connected to: <my_ip>:57668\r\nMar 06 17:58:23 turn-server001 turnserver[23926]: 93: session 001000000000000001: realm <brilliant.tech> user <>: incoming packet message processed, error 300: Try Alternate\r\nMar 06 17:58:23 turn-server001 turnserver[23926]: 93: session 001000000000000001: TLS/TCP socket disconnected: <my_ip>:57668\r\nMar 06 17:58:23 turn-server001 turnserver[23926]: 93: session 001000000000000001: usage: realm=<brilliant.tech>, username=<>, rp=1, rb=28, sp=1, sb=96\r\nMar 06 17:58:23 turn-server001 turnserver[23926]: 93: session 001000000000000001: closed (2nd stage), user <> realm <brilliant.tech> origin <>, local 0.0.0.0:3478, remote <my_ip>:57668, reason: TLS/TCP socket buffer operation error (callback)\r\n```\r\n\r\nOn the \"relay\" TURN server, I see this in the logs:\r\n```\r\nMar 06 17:58:23 turn-relay-server001 turnserver[2695]: 51335: IPv4. tcp or tls connected to: <my_ip>:57669\r\nMar 06 17:58:24 turn-relay-server001 turnserver[2695]: 51335: session 000000000000000002: TLS/TCP socket disconnected: <my_ip>:57669\r\nMar 06 17:58:24 turn-relay-server001 turnserver[2695]: 51335: session 000000000000000002: usage: realm=<brilliant.tech>, username=<>, rp=0, rb=0, sp=0, sb=0\r\nMar 06 17:58:24 turn-relay-server001 turnserver[2695]: 51335: session 000000000000000002: closed (2nd stage), user <> realm <brilliant.tech> origin <>, local 0.0.0.0:3478, remote <my_ip>:57669, reason: TLS/TCP socket buffer operation error (callback)\r\n```\r\n\r\n\r\nIn wireshark, I see two conversations - one between the main server and one between the relay server. The main server conversation completes the TLS Handshake and sends application data back and forth. However, in the relay server conversation, the TLS Handshake is completed, but the client immediately sends a `FIN` packet back to close the connection.\r\n\r\nAny ideas? Happy to provide configuration or pcap capture if necessary.\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/coturn/coturn/issues/comments/471128892","html_url":"https://github.com/coturn/coturn/issues/358#issuecomment-471128892","issue_url":"https://api.github.com/repos/coturn/coturn/issues/358","id":471128892,"node_id":"MDEyOklzc3VlQ29tbWVudDQ3MTEyODg5Mg==","user":{"login":"asgoel","id":1323030,"node_id":"MDQ6VXNlcjEzMjMwMzA=","avatar_url":"https://avatars3.githubusercontent.com/u/1323030?v=4","gravatar_id":"","url":"https://api.github.com/users/asgoel","html_url":"https://github.com/asgoel","followers_url":"https://api.github.com/users/asgoel/followers","following_url":"https://api.github.com/users/asgoel/following{/other_user}","gists_url":"https://api.github.com/users/asgoel/gists{/gist_id}","starred_url":"https://api.github.com/users/asgoel/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/asgoel/subscriptions","organizations_url":"https://api.github.com/users/asgoel/orgs","repos_url":"https://api.github.com/users/asgoel/repos","events_url":"https://api.github.com/users/asgoel/events{/privacy}","received_events_url":"https://api.github.com/users/asgoel/received_events","type":"User","site_admin":false},"created_at":"2019-03-09T00:59:05Z","updated_at":"2019-03-09T00:59:05Z","author_association":"NONE","body":"Hmm, i've listed my `tls-alternate-listener` as `turn-relay.example.com:3478` (with a valid certificate installed), so why is it saying it's connecting to `52.37.198.x:3478` instead of `turn-relay.example.com:3478`? Is this resolution happening on the server before it returns the alternate server? Or is this happening transparently on the client?"}}
other: {"actor":{"display_login":"asgoel"}}