Only internal calls possible
-
here is my turnserver.conf:
server-name=kopanotest.tuxlan.de
realm=kopanotest.tuxlan.de
cert=/etc/tuxlan/keys/public_tuxlan.pem
pkey=/etc/tuxlan/keys/key_tuxlan.pem
fingerprint
listening-ip=0.0.0.0
listening-port=3478
tls-listening-port=5349
use-auth-secret
static-auth-secret=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
cipher-list=“DEFAULT”
no-multicast-peers
min-port=32355
max-port=65535I’ve create 3 account’s for you: kopano1, kopano2, kopano3, the passwords are the same as the account name
The server is reachable under https://kopanotest.tuxlan.de/meet
Webapp does currently not work, i am playing with OIDC for single sign on …
best regards,
Michael -
@mniehren and what have you configured in kwmserver for it?
-
here is my kwmserver.cfg:
oidc_issuer_identifier = https://kopanotest.tuxlan.de
insecure = no
enable_guest_api = yes
registration_conf = /etc/kopano/konnectd-identifier-registration.yaml
turn_uris = turn:kopanotest.tuxlan.de:5349?transport=tcp
turn_server_shared_secret = /etc/turnserver.secret
public_guest_access_regexp = ^group/public/.* -
if your support need root access over ssh, send me the public key to michael@niehren.de
-
@mniehren said in Only internal calls possible:
turn_uris = turn:kopanotest.tuxlan.de:5349?transport=tcp
There are two issues on this line:
- you are using the tls port of turn, but classify it as non-tls in the url (
turn:
instead ofturns:
) - but: most browsers do not fully support turns, so its recommended to use a non tls connection to the server.
- you are using the tls port of turn, but classify it as non-tls in the url (
-
so it’s better to take turn with port 3478 for all browsers ?
-
@mniehren yes
Edit: well it does not have to be this port, but simply the non-tls port of your turn. To raise the chance to get connections on public hotspots you should actually make your turn listen on port 443.
-
ok, i open the port 3847/tcp on the firewall, change the config to
turn_uris = turn:kopanotest.tuxlan.de:3478?transport=tcp
and restart kwmserverdbut i still got no connection with Chrome
-
Port 443 is handled by kwebd. It’s all on the same server.
-
@mniehren said in Only internal calls possible:
3847/tcp on the firewall
Typo?
If it still does not work I recommend again to get in direct contact with our support: https://kopano.com/support-info/
-
i mean port 3478/tcp
-
Hi Felix,
i found the error. I forgot to open the firewall for the turnserver UDP Port’s. Now,
everything is runnig :-)). Many thanks for your help.