▶ Yarr.It — network settings
Two things a web page cannot do and an extension can: send this browser through a proxy, and reach services on your own network. Both are off until you turn them on, everything they may touch is listed here, and you can take any of it back at any time.
Waiting for your permission
A page asked for these and has not been allowed yet.
Network protection
Send this browser's traffic through your VPN provider's proxy, and stop WebRTC going around it. Torrent peers connect over WebRTC, so without that second half a proxy covers your page loads and leaves every peer you connect to seeing your real address.
Not protected
This proxy needs a username and password
Chrome cannot take a password from the address, so it is entered here and kept on this machine only — never in your synced Chrome profile. Asking Chrome for the access needed to answer a proxy's password prompt shows a broad warning, so it is only requested if you fill this in. Chrome cannot do this for SOCKS proxies at all — it has no support for SOCKS username and password. If your provider's SOCKS proxy needs one, use their HTTPS proxy instead.
not checked
Your services
Addresses Yarr.It is allowed to fetch from. Revoking one stops the relay
reaching it immediately. Chrome grants these per site, not per port —
allowing 192.168.0.251 covers every port on that machine,
because Chrome has no way to express a port here.
Pages allowed to use the relay
Only these pages may ask Yarr.It to fetch from your network. Anything else is refused, so a random site cannot use this to look around your home network. Add your own Yarr.It instance here if you run one.
Yarr.It never sends cookies or saved logins to these addresses, and never forwards a response anywhere but back to the page that asked. Requests are capped and time out, so a service that has stopped responding cannot back everything else up.