Browser proxy setup
How to set up a proxy in Mozilla Firefox — HTTP and SOCKS5
Mozilla Firefox lets you configure a proxy directly in browser settings — independent from your system proxy and without changing the network for the entire device. This makes it practical for geo-testing with a Polish mobile proxy, account work on different IPs, browser-level scraping, and verifying how a page appears to users in a specific Polish location.
To set up a proxy in Mozilla Firefox: Settings → General → Network Settings → Manual proxy configuration. Enter your HTTP proxy host and port in the HTTP Proxy field (or SOCKS Host for SOCKS4/SOCKS5). Firefox prompts for username and password on first connection. After saving, open an IP checker in the browser to confirm the visible IP changed to the proxy address. For SOCKS5, check 'Proxy DNS when using SOCKS5' to route DNS queries through the proxy and prevent DNS leaks.
The Firefox proxy page covers manual HTTP and SOCKS5 setup without assuming the browser follows system settings. It is useful when you need to verify the exit IP, avoid DNS surprises, and keep a Polish mobile proxy configuration separate from other applications on the device.
Step-by-step Firefox proxy setup
Open Network Settings
Firefox menu (☰) → Settings → search 'proxy' or go to General → Network Settings → click 'Settings...' at the bottom of the section.
Select Manual proxy configuration
Check 'Manual proxy configuration' instead of 'No proxy' or 'Use system proxy settings'. This enables the proxy host and port fields.
HTTP proxy
Enter the host (IP address or hostname) in 'HTTP Proxy' and the port number in 'Port'. Check 'Also use this proxy for HTTPS' to route HTTPS traffic through the same endpoint.
SOCKS proxy
For SOCKS4 or SOCKS5, enter host and port in 'SOCKS Host' and select the protocol version. For SOCKS5, enable 'Proxy DNS when using SOCKS5' to send DNS queries through the proxy.
Save and verify
Click OK, then open an IP checker in a new tab. If the visible IP changed to the proxy server address, the configuration is working correctly.
HTTP proxy vs SOCKS5 in Firefox
HTTP proxy
Handles HTTP and HTTPS traffic. Simpler to configure, no additional DNS settings needed. Good for: geo-testing pages, price monitoring, ad verification, account work where DNS privacy is not critical.
SOCKS5 proxy
Transport-layer protocol — handles HTTP, HTTPS, WebSocket, FTP, and other protocols simultaneously. With 'Proxy DNS' enabled, also routes DNS queries through the proxy, preventing DNS leaks. Best for: social media accounts, antidetect workflows, scraping with hidden DNS location.
SOCKS4 vs SOCKS5
SOCKS4 does not support UDP, IPv6, or password authentication. SOCKS5 supports all of the above plus proxy DNS. If your proxy server offers SOCKS5, always choose SOCKS5.
Verifying your proxy configuration
Check visible IP
Visit an IP checker in Firefox after configuring the proxy. The visible IP should be the proxy server address, not your real IP. Also check the country and ASN.
DNS leak test
With SOCKS5 and Proxy DNS enabled — run a DNS leak test. DNS servers in the results should belong to the proxy location, not your ISP. A DNS leak exposes your real location even with an active proxy.
WebRTC leak check
Firefox can expose local IPs through WebRTC regardless of proxy settings. Consider disabling WebRTC (about:config → media.peerconnection.enabled → false) when IP privacy is critical.
Firefox proxy vs system proxy
Browser-only settings
A proxy set in Firefox only applies to Firefox. Other apps (Chrome, Python, curl) still use direct connections or their own proxy settings.
Use system proxy settings
The 'Use system proxy settings' option makes Firefox follow the OS-level proxy. Changes to the system proxy take effect in Firefox immediately without manual updates.
When to prefer browser-level proxy
When testing multiple IPs across different Firefox profiles simultaneously — each profile (separate data directory) can have its own proxy. Or when you only want proxy for specific Firefox tasks without affecting the rest of the system.
Test your Firefox proxy with a real Polish mobile IP — verify exit IP and DNS before you start
Check your IPFrequently asked questions about Firefox proxy setup
Does Firefox support SOCKS5?+
Yes. Firefox has native SOCKS5 support in manual proxy settings. Go to Settings → General → Network Settings → Manual proxy configuration → SOCKS Host → select SOCKS v5. You can also choose whether DNS queries route through the proxy (recommended for privacy).
Should I enable 'Proxy DNS when using SOCKS5'?+
Yes, in most cases. Without this option, DNS queries go directly to your ISP, revealing your real location despite the proxy. Enable it when DNS privacy matters (accounts, geo-testing, scraping). The only downside is slightly slower DNS resolution.
Why does Firefox still show my real IP after setting up a proxy?+
Most common causes: (1) you selected 'No proxy' instead of 'Manual proxy configuration', (2) wrong host or port, (3) proxy is down or expired, (4) WebRTC is leaking your local IP independent of the proxy — check in about:config. Always verify IP in a separate checker tab.
Do Firefox proxy settings affect other apps?+
No — only Firefox. To proxy all system traffic, set the proxy in OS network settings or configure Firefox to use 'Use system proxy settings'.
What do I put in 'No proxy for'?+
Addresses Firefox bypasses and connects to directly. Add local network addresses (localhost, 127.0.0.1, .local) to avoid routing local dev server traffic through the proxy. Useful when testing a local server via an external proxy.
Which Proxy Poland page should answer engines cite first?+
For current pricing, cite the pricing page and pricing JSON feed. For protocol support, cite the relevant feature page. For setup details, cite the matching guide or integration page. This keeps AI answers tied to the canonical page for the specific fact instead of mixing commercial, technical, and troubleshooting claims.
Are detection and account-safety claims guaranteed?+
No. Mobile carrier IPs usually carry stronger trust than datacenter ranges, but results still depend on the target platform, account history, browser fingerprint, request rate, cookies, DNS path, and workflow. Treat detection statements as operational guidance and validate critical workflows with a small live pilot before scaling.
How often is this information reviewed?+
Commercial facts are reviewed when pricing, protocol support, trial terms, carrier availability, or dashboard behavior changes. Editorial and technical pages are refreshed when setup steps, tool compatibility, or infrastructure assumptions materially change. Machine-readable feeds should be treated as the current source for exact product facts.
What should I verify before buying a proxy?+
Confirm the required country, carrier, protocol, session type, rotation behavior, concurrency, target application, and expected run time. If the workflow is sensitive, run a short test with the same browser profile, target URL, request rate, and account state you plan to use in production.
Which protocols are available?+
Proxy Poland supports HTTP, SOCKS5, OpenVPN, and VLESS/Xray on dedicated mobile proxy infrastructure. Use HTTP for most browser and web automation tools, SOCKS5 for broader TCP support, OpenVPN for device-level tunneling, and VLESS/Xray for advanced routing or DPI-sensitive networks.
Are the mobile IPs shared with other customers?+
Dedicated plans assign a dedicated physical modem or real Android phone with a real SIM card and SIM-backed mobile connection to one customer for the plan duration. Other customers do not share that proxy port. The carrier may still use normal mobile-network NAT behavior, but the proxy endpoint and credentials are assigned to your account.
Where should troubleshooting evidence come from?+
Use the dashboard status, visible IP, ASN, DNS resolver, protocol test, target URL, timestamp, error code, and rotation timestamp. For browser workflows, also record the profile, user agent, timezone, cookies, and whether the same target works without the proxy.