1. Choose a compatible endpoint
Open the HTTP list or SOCKS5 list. Note the IP address, port and protocol separately. Prefer a recent check and inspect the observed success sample; a small response time from our checker may differ on your network.
The location shown belongs to source-reported endpoint metadata. Your destination may see a different exit location. This list does not promise access to a particular website or streaming service.
2. Open the browser’s proxy settings
Open Firefox Settings and search for proxy. Open the connection or proxy configuration dialog and choose Manual proxy configuration. Labels and the Settings section can differ between Firefox versions.
- HTTP: enter the IP in the HTTP Proxy field and the port in its port field. Apply the same proxy to HTTPS if that option is offered.
- SOCKS5: enter the IP in SOCKS Host, set its port and select SOCKS v5. Select proxy DNS with SOCKS v5 if remote resolution is needed.
- Do not paste
http://orsocks5://into a field that requests only the host address.
Review the “No proxy for” exceptions because matching destinations bypass the proxy. The Mozilla connection settings documentation describes the available options.
3. Verify the request path
Before applying the proxy, note your address on What is my IP. After saving, reload that page and compare the result. Open an ordinary HTTPS page and confirm that it loads without certificate warnings.
A changed IP establishes only that this request used a different exit. It does not establish that other applications use the proxy. DNS and WebRTC behavior need separate checks; see the connection leak tools. Never install a certificate supplied by an unknown proxy operator.
4. Restore your previous configuration
When finished, return to the same dialog and restore the setting you recorded. For a computer that previously used no proxy, select No proxy. On a managed network, restore the original system or automatic configuration instead of assuming No proxy is appropriate.
If browsing stops working, remove the temporary proxy before troubleshooting the rest of your connection. Public endpoints often disappear quickly; a timeout is not evidence that Firefox or your internet connection is broken.