-
Notifications
You must be signed in to change notification settings - Fork 6.9k
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
TURN port seems to be +1 than in config #6672
Comments
On a fresh install coturn is listening on 4445 and 4446 (we are going to change those there is PR for that) and Nginx is multiplexing traffic and forwarding turn to port 4445 for turns What is the problem, actually? |
The problem is that if I modify the exposed ports in the file /etc/turnserver.conf (like I did in this example) the port that turnserver actually listen are not those configured but are +1 : listening-port=4445 Gives turnserver listening on 4445 and 4446. |
With another try, it seems that it is not +1, This is not what one could expect when modifying this configuration file. |
So more information you can find at https://github.com/coturn/coturn/blob/master/README.turnserver |
Also this: |
Ok, understood. I close this here as it is not related to jitsi but coturn. |
Sorry but I'm reopening it as on a fresh install of jitsi-meet I got these :
and
So, turnserver will never be reached by the nginx proxy rule as nothing is listening on 4445 because of the coturn bug explained before. |
Can you include the coturn logs from the same run. |
The file exists :
|
Ah there is nothing about ports in there :( |
It says that it won't listen on TLS ports because :
And I found what the problem is : The rights of the key file aren't good for turnserver to read it. The install script on debian should make the file group-owned by turnserver ant readable by group. After those two manipulations, the server is starting right :
|
While this technically solves the problem, the install script should under no circumstances mess around with certficates which were not created by itself during the install process. Certificate owners have to find their own way to fix this. Best way is to copy the keyfile into a directory which is accessible for turnserver only. If only coturn wouldn't drop it's privileges so early... |
So this is done when installing let's encrypt: |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
no stale |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This Issue tracker is only for reporting bugs and tracking code related issues.
Before posting, please make sure you check community.jitsi.org to see if the same or similar bugs have already been discussed.
General questions, installation help, and feature requests can also be posted to community.jitsi.org.
Description
After a fresh install on debian 10.4 turn port seems to get a +1 than what is configured
Current behavior
/etc/turnserver.conf :
Then after a :
systemctl restart coturn
Expected Behavior
Than the port configured are exposed
Possible Solution
Steps to reproduce
Fresh Debian install with nginx installed first
Environment details
The text was updated successfully, but these errors were encountered: