Proxy Error

[Mkopl360]

i'm using a valid proxy but still gettign InvalidProxy [Error]: Failed to connect to proxy.
its bug or something else ?
Also its possible to use different browser profile or only can define OS (and its only support Firefox profile)
code example:

import { Camoufox } from 'camoufox-js';

async function main() {
    const browser = await Camoufox({
        os: 'windows',
        headless: false,
        geoip: true,
        proxy: {            
          server: 'IP:PORT',
          username: 'fd75-time-30-session-y5f',
          password: '2882'
      }
    });
    const page = await browser.newPage();
    
    await page.goto('https://browserscan.net/');
}

main().catch(console.error);

[barjin]

Hello and thank you for your interest in this project!

I didn't manage to replicate this issue - with my proxy URL (in the same format as yours, i.e. IP address with port, username, and password), I got through to the target server.

Could you please try using your proxy with a vanilla Playwright instance (i.e. using the browserType.launch() proxy option)?

Also its possible to use different browser profile or only can define OS (and its only support Firefox profile)

Camoufox is a custom build of Firefox (see docs). You cannot (afaik) impersonate other browsers (like Chromium etc.) using Camoufox, but you can still customize many markers within the browser besides the operating system. See here for the full list of Camoufox features.

[Mkopl360]

currently i'm using it with playwright firefox
code:

import { firefox } from 'playwright';
import { HeaderGenerator } from 'header-generator';
import { FingerprintGenerator } from 'fingerprint-generator';
import { FingerprintInjector } from 'fingerprint-injector';
..........
    const fingerprintInjector = new FingerprintInjector();
    const context = await browser.newContext({
        userAgent: fingerprint.fingerprint.navigator.userAgent,
        locale: fingerprint.fingerprint.navigator.language,
        ignoreHTTPSErrors: true,
        bypassCSP: true,
        proxy: {
          server: 'IP:PORT',
          username: 'fd75-time-30-session-y5f',
          password: '2882'
        },
    });

    await fingerprintInjector.attachFingerprintToPlaywright(context, fingerprint);
........

same proxy i use for camoufox-js but still same issue.

also i need one more help. for camoufox i want to use other browser profile too. how to set it ? any particular file ?
or use fingerprint-suit with camoufox-js ?

and thanks for your response. reapply appreciate your help.

[J3n5en]

Same here.
I can use a proxy on Mac but not on Windows.
getting an error from

camoufox-js/src/ip.ts

Line 97 in 274362b

console.warn(new InvalidProxy(`Failed to connect to proxy: ${proxy}`));

:

 Object property 'bytes' type mismatch. Expect value to be Function, but received Undefined
    at ImpitResponse.text (D:\xxxxxx\.pnpm\impit@0.2.5\node_modules\impit\index.wrapper.js:5:35)

BTW. why impit was chosen over more common alternatives like axios or got(got-scraping)?

[barjin]

@Mkopl360: also i need one more help. for camoufox i want to use other browser profile too. how to set it ? any particular file ? or use fingerprint-suit with camoufox-js ?

I'm not sure I understand your request fully, but you can launch a persistent context using Playwright and Camoufox like this:

import { launchOptions } from 'camoufox-js';
import { firefox } from 'playwright-core';

const camoufox = await firefox.launchPersistentContext(
    './user-data-dir', // path to the user profile directory
    {
        ...await launchOptions({ 
            humanize: true,
            /// other Camoufox-specific options
        }),
        headless: false,
    }
);

const page = await camoufox.newPage();
/// use your Camoufox context as usual with playwright

In general, you can use the launchOptions function to integrate Camoufox into your Playwright scripts more easily than using the Camoufox function itself.

Regarding the proxy issue, I still didn't manage to replicate it. Is it the same issue @J3n5en is mentioning, i.e. Object property 'bytes' type mismatch from impit? If not, could you share the full error message you're getting?

Cheers!

[barjin]

@J3n5en BTW. why impit was chosen over more common alternatives like axios or got(got-scraping)?

We're developing impit as a successor of got-scraping, which got less effective and more complicated to maintain over time. "Dogfooding" impit in Camoufox allows us to get more feedback on the project and see how it behaves in the real world.

