Use a self-signed certificate: You can generate your own self-signed certificate and install it on the local server. Then, trust the certificate in the browser and use it for encrypted communication in WebRTC configuration. Note that self-signed certificates provide less security and credibility than certificates issued by trusted certification authorities.
Use WSS(WebSocket Secure): If the server supports WSS(WebSocket Secure), WebRTC communication can be transmitted through WebSocket Secure. WSS uses TLS to encrypt communication to ensure the security of data. Combining WebRTC with WSS can realize secure WebRTC communication without HTTPS.
Use a proxy server: Another solution is to use a proxy server to encrypt WebRTC communications. The proxy server can encrypt and decrypt communication data and forward it to the target server. This method requires that a certificate be installed on the proxy server and trusted in the browser.
No matter which way you choose, you need to pay attention to the security risks of using WebRTC without HTTPS. Therefore, before implementing any solution, please ensure that you understand and accept these risks and take appropriate security measures to protect your application and user data.