Janus and Coturn cant connect

[Charles]

Hi im using webrtc janus server, and i set up a coturn in AWS as my turn relay development if everything works fine i will transfer to on premise. Currently im using expressturn.com as my turn relay and everything works fine as relay, then decided to create my own turn relay server because of the subscription, when I testing it with trickle ice, it works fine (Picture 1), but when im using it in my webrtc janus server, i cant get a relay and the logs is in (Picture 2)   

[Charles]

this is my full logs when first connecting using WEBRTC JANUS 

0: ERROR:
CONFIG ERROR: Empty cli-password, and so telnet cli interface is disabled! Please set a non empty cli-password!
0: WARNING: cannot find certificate file: turn_server_cert.pem (1)
0: WARNING: cannot start TLS and DTLS listeners because certificate file is not set properly
0: WARNING: cannot find private key file: turn_server_pkey.pem (1)
0: WARNING: cannot start TLS and DTLS listeners because private key file is not set properly
0: pid file created: /var/run/turnserver.pid
0: IO method (main listener thread): epoll (with changelist)
0: WARNING: I cannot support STUN CHANGE_REQUEST functionality because only one IP address is provided
0: Wait for relay ports initialization...
0:   relay <coturn_private_ip> initialization...
0:   relay <coturn_private_ip> initialization done

0: Relay ports initialization done
0: IO method (general relay thread): epoll (with changelist)
0: turn server id=1 created
0: IPv4. SCTP listener opened on : 0.0.0.0:3478
0: IPv4. TCP listener opened on : 0.0.0.0:3478
0: IO method (general relay thread): epoll (with changelist)
0: IPv4. UDP listener opened on: 0.0.0.0:3478
0: Total General servers: 2
0: turn server id=0 created
0: IPv4. SCTP listener opened on : 0.0.0.0:3478
0: IPv4. TCP listener opened on : 0.0.0.0:3478
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: SQLite DB connection success: /var/lib/turn/turndb
26: IPv4. tcp or tls connected to: <my_public_ip>:1396
26: session 001000000000000001: realm <myrealm> user <>: incoming packet message processed, error 401: Unauthorized
26: IPv4. Local relay addr:  <coturn_private_ip>:19001
26: session 001000000000000001: new, realm=<myrealm>, username=<admin>, lifetime=600
26: session 001000000000000001: realm <myrealm> user <admin>: incoming packet ALLOCATE processed, success
26: session 001000000000000001: peer <janus_public_ip> lifetime updated: 300
26: session 001000000000000001: realm <myrealm> user <admin>: incoming packet CREATE_PERMISSION processed, success
26: session 001000000000000001: peer  <janus_public_ip>  lifetime updated: 300
26: session 001000000000000001: realm <myrealm> user <admin>: incoming packet CREATE_PERMISSION processed, success
38: session 001000000000000001: refreshed, realm=<myrealm>, username=<admin>, lifetime=0
38: session 001000000000000001: realm <myrealm> user <admin>: incoming packet REFRESH processed, success
38: session 001000000000000001: TCP socket closed remotely  <my_public_ip>:1396
38: session 001000000000000001: usage: realm=<myrealm>, username=<admin>, rp=102, rb=13612, sp=5, sb=488
38: session 001000000000000001: closed (2nd stage), user <admin> realm <myrealm> origin <>, local 0.0.0.0:3478, remote  <my_public_ip>:1396, reason: TCP connection closed by client (callback)
38: session 001000000000000001: delete: realm=<myrealm>, username=<admin>
38: session 001000000000000001: peer  <janus_public_ip>  deleted