I just tried adding a new proxy usage test to impit (apify/impit#145), but it seems to pass just fine with our proxies. Would you mind sharing more details about your setup? Windows version, Node.JS version, etc? Does the error appear with any proxy, or just one specific one? If you could try installing impit separately into a new project and calling it directly, it would also help us understand what is going on.

Cheers!

[J3n5en]

@J3n5en BTW. why impit was chosen over more common alternatives like axios or got(got-scraping)?

We're developing impit as a successor of got-scraping, which got less effective and more complicated to maintain over time. "Dogfooding" impit in Camoufox allows us to get more feedback on the project and see how it behaves in the real world.

I just tried adding a new proxy usage test to impit (apify/impit#145), but it seems to pass just fine with our proxies. Would you mind sharing more details about your setup? Windows version, Node.JS version, etc? Does the error appear with any proxy, or just one specific one? If you could try installing impit separately into a new project and calling it directly, it would also help us understand what is going on.

Cheers!

Try to execute the following code with tsx.

import { Impit } from "impit";
const impit = new Impit({
  proxyUrl: `xxxx`,
  browser: "chrome",
});

const response = await impit.fetch("https://httpbin.org/headers");

await response.text();

in node(v21.7.1) throw Object property 'bytes' type mismatch. Expect value to be Function, but received Undefined
but works in current lts version (v22.15.0).

Seems that upgrading the nodejs version will solve the problem.

thanks!

[barjin]

Somehow, I'm not getting the error on 21.7.1 either (I'm on Linux), but I'm happy to hear you managed to solve this issue for yourself. The Node updates directly after 21.7.1 contain version bumps for undici (Node's native HTTP library), so it's possible that the issue got solved there.

I'll keep this issue open for @Mkopl360 - could you please check if updating your Node version solves your problem as well? Cheers!

[Mkopl360]

I'm currently using Node.js v23 and encountered a proxy error. I'll test with versions 20 through 22 and get back to you as soon as possible. Apologies for the delayed response.

[Mkopl360]

its work with node 21
thanks

[barjin]

@Mkopl360 can you share the full error message coming from your proxy usage on Node 22/23? We're glad to hear you made your use case work, but we would still prefer to fix this in our library (if there's something to fix), to make the lib more valuable for other users.

[hkovachev928]

I get the error. Let me send the error. This is on node 23 installed using NVM. Why I mention NVM is I have had issues with different request depending if its installed using NVM or Brew. Also I do not get the error every time. I get it from time to time when running a lot of workers. The issue is not proxies because when I run the same proxies for extended periods of time I never get that error when using patchright for example.
InvalidProxy [Error]: Failed to connect to proxy: http://[USERNAME]:[PASSWORD]@[PROXY_SITE]:[PORT]/ at publicIP (file:///[PATH]/node_modules/camoufox-js/dist/ip.js:82:26) at async launchOptions (file:///[PATH]/node_modules/camoufox-js/dist/utils.js:384:17) at async NewBrowser (file:///[PATH]/node_modules/camoufox-js/dist/sync_api.js:15:23) at async runThread (file:///[PATH]/dexscr.js:188:19) at async runThread (file:///[PATH]/dexscr.js:253:9) at async runThread (file:///[PATH]/dexscr.js:253:9) at async runThread (file:///[PATH]/dexscr.js:253:9) at async runThread (file:///[PATH]/dexscr.js:253:9) at async runThread (file:///[PATH]/dexscr.js:253:9) at async runThread (file:///[PATH]/dexscr.js:253:9)

[barjin]

Upon closer inspection, this might happen if one of the IP-resolving servers from the URLs list fails to respond:

camoufox-js/src/ip.ts

Lines 72 to 79 in 249bb61

	const URLS = [
	"https://api.ipify.org",
	"https://checkip.amazonaws.com",
	"https://ipinfo.io/ip",
	"https://icanhazip.com",
	"https://ifconfig.co/ip",
	"https://ipecho.net/plain",
	];

By default, if one of the servers fails, camoufox-js retries with the next server from the list (logging the warning message). I might just lower the log severity (or only show it with some debug option), as it's not really that problematic (one of these servers might just not respond from time to time, we still have 5 more to try). I also added more detailed logs to the HTTP client, so we can learn more about the source of those errors.

I'll keep you updated here once I get these changes ready. Thanks!