Outbound ports when forcing traffic to 443 TLS

Request for enhancement
1

I have been using OpenVidu3 for my projects and noticed a potential gap in the documentation regarding traffic handling when forcing it to use 443 TLS which is needed in environments with strict firewall.

The current documentation seems to imply that all outbound ports are open for proper functionality. However, in practice, I found that the 40000-60000 UDP port range must be explicitly opened for the platform to operate as expected. Please let me know if this observation correct or not.

This is quite important to know while deploying in environments with strict firewall rules or outbound traffic restrictions. Highlighting this requirement in the documentation would greatly help developers configure their setups without unnecessary troubleshooting which had to spend additional time for.

Could you consider updating the relevant sections of the documentation to reflect this? Including a clear explanation of why these ports are needed and any potential workarounds for environments that restrict outbound traffic would be invaluable.

Thank you for your excellent work on OpenVidu. I look forward to seeing this improvement.

1 Like
2

Thanks for your words, we’re really putting a lot of effort to improve OpenVidu development and operations experience.

Which type of deployment are you using?

I think outbound traffic happens in the internal network where OpenVidu is deployed, but the traffic should not pass through the public internet.

Is this the guide you’ve used?: Force traffic to 443 TLS - openVidu