Virtualmin latest update and coturn server

General Discussion
1

Recently I see in Virtualmin some fix and edit about how domains are configured has been made.

I can see that my Nextcloud configured in my Virtualmin server is unable to connect anymore with the Coturn server.

I was following a guide to configure Coturn and Nextcloud but now seems Coturn server is no more working for the Nextcloud talk app.

What sound strange to me is that this should work as I never changed the Coturn configuration. I try also to do a new coturn install and config following the guide that was working but nothing.

Can this issue arrive from some Virtualmin or Webmin update?

In the past I followed what is on this YouTube video and worked, now it doesn’t works anymore.

I tried also with a test php script file and I’m unable to see Coturn server work.

Virtualmin version 7.50.2 GPL
Webmin version 2.610

2

I don’t see how that conversation could be related to your problem (and it is a bug that has been fixed in the current version in our repos, so it is doubly unrelated to your problem).

I don’t know what “no more working” means. Just saying it doesn’t work is not actionable data.

You need to look at logs, you need to give us actual errors, otherwise we can’t possibly be helpful. I have never used Coturn or Nextcloud, so I can’t even begin to guess what problem you have. I don’t even know what one of those things does.

Please re-read our forum guidelines, as it will help you include the necessary information: FAQ - Virtualmin Community

1 Like
3

Hi Joe,
how are you? I hope the day is going well.

Sorry for my incomplete post but I tried to attach all info’s I had.
No error logs or other things that help… I was simply not able to see Coturn work and connect on a Nextcloud Talk or in a test file.

Maybe I’m discovering can exist a bug in Ubuntu 24 and Coturn 4.6.1 that create a lot of listeners so maybe it’s a Coturn bug.

If also maybe not a bug I will try to see if I get support from Coturn.
Thank you and sorry again as I don’t wanna stress you and I know you have a lot to do and follow on the forum.

Wish you a very great day and week.

4

Resolved, was not a Virtualmin issue but issue with Coturn configuration and Firewall.

5

It would really help if someone from Virtualmin could confirm whether domain or proxy template updates could break TURN functionality. Seeing more reports like this lately.

1 Like
6

Sure the issue was the Firewall I need opens ports also on my hosting provider.

sudo firewall-cmd --permanent --add-port=3478/tcp
sudo firewall-cmd --permanent --add-port=3478/udp

sudo firewall-cmd --permanent --add-port=5349/tcp
sudo firewall-cmd --permanent --add-port=5349/udp

sudo firewall-cmd --reload

I made also some Network edit on the config file.
Using the AI can help. I have used Google AI.

1 Like