The extension is a separate product from the ProxyJam proxy service. It needs no account and works with proxies from anywhere. Its optional ProxyJam tab can sign in to a ProxyJam account, but that account, its balance, and its orders belong to the service.
Contact
Email support@proxyjam.com with questions, bug reports, and feature requests.What to include
- The extension version. Open the options page — the gear icon at the top of the popup, or Manage profiles & rules → at the bottom — and read the number after ProxyJam Connector at the foot of the page.
- Your browser and its version. Chrome, Edge, or Firefox, with the exact version number. If the problem shows up in only one of them, say which.
- Steps to reproduce. What you did, what you expected, and what happened instead. Mention the mode you were in — Direct, Auto, or a profile — and what the toolbar badge showed.
- The console log. See Collecting a log.
- Optionally, your configuration without passwords. Useful when the problem involves profiles, rules, or the bypass list. See Sharing your configuration.
Collecting a log
The extension writes to the console of its own background script, not to the console of the page you are browsing.1
Turn on Debug logging
In the options page, open Settings and turn on Debug logging in the Behavior card. Warnings and errors are written either way; the setting also lets the extension’s debug-level messages through.
2
Open the background console
- Chrome: go to
chrome://extensions, turn on Developer mode, and click service worker on the ProxyJam Connector card. - Edge: the same, at
edge://extensions. - Firefox: go to
about:debugging#/runtime/this-firefoxand click Inspect next to ProxyJam Connector.
3
Reproduce the problem and copy the output
Every line the extension writes starts with
[ProxyJam:. Copy those lines into your email.The logger redacts before anything is printed: a field named as a password, username, API key, token, or authorization header is replaced with
••••, however deeply it is nested. Other values — a hostname, or the email address of a signed-in ProxyJam account — are not masked, so read the lines before you send them.Sharing your configuration
1
Open Import / Export
In the options page, open the Import / Export tab.
2
Keep both toggles off
Leave Include passwords off, which is how the tab opens, and leave Encrypt with a password off too. An encrypted export always carries usernames and passwords inside it, so it is never a password-free file.
3
Export as ProxyJam JSON
Choose ProxyJam JSON and press Export. The file downloads as
proxyjam-connector.json, with every username and password removed.Troubleshooting
The proxy stops working after a browser restart
It should not. The extension rebuilds the browser’s proxy configuration from its stored settings every time its background script starts: at browser startup, after an install or update, and whenever the browser restarts the extension’s suspended background script. The mode you chose is part of what is stored. If the proxy is still not in use after a restart:1
Re-apply the configuration
Open the popup, choose Direct (no proxy), then choose your profile or Auto (rules) again. Every switch re-applies the whole configuration from storage.
2
Look at the toolbar badge
A red ! or an amber AUTH on the extension’s icon points to one of the problems below.
3
Tell us
If neither helps, email support with your browser version and a log.
The toolbar badge shows a red exclamation mark
This appears on Chrome and Edge only. The ! badge means the last attempt to apply your configuration failed: the browser refused the proxy setting, or no usable proxy could be built from the profile you selected. Choose Direct (no proxy) in the popup, then select the profile again. The badge returns to normal as soon as an attempt succeeds. If it keeps coming back, email support with the steps that lead to it.An authenticated proxy does not connect on Chrome or Edge
On Chrome and Edge the extension answers a proxy’s login challenge itself, with the username and password stored on the profile whose host and port match that proxy. Two things have to be true:- The Network access permission is granted. Without it the extension does not listen for the challenge at all. It is not requested on install: open Settings, find Network access permission in the Network checks card, and press Grant.
- The proxy accepts the stored credentials. If it rejects them twice for the same request, the extension stops retrying, cancels that request, and shows AUTH on the toolbar badge.
SOCKS5 username and password are ignored on Chrome
Chrome’s proxy API accepts a SOCKS5 server but has no way to hand it a username and password, and Chrome itself does not support SOCKS5 authentication (Chromium issue 40323993). The extension keeps the credentials you enter, but the browser never uses them, and the profile says so: Chrome ignores SOCKS5 username/password. What works instead:- Authorize by IP address. Add your IP address to the proxy’s allowlist. For a proxy bought from ProxyJam, that list is Allowed IP addresses under Managing a proxy.
- Use HTTP, if the proxy offers it. A profile with the
httpscheme and the same credentials authenticates on Chrome — see the entry above. - Use Firefox for that profile. Firefox passes SOCKS5 credentials to the proxy.
A URL or path rule does not match HTTPS pages on Chrome
For HTTPS requests, Chrome strips the path from the URL before handing it to the PAC script. Six condition types depend on that path: URL wildcard, Regex, Exact URL, URL prefix, URL suffix, and URL contains. On Chrome and Edge they see only the host of an HTTPS request, while plain HTTP requests still match in full. The Rules page shows a warning whenever one of your rules uses these types. Rewrite the rule with a host-based condition — Exact domain, Domain + subdomains, or Host wildcard — which match the same way on every browser. Or use Firefox, which checks each request against its full URL. Details: Path matching on HTTPS in Chrome.Auto is greyed out in the popup
Auto (rules) stays disabled, marked no rules yet, until at least one rule exists. Add one on the Rules tab and press Save changes. Rules inside a disabled rule set still count, so Auto can be selectable while every rule is switched off. In that case no rule matches, and everything not on the bypass list goes to the fallback.A health check switched you to another profile
The popup shows a notice beginning Health check failed — switched from, naming both profiles. That only happens when all of these are true: Periodic health check and Auto-failover are both on, you are using a single profile, and that profile has a Failover proxy set. The check fetches your IP address fromapi.ipify.org through the active proxy. A timeout or an HTTP error on that one request counts as a failure, even if other sites still load through the same proxy.
1
Dismiss the notice
Press Dismiss in the popup once you have read it.
2
Test the original proxy
On the Checker tab, press Measure on the original profile. It briefly routes all traffic through that proxy, times a request, and switches back.
3
Switch back
Choose the original profile in the popup. If it still fails and failover is still on, the next scheduled check switches you again.
Checker fields show n/a
Hover over n/a to see why. The usual reasons:- Testing an inactive proxy requires switching to it. Check tests only the profile selected in the popup, and in Direct or Auto mode there is none. Select the profile first, or press Measure, which switches to it briefly and then restores your routing.
- Enable the external IP check to test this proxy. Turn on External IP check under Settings → Network checks. Reachability, IP, and latency all depend on it.
- Geo lookup is off or WebRTC leak test is off. Turn on that toggle in the same card.
- The DNS field always reports unavailable. See DNS-leak test for why.
An import skipped or rejected entries
Every import ends with a report under the Import button. Input never disappears silently: anything that did not come across is counted, with the first three reasons printed as short codes. Skipped entries could not be read as a proxy:
Skipped rules could not be expressed or attached to a profile:
For encrypted exports: Wrong password, or the file was modified covers both cases, because the two cannot be told apart. The file chooser is set to
.json, .txt, .csv, and .bak files; if it will not let you pick a .pjenc export, open that file in a text editor and paste its contents into the box instead. More: Import / Export.
A Firefox container ignores your rules
A container with a proxy assigned sends everything through that proxy, ahead of the global mode and your rules. Only the bypass list, which always includes localhost and private ranges, comes before it. To make a container follow the mode and rules again, set it to Use global mode on the Containers tab. More: Per-container proxies. The Containers tab exists only in Firefox; the Chrome and Edge builds do not have one. If the tab says the browser does not expose container information, the extension could not reach Firefox’s container API — it needs Firefox 128 or later with Container Tabs available.The extension could not read its own stored data
A message ending in the extension could not read its own stored data means the extension refused to save anything. It does that when the stored data could not be read, or was written by a newer version of the extension than the one installed. Rather than overwrite data it cannot trust, it declines every change and, until the data can be read again, shows empty lists and routes traffic directly. The stored data itself is left as it was.- Do not remove and reinstall the extension. Removing an extension deletes its local storage, including the data this state is protecting.
- Update the extension and restart the browser.
- If the message stays, email support with a log. The relevant line reads
read failed; using defaultsormigration failed; using defaults without overwriting.
Known platform limitations
The extension never fakes a capability: where a browser cannot do something, the interface says so. It runs on Chrome 116 or later and Firefox 128 or later; Edge installs the same package as Chrome.Frequently asked questions
Why are my SOCKS5 username and password ignored on Chrome?
Chrome’s proxy API has no way to pass them to a SOCKS5 proxy. The extension stores them, the browser does not use them, and the profile shows a warning. What to do instead: SOCKS5 username and password are ignored on Chrome.My URL or path rule does not match on HTTPS in Chrome
Chrome strips the path from an HTTPS request before the PAC script sees it, so no rule can match on it. Use a host-based condition, or run the profile in Firefox, which evaluates the full URL. The Rules page warns you while any rule depends on the path. Details: A URL or path rule does not match HTTPS pages on Chrome.Does anything get sent to a server?
Nothing until you turn something on:- The network checks — External IP, Geo / ASN, and WebRTC — are off by default, and each one names the host it contacts.
- The health check is off by default. It reuses the External IP request, on the interval you choose.
- The ProxyJam tab sends nothing until you sign in, and asks for access to
api.proxyjam.comat that moment.