Suggestion: Add TCP Port 443 as an Alternative Port for TURN over TCP

[testfirst.sy]

For Workes & Pages, what is the name of the domain?

``

What is the issue or error you’re encountering

Alternative ports for TURN over TCP

What are the steps to reproduce the issue?

Hi Cloudflare Team,

I have a suggestion regarding the TURN over TCP setup. The default TURN over TCP port is 3478, with port 80 as an alternative for environments where 3478 may be blocked. However, port 80 is less commonly allowed by firewalls today due to the increasing use of HTTPS. Adding TCP port 443 as an alternative for TURN over TCP would improve compatibility with firewalls.

The reason behind this is that many firewalls usually allow traffic over TCP port 443, as it is used for HTTPS. With most websites moving to HTTPS, firewalls are increasingly blocking TCP port 80. As a result, relying on port 80 is increasingly ineffective, whereas port 443 remains widely accessible.

This change could improve connectivity in restricted environments where non-standard ports or even port 80 might be blocked. Although TURN over TLS supports TCP 443, it is not supported in my current setup due to specific compatibility issues with our App.

Thank you for considering this suggestion! This change would greatly enhance usability for users in restricted environments. Please let me know if you have any questions or need further information.

[nils6]

Unfortunately we can’t run TCP and TLS on the same port number on the same IP address.
And from my personal point of view it is more important to keep TLS on port 443, because that is where firewalls expect to see TLS negotiations.