FoxyProxy Setup: Databay Proxy Patterns and Verification
Set up FoxyProxy in Firefox or Chrome with Databay: map the gateway fields, route only authorized hosts by pattern, verify the exit with the proxy off and on, and fix failures.
FoxyProxyProxy clientgw.databay.co:8888Operating principle
Send only URLs that match an include pattern for an authorized host through Databay; everything else stays direct, and Global Exclude always wins.
What FoxyProxy Decides and What Databay Decides
FoxyProxy is a proxy-switching extension for Firefox and for Chromium browsers such as Chrome, Edge and Brave. It decides per request whether the browser connects directly or through a saved proxy. Databay decides the rest: the gateway at gw.databay.co:8888 checks your dashboard username and password, and options inside that username select the pool, location and any sticky session.
Use this setup only for sites you own or are permitted to test, and follow each destination's terms. A proxy changes the route a site observes; it does not grant permission.
This guide follows FoxyProxy's official help page and changelog. At the time of writing, addons.mozilla.org listed FoxyProxy Standard 9.8 and the Chrome Web Store listed 9.7, so record your installed version with any evidence. FoxyProxy Basic and Chrome hide some controls until you click the FoxyProxy icon on the Options page. Scripted browsers are covered in the Playwright and Selenium guides.
Map the Databay Gateway to FoxyProxy Proxy Fields
On the Options page, open the Proxies tab and add a proxy. FoxyProxy identifies each proxy by hostname:port:
| FoxyProxy control | Databay value | What to verify |
|---|---|---|
| Title | A purpose label such as Databay US QA | Names the route; no routing effect |
| Type | HTTP, or SOCKS5 on Firefox only | Not HTTPS or SOCKS4 |
| Hostname | gw.databay.co | No scheme, path or stray spaces |
| Port | 8888 | Digits only, unless you use Firefox augmented-port letters |
| Username | The complete username from the Databay dashboard | Pool, location and session match the order |
| Password | The dashboard proxy password | Pasted from a password manager, never shown in a capture |
| Proxy DNS | On, for Firefox SOCKS5 entries | Left at its default so the gateway resolves names |
| Country, City, Color | Optional | Display labels only; they do not request a location |
Title: Databay US QA
Type: HTTP
Hostname: gw.databay.co
Port: 8888
Username: USER-zone-residential-countryCode-us
Password: PASS (from your password manager)Type describes the browser-to-proxy hop, not the site's scheme: with HTTP, HTTPS sites still use a CONNECT tunnel and TLS stays end to end. FoxyProxy's HTTPS type expects TLS to the proxy itself, and SOCKS4 is an older protocol; Databay documents neither for this gateway, only HTTP proxying, HTTPS CONNECT tunnelling and SOCKS5.
Copy the whole username rather than composing it: USER-zone-residential-countryCode-us requests a US residential exit, and USER-zone-residential-countryCode-us-sessionId-abc123 adds a sticky session. Then click Save; FoxyProxy applies nothing until settings are saved.
Select the Databay Network Before Copying the Username
FoxyProxy cannot choose a pool or location; the username does, so decide in the dashboard first:
- Premium Residential accepts one selector at a time: country, state, city, ZIP, coordinate or ASN.
- Residential Flex, Datacenter and Mobile target a country or a continent.
All Databay pools are shared, so no product reserves an address for one customer. A sticky session requests continuity for up to 1440 minutes on Premium Residential and Residential Flex where available, or up to 120 minutes on Datacenter and Mobile. The IP can change before the window ends. Without a session, a new connection may select another available exit while a reused connection may keep the same one; neither outcome is promised.
Firefox and Chromium Differences That Change the Setup
FoxyProxy's help page documents browser differences that matter for an authenticated gateway:
- SOCKS5 authentication is Firefox only. FoxyProxy states that Chrome does not support SOCKS authentication, so use HTTP in Chrome, Edge, Brave and other Chromium browsers.
- Proxy DNS is Firefox only. It passes DNS to the SOCKS proxy and defaults to on. HTTP name resolution is proxy side in both browsers.
- One gateway, several usernames. FoxyProxy treats credentials as port specific, and every Databay route shares
gw.databay.co:8888, so entries with different usernames are ambiguous. Firefox accepts letters after the port, such as8888aand8888b, which FoxyProxy removes before use. In a Chromium browser, keep one entry and edit its username when the route changes. - Private windows. Firefox needs Run in Private Windows enabled for proxy settings; Chrome needs Allow in Incognito only to proxy incognito windows.
- Logging. The Log can record
407 Proxy Authentication Requiredchallenges, but only Firefox shows which proxy handled a request.
The HTTP versus SOCKS5 comparison covers the protocol trade-offs in more depth.
Choose Disable, Individual Proxy, or Proxy by Patterns
The toolbar popup sets one of three documented modes:
- Disable hands proxying back to the browser, so its own or system proxy settings, and any VPN underneath, still apply.
- Individual Proxy, chosen by selecting the Databay entry, sends every connection through it and ignores patterns. It proves a credential cleanly, but all browsing in that profile becomes billed traffic.
- Proxy by Patterns proxies only URLs that match an include pattern. The popup offers it once an include pattern exists, and unmatched URLs go direct.
Some rules run before the mode. FoxyProxy's documented proxying order is Global Exclude, Tab Proxy and Tab Proxy by patterns (Firefox only), Incognito Proxy, Container Proxy (Firefox only), and then Individual Proxy or Proxy by Patterns. Global Exclude therefore beats every pattern, and a Firefox tab or container assignment can override the popup mode, so clear those features before a clean test.
Verify the Observed Exit With the Proxy Off and On
Prove the route before opening the real destination. Databay's What Is My IP page reports the address that reached its server, so it shows a Databay exit only when FoxyProxy routes databay.com through the gateway.
- Proxy off. Set Disable, open
https://databay.com/what-is-my-ipand record the IP, country estimate and UTC time. This baseline includes any system proxy or VPN. - Proxy on for all URLs. Select the Databay entry and load the page in a new tab. The IP should differ from the baseline and the country should match the requested target; if nothing changes, reopen the tab.
- Proxy on by pattern. Switch to Proxy by Patterns with the
://databay.com/include enabled, and the Databay exit should reappear. Disable that pattern, click Save and reload in a new tab: the exit should disappear. - Authorized host. Load one harmless URL you are permitted to test and confirm it used the entry, with the Firefox Log or the Pattern Tester.
The /what-is-my-ip/json endpoint returns the same observation as JSON. FoxyProxy's Test feature can also check a proxy against an IP check server; on Chrome, authenticate first. Each result is point-in-time evidence about the HTTP connection, not WebRTC or other signals, so it is not proof of anonymity. With a sticky session, recheck at meaningful checkpoints and record any change of exit.
Ready to run this for real?
Credentials appear in your dashboard in minutes, on the same gateway and username format this FoxyProxy guide uses.
Export, Import, and Back Up FoxyProxy Settings Without Leaking Credentials
FoxyProxy exports all preferences to a local JSON file and imports them later; nothing applies until you click Save. The full export uses the format FoxyProxy documents for managed storage, and this abridged excerpt shows that it stores credentials in plain text:
{
"mode": "pattern",
"data": [{
"type": "http",
"hostname": "gw.databay.co",
"port": "8888",
"username": "USER-zone-residential-countryCode-us",
"password": "PASS",
"include": [{ "type": "match", "title": "staging", "pattern": "https://*.staging.example.com/*", "active": true }],
"exclude": []
}]
}- Keep full exports in a password manager or secret vault, never in tickets, chat, shared drives or repositories.
- Auto Backup, when enabled, writes a copy to the downloads folder on every Save; keep that folder private or leave the option off.
- Enable Sync copies proxies to browser sync storage on every signed-in device; leave it off unless that reach is acceptable.
- The Proxy List importer takes
host:port:user:passor URL-style lines, which expose the password in a text box and the clipboard; prefer the proxy fields.
To share routing rules, export patterns alone or send a copy with the password blanked, and never host a credential-bearing export for Import from URL. If a full export, screenshot or log leaves your control, treat the password as exposed and replace it. When enterprise policy manages FoxyProxy, local changes do not apply.
Troubleshoot FoxyProxy and Databay by Layer
Find the first failed hop before changing anything. The proxy hop is TCP to gw.databay.co:8888, proxy authentication, then CONNECT or the SOCKS5 handshake; the destination hop is TLS with the site and its HTTP status. FoxyProxy decides whether the proxy hop happens at all, so check routing first.
| Symptom | Layer | Next safe check |
|---|---|---|
| Baseline IP in pattern mode | FoxyProxy routing | Use the Pattern Tester; check earlier entries, excludes, Global Exclude and Firefox's No proxy for list (Firefox 137+) |
| Grey toolbar icon | Browser proxy control | Another extension, such as a VPN add-on, controls proxying; disable it for the test |
| Browser proxy sign-in dialog | Proxy authentication | No credentials are stored for that hostname and port; fill both fields and Save |
| 407 in the Log | Proxy authentication | Re-copy both values; check for spaces or a second entry on the same hostname and port |
| SOCKS5 fails in Chrome or Edge | Proxy authentication | Chromium lacks SOCKS authentication; switch the type to HTTP |
| Failure before any prompt | TCP to the gateway | Check that a VPN or firewall allows outbound port 8888 |
| Wrong regional server over SOCKS5 | DNS | Keep Proxy DNS on in Firefox; with DNS over HTTPS enabled, test resolution explicitly |
| TLS or certificate error | Destination hop | Keep verification on; compare with the proxy off |
| 401, 403, 429 or CAPTCHA | Destination policy | Stop and use the site's supported process; another exit is not permission |
Change one variable at a time and keep each failed observation. A full-tunnel system VPN normally carries the connection to the gateway, so the site still sees the Databay exit while the proxy-off baseline shows the VPN's address. For protocol-level evidence, the cURL proxy guide separates 407, CONNECT and TLS failures. Never put the password in a URL, screenshot or support thread.
Questions specific to FoxyProxy
Which FoxyProxy proxy type should I choose for Databay?
Why does What Is My IP still show my own address with FoxyProxy on?
Can I keep several Databay routes in FoxyProxy at the same time?
Does a FoxyProxy settings export include my proxy password?
Why does the browser show a proxy sign-in dialog when FoxyProxy is on?
Does FoxyProxy Disable mode mean a direct connection?
Same gateway, different control surface
Proxifier
Proxy client
Proxification Rule -> SOCKS5 or HTTPS entry -> gw.databay.co:8888 -> observed exit
Android
Mobile operating system
Wi-Fi network -> Manual or PAC proxy -> app 407 prompt -> observed exit
Pick the network once the route works. Residential for home-connection exits with state, city, ZIP and ASN targeting; datacenter for fast server IPs on public websites. Switching is one word in the username.
Where teams run FoxyProxy behind the gateway: Proxies for cybersecurity testing · Proxies for market research
Ship FoxyProxy to production
Create an account, drop in your gateway credentials, and route your first FoxyProxy request in minutes.
Pricing, order minimums, and traffic validity vary by product.