Why do I need a UDP proxy?
At the moment, there is a problem that the available anti-detection tools do not provide complete anonymity cause many sites have begun to use the STUN (Session Traversal Utilities for NAT) protocol, which is used in WebRTC and detects your real IP, into their anti-fraud systems. As a result, this leads to a ban on your account.
We solved the problem one of the first through the introduction of UDP (User Datagram Protocol), on which STUN is based. Now, if you use a UDP-enabled proxy, you can be calm about passing antifraud on our product!
It should be noted that UDP currently only works with Socks5 proxies with UDP support, other connection methods will not work
How do I know if my proxy supports WebRTC UDP?
Go to iphey.com and look at the WebRTC STUN parameter. (there should be the IP address of your request server or yours if you start without asking)
The browser, depending on the parameters of the request, choose needed the mode for work by itself.
Options can be:
Proxy type | Checking JS API | Checking STUN |
SOCKS5 with UDP support | Shows IP of the proxy server | Shows IP of the proxy server |
SOCKS5 without UDP support | WebRTC disabled | WebRTC disabled |
HTTP | WebRTC disabled | WebRTC disabled |
No proxy | Shows your IP | Shows your IP |
API Options (npm package)
The parameter is added to preference in profile startup
gologin_webrtc_enable: Boolean
Remains support for the old format:
Mode: disable - WebRTC is disabled.
Mode: !disable - any value other than disable, WebRTC is enabled.
Started support from 108 Orbita